in reply to Install Perl64 *AND* Perl32

I had a similar frustration when I installed ActiveState 5.14.2 on my new work machine.

Many of the PPM modules are not available and the PDK graphical Perl debugger does not run under Win64

So I finally installed the 32-bit and haven't looked back. I still kept the 64-bit version on the machine but I never use it

From the ActiveState documentation at:

http://docs.activestate.com/activeperl/5.14/install.html

Side-by-Side x64 and x86 Installation: On 64 bit operating systems which support 32 bit compatibility, both x86 and x64 versions of ActivePerl can be installed on the same system as long as they are installed in separate directories. The Windows MSI installer will suggest the following default directories to keep them separate:

Replies are listed 'Best First'.
Re^2: Install Perl64 *AND* Perl32
by EigenFunctions (Beadle) on Mar 16, 2012 at 01:22 UTC

    tokpela:

    That is good to know that I can have both installed and use what I need by specifying it at run time. I run a few analysis programs, from time to time, that are huge with 100's of multi-megabyte data files and having a 64-bit system might speed things up.

    I now have "arch = MSWin32-x64-multi-thread-5.14" and it is installed at "D:\Apps\Perl64". Having installed other Win32 applications, there already exists "D:\Apps (x86)", so that is where I will install the 32-bit version of Perl.

    Given what you mentioned, there are apparently no environment variables or registry entries that will get confused with two versions on the same machine. Although, I wonder how PPM will distinguish between the two.

    As for the loading of two libraries, even though I use a lot of disk space, I don't expect to run out of space anytime soon.

    My sincere thanks to everyone that responded, I appreciate the help!

    Thanks,

    EigenFunctions

[reply]
      I wonder how PPM will distinguish between the two.

      PPM is (at its heart) a perl script. It will install into whichever Perl installation is used to run it. So, if you do:

      path c:\perl32\bin\; ...
ppm

      [download]

      It will run under and install into the 32-bit version.

      If you do:

      path c:\perl64\bin\; ...
ppm

      [download]

      It operates upon the 64-bit install. (Assuming you use your paths not mine :)

      One possibility for making life a little easier is to have both perls in your path (your preferred version first), and rename the ppm.bat files in the two subdirectories as (say) ppm32.bat and ppm64.bat.

      You could also rename (say) the 64-bit perl.exe to perl64.exe. And you can set up two sets of file associations:

      C:\test>assoc .pl
.pl=Perl

C:\test>ftype perl
perl=c:\perl32\bin\perl.exe "%1" %*

C:\test>assoc .pl64
.pl64=Perl64

C:\test>ftype perl64
perl=c:\perl64\bin\perl64.exe "%1" %*

C:\test>set pathext
PATHEXT=.pl;.pl64;.COM;.EXE;.BAT;.CMD;

      [download]

      Then you can specify which perl is used for your perl scripts by giving them the appropriate extensions.

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.

      The start of some sanity?
[reply]
[d/l]
[select]

        That is really a great idea, I'll set it up that way.

        Thanks again for all the help...

        Thanks,

        EigenFunctions

[reply]

In Section Seekers of Perl Wisdom