On Tue, Apr 21, 2015 at 8:57 PM, Harald Jörg <[email protected]> wrote:
> > The DLLs are the notorious libeay32_.dll and ssleay32_.dll. I guess zlib1_.dll, as used by > Archive::Tar, is of the same sort. Hmmm... I can --link them to the > executable, but after unpacking to tempdir they end up in a directory > where apparently Windows doesn't look for them. What command line did you use? I just tried: > pp -o ssleay.exe --link libeay32_.dll --link ssleay32_.dll -E "use Net::SSLeay; say 'OK'; And this places these dlls into shlib/MSWin32-x86-multi-thread-64int in the packed executable: $ unzip -l ssleay.exe | grep -i dll 27136 09-15-2014 20:10 lib/auto/File/Glob/Glob.xs.dll 44544 09-15-2014 20:48 lib/auto/List/Util/Util.xs.dll 19456 09-15-2014 20:10 lib/auto/MIME/Base64/Base64.xs.dll 350208 09-15-2014 21:42 lib/auto/Net/SSLeay/SSLeay.xs.dll 36352 09-15-2014 20:34 lib/auto/Socket/Socket.xs.dll 1764352 07-28-2014 02:31 shlib/MSWin32-x86-multi-thread-64int/libeay32_.dll 394752 07-28-2014 02:31 shlib/MSWin32-x86-multi-thread-64int/ssleay32_.dll And they will be extracted to the top level cache directory which is in the PATH when the executable is run. I can provide a list of CPAN module dependencies which Module::ScanDeps > doesn't find to its queue. However, these dependencies are only > required if certain conditions are met. For applications where these > conditions don't apply, the PAR gets bloated without need. > Please do - PAR::Packer (and Module::ScanDeps) try to err on the generous side. For example, if there's the slightest whiff that a script might be using unicode stuff, the whole machinery will be included. Cheers, Roderich
