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.
In reply to Re: PAR::Filter::Crypto Fails
by Anonymous Monk
in thread PAR::Filter::Crypto Fails
by cmv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |