Any major problems or gotchas with Perl2EXE or PerlApp? I have used PAR
because it was "free", but i think its time to get serious about this :)
I used both in the past, but I had to stop using Perl2exe as the version of
perl they were supporting at the time caused me issues (was bugs in perl and
I needed to use a later version) - this issue probably doesn't exist now.
One feature I like with PerlApp is the --dyndll switch:
--dyndll
Use the 'dynamic DLL loader'. By default, PerlApp writes bundled
DLLs to disk in the "tmp" directory and then uses the operating
system to load them into the process. The default setting is
"--nodyndll".
The dynamic DLL loader bypasses some operating system mechanisms
and loads the libraries directly from memory without ever writing
them to disk. However it may not be fully compatible with all types
of DLLs. It is also not yet compatible with Windows 9x. Executables
generated using the "--dyndll" option do not run on Windows
95/98/Me.
This means that dll's such as the Win32::GUI modules aren't extracted to
disc, then loaded again - a significant saving in start up time. The gotcha
is the 95/98/Me issue (which isn't a problem for me). I also use the PerlApp
GUI now and again to track down unused modules that sometimes add to the exe
size. Both have a free trial (or at least did) so try both:)
Cheers,
jez.
