pp --gui -l \Perl\site\lib\auto\Wx\wxbase252u_vc_custom.dll -l \Perl\site\lib\auto\Wx\wxbase252u_net_vc_custom.dll -l \Perl\site\lib\auto\Wx\wxbase252u_xml_vc_custom.dll -l \Perl\site\lib\auto\Wx\wxmsw252u_adv_vc_custom.dll -l \Perl\site\lib\auto\Wx\wxmsw252u_core_vc_custom.dll -l \Perl\site\lib\auto\Wx\wxmsw252u_html_vc_custom.dll
-M "Wx::DocView" -N CompanyName="DonorWare LLC";LegalTrademarks="DonorWare";ProductVersion="1.49";FileVersion="1.49";ProductName="dwlaunch";Comments="Production Version" --icon icons\dw.ico -o bin\dwlaunch.exe dwlaunch.pl
And this is at the top of the script being pp'd:
# Pre-Load all the Wx modules that need dll/so support
use Wx::Calendar;
use Wx::DateTime;
eval("use Wx::DocView;") if $^O eq "MSWin32";
# and whatever else you need based on what tags were specifiedWe have started trying out the eval method (notice the corresponding -M in the build script) to avoid some cross-platform issues... (wxMac does *not* like Wx::DocView).
Ed W wrote:
Ed W wrote:
I have used PAR successfully to package my app in the past. Just got a new PC and loaded on recent perl (5.8.6), and whatever the latest wxperl is. My script runs fine without PAR, but using PAR gives an error:
Further to this. I find that everything works fine if I generate an exe directly (and use "-l wxmsw242.dll"). However, if I generate a par file (-p) then lots of the dependencies don't seem to get included, not even if I explicitly list them with -M or put them right at the top of the script in USE statements...
Any ideas?
Ed W
--
Mike Schroeder
877-751-3300 x401 [EMAIL PROTECTED] http://www.donorware.com
