NAME
wxpdk
VERSION
Version 0.11
SYNOPSIS
PerlAPP / PDK assistant
To start perlapp gui run 'wxpdk' without any arguments.
To use perlapp from the command line you can use wxpdk to create argument file
wxpdk -A argfile.args
then:
perlapp @argfile.args--norunlib --dyndll --gui --exe foo.exe foo.pl
To create a full .perlapp file without loading GUI
wxpdk -S foo.pl -P foo.parlapp
All options to wxpdk are
-S scriptname to package
-P perlapp file to write
-A args file to write with wxPerl dependencies
-H print these options
Wx::Perl::Packager now supports the --dyndll option for PerlApp. The wxWidgets DLLs
are not themselves dynamically loaded.
Wx::Perl::Packager does not support the --clean option for PerlApp
Wx::Perl::Packager works with PerlApp by moving the following extracted bound
wxWidgets files to a separate temp directory:
base
core
adv
mingwm10.dll if present
gdiplus.dll if needed by OS.
The name of the directory is created using the logged in username, wxWidgets versions
the file sizes of the wxWidgets DLLs. This ensures that your application gets the
correct Wx dlls whilst also ensuring that only one temp directory is ever created
for a unique set of wxWidgets DLLs
base, core, adv and mingwm10.dll should be bound as wxcore/dllname.dll.
All other wxWidgets dlls should be bound as 'dllname.dll'.
The wxpdk utility takes care of this for you.
At the start of your script ...
#!c:/path/to/perl.exe
use Wx::Perl::Packager;
.....
or if you use threads with your application
#!c:/path/to/perl.exe
use threads;
use threads::shared;
use Wx::Perl::Packager;
Wx::Perl::Packager must be loaded before any part of Wx so should appear at the
top of your main script. If you load any part of Wx in a BEGIN block, then you
must load Wx::Perl::Packager before it in your first BEGIN block. This may cause
you problems if you use threads within your Wx application. The threads
documentation advises against loading threads in a BEGIN block - so don't do it.