Hello Everyone, I'm seeing these couple of problems with PAR-Packer-1.005, well this one was present with 1.004 too but had different line numbers in the error message:
If perl512.dll is in the output path (where a.exe is created) I get this error == B:\>pp -d -e "print q(hello!!)" Can't locate Win32.pm in @INC (@INC contains: .) at -e line 780. BEGIN failed--compilation aborted at -e line 966. C:\strawberry\perl\site\bin/pp: Failed to extract a parl from 'PAR::StrippedPARL ::Dynamic' to file 'parl8R0UwKC.exe' at C:/strawberry/perl/site/lib/PAR/Packer.p m line 1172, <DATA> line 1. == It's not big deal, renaming perl512.dll to something else works but took me a couple of days to figure out why was it giving my an error randomly :P There are couple of other issues where I'm not sure if there's a real problem or I have wrong expectations. I've been running tests with a lot of switch combinations and getting wierd results. It's mainly about the -d and -B switch. I have the following combination of switches that I "think" are valid: 1. pp -e "print qq(hello world!)" # Single .exe without dependencies that works on any Win32 installation. (-B implied if -p or -P is not mentioned) 2. pp -d -e "print qq(hello world!)" # .exe that requires perl512.dll. I expected that putting perl512.dll in the same folder as the .exe would make it work on any Win32 installation (-B implied if -p or -P is not mentioned) 3. pp -p -e "print qq(hello world!)" # Par archive with no bundled core modules. Would work on any win32 installation with parl.exe 3. pp -P -e "print qq(hello world!)" # Perl script with no bundled core modules. Would work on any win32 installation with parl.exe. This looks like a perlscript with an embedded .par file, is that right? One other unrelated question: There's a parl.nsi in the package directory of PAR-Packer tarball which looks like a NSIS script but I can't figure out how it's being used. Could someone please point me in the right direction. Regards.
