in reply to "Strawberry Perl" - can it live together with ActivePerl 5.10.0 Build 1003 (on WinXP)?

sure, as long as you don't install activeperl in C:\strawberryperl, and you fix your %ENV, you're good to go. Here's what I use
set INCLUDE=;C:\strawberry\c\include;C:\strawberry\perl\lib\CORE set LIB=;C:\strawberry\c\lib;C:\strawberry\perl\bin set path=%windir%\system32 set path=%path%;%windir% set path=%path%;%windir%\System32\Wbem set path=%path%;C:\strawberry\perl\bin\ set path=%path%;C:\strawberry\c\bin set path=%path%;%programfiles%\gnuwin32\bin set path=%path%;%programfiles%\GNU\GnuPG @rem @echo ... set TMPDIR=
after that cpan/cpanp correctly calls the strawberry version
  • Comment on Re: "Strawberry Perl" - can it live together with ActivePerl 5.10.0 Build 1003 (on WinXP)?
  • Download Code

Replies are listed 'Best First'.
Re^2: "Strawberry Perl" - can it live together with ActivePerl 5.10.0 Build 1003 (on WinXP)?
by syphilis (Archbishop) on Aug 24, 2008 at 09:53 UTC
    set INCLUDE=;C:\strawberry\c\include;C:\strawberry\perl\lib\CORE set LIB=;C:\strawberry\c\lib;C:\strawberry\perl\bin
    It is pointless setting the LIB and INCLUDE environment variables. They are not used by Strawberry Perl(afaict) and MinGW certainly makes no use of them.

    Mind you, they probably do no harm - unless you subsequently start using a Microsoft Compiler (Visual Studio *does* take notice of the LIB and INCLUDE variables). Even then, it might not cause any problems.

    It's just a potential cause for confusion, that's all. People see that Strawberry sets those environment variables, and think it must serve a purpose. But it doesn't :-)
    I removed them from my Strawberry env vars long ago, without any ill effect.

    Cheers,
    Rob
      Ha, its a leftover from running multiple perls
        its a leftover from running multiple perls

        Installing Strawberry Perl will set those variables - and Strawberry Perl is the only perl does that. So I think it's a leftover from installing Strawberry Perl .... agreed that it's a leftover from *somewhere*, at least :-)

        Cheers,
        Rob
      Strawberry USED to set those env variables, it doesn't any more.