Got perl2exe, and it works a treat :)
old par/pp compile time (with filters) -> 10 mins
new perl2exe compile times -> 10 seconds
its also dropped the memory footprint back down to where it should be
(40Mb down to 17Mb), and it also fires up a lot faster (8-9 seconds down
to 2-3 seconds).
Wha
I have used Perl2Exe successfully for internal and commercial
applications for years now. I highly recommend it.
--Steve Lloyd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jeremy White
Sent: Wednesday, August 23, 2006 9:39 AM
To: [EMAIL PROTECTED]
Cc:
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
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 :)
Steve
Adding resources works for both Perl2exe and PerlApp, but I think you
might have to add resources to Parl.exe (or what ever its called) rather
I dont want to store the plain bitmaps as files in a directory where the
EXE is located, to prevent them being mangled or replaced by end-users.
Does anyone have any good ideas or tips on how I would securely "pack"
the bitmap files (various sizes and color depths) all into one large
disk file (
Hi all
Recently, my code has become a bit "bloated" with inline bitmaps.
Although this causes no problems when run from the native perl
application, when I run my code through PAR/PP (with filters), it causes
the EXE to "fire-up" a lot slower, due to the extra room taken up by the
images, and
6 matches
Mail list logo
