in reply to Copying the Strawberry perl.exe

Copying the perl.exe alone will not work, as it won't find the installed libraries that way. What you can do is copy/move the perl of Strawberry to c:\perl64</p>. At least my ActiveState (5.12.x) lives under <c>C:\Program Files\Perl, having bin/ and lib as subdirectories there, and if your "standard" Perl in c:\Perl64 doesn't have these subdirectories, your "standard" is not really existent outside of your organization :)

Replies are listed 'Best First'.
Re^2: Copying the Strawberry perl.exe
by Boldra (Curate) on Jul 04, 2011 at 11:15 UTC
    perl.exe does continue to work after we copied it, although I don't know how. It even finds libraries in site/lib. I stringsd the exe, but found no path. Maybe it's finding a dll from the PATH somewhere which contains the rest of the config?

    Yes "standard" here is just what someone said it is.



    - Boldra

      Perl.exe usually loads perl512.dll, which contains the core of Perl. I believe that all other directories are (on Windows) determined relative to perl512.dll. So either the "correct" perl*.dll is loaded from the appropriate directory, or you have the appropriate PERL5INC set up to make this work. Just copying the perl.exe around shouldn't work.

        This leads me to wonder whether it would help to delete the original perl.exe after copying it to the new location. Of course, the OP has probably done that, but I don't see it stated explicitly anywhere in the thread.

        Regards,

        John Davies