NAME
wxpar
VERSION
Version 0.18
SYNOPSIS
PAR assistant
run 'wxpar' exactly as you would run pp.
e.g. wxpar --gui --icon=myicon.ico -o myprog.exe myscript.pl
At the start of your script ...
#!c:/path/to/perl.exe
use Wx::Perl::Packager;
use Wx;
.....
or if you use threads with your application
#!c:/path/to/perl.exe
use threads;
use threads::shared;
use Wx::Perl::Packager;
use Wx
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.
wxpar will accept a single named argument that allows you to define how the
wxWidgets libraries are named on GTK.
wxpar ordinarily packages the libraries as wxbase28u_somename.so
This will always work if using Wx::Perl::Packager.
However, it maybe that you don't want to use Wx::Perl::Packager, in which case
you need the correct extension.
If you want librararies packaged as wxbase28u_somename.so.0, then pass the first
two arguments to wxpar as
wxpar wxextension .0
If you want wxbase28u_somename.so.0.6.0 , for example
wxpar wxextension .0.6.0
which would mean a full line something like
wxpar wxextension .0.6.0 -o myprog.exe myscript.pl
NOTE: the arguments must be FIRST and will break Wx::Perl::Packager (which should
not be needed in this case).
OF COURSE - the symlinks must actually exist. :-)