For example, in my launcher.pl, I have tried variations of:
use PAR "http://website/path/launcher.par"; or use PAR; use lib "http://website/path/launcher.par";
I then use "pp -o launch.exe launch.pl" to get a binary "launcher" to deploy which in turn *should* remotely fetch the freshest version of launcher.par. I have this working in RH9, but am having trouble in Windows. Since PAR is excluded from the pp process, is there some trick to getting it, and in turn LWP::Simple to be included in my exe file? I have tried numerous variations (using -M params to pp, or adding the files to the PAR file before converting it to an exe, etc).
I amusing a number of -M args to pp to ensure that those modules I need that have dll/so (such as some wxPerl modules) are embedded into the binary launcher, saving me the hassle of fetching those remotely for different platforms - my remote PAR files should just be pure Perl.
The docs and message boards seem to imply this should be possible, and it does seem to be possible in Linux (unless I am not running into the problem since Perl and LWP::Simple seem default), I'm just wondering if there is some trick to how PAR.pm gets instantiated since it is not included in the PAR file itself.
Thanks for any advice.
Mike Schroeder DonorWare LLC
