in reply to PAR::Filter::Crypto Fails

Par won't automatically detect DLL's that modules might call. So one way around this is use of the -x argument - which will execute your program as part of packaging to see what it loads

What you should do is use -x and --xarg=parbuild, then in my program if the first argument is 'parbuild' I trigger a 'build' sub routine that calls and uses all the modules and performs comms etc, this helps ensure all the DLL's get used, and thus detected by par.

Replies are listed 'Best First'.
Re^2: PAR::Filter::Crypto Fails
by swl (Prior) on May 02, 2023 at 01:38 UTC

    That ensures all the relevant perl libraries, and their associated DLLs, are detected by Module::ScanDeps.

    However it does not tell PAR::Packer which external DLLs to load. External tools like objdump, otool and ldd are needed to find those, and are what App::PP::Autolink uses, depending on the OS.

    Use of the argument to trigger extra module loads is useful. I do the same thing with an environment variable.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom