I have the impression that AS compiles their Perl with an exceedingly long sets of library paths, then edits the binary after installation to use the actual installation paths on that machine. Clever, but a hack.
No. It's conveniently possible under Windows to get at the path where your executable lives in. ActiveState does patch some modules upon installation, I believe, but patching the Perl.exe executable is not necessary, as long as the relative position of files remains the same.
This is perl, v5.8.3 built for MSWin32-x86-multi-thread
(with 8 registered patches, see perl -V for more detail)
Copyright 1987-2003, Larry Wall
Binary build 809 provided by ActiveState Corp. http://www.ActiveState.
ActiveState is a division of Sophos.
Built Feb 3 2004 00:28:51
Perl may be copied only under the terms of either the Artistic License
+ or the
GNU General Public License, which may be found in the Perl 5 source ki
Complete documentation for Perl, including FAQ lists, should be found
this system using `man perl' or `perldoc perl'. If you have access to
Internet, point your browser at http://www.perl.com/, the Perl Home Pa
C:\Programme\Perl\bin>.\perl.exe -e die@INC
C:/Programme/Perl/libC:/Programme/Perl/site/lib. at -e line 1.
Q:\tmp_perl>xcopy /s C:\Programme\Perl .
Q:\tmp_perl\bin>.\perl -e die@INC
Q:/tmp_perl/libQ:/tmp_perl/site/lib. at -e line 1.