Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Compile - > Perl to EXE
- Thread starter jr8rdt
- Start date
PerlApp by ActiveState is a really good one that I used for quite a while. It's not free though, but it does a pretty good job at creating the smallest executable size possible.
For a free solution though, `pp` works just as well as PerlApp as far as I've seen. Just search it on CPAN. It compiles and installs pretty easily on Windows and Linux (just do the 'perl Makefile.pl; make; make install').
I actually just use pp for everything now. So I kinda recommend that. The whole Perl Dev Kit is pretty expensive when all you want from it is PerlApp.
-------------
Cuvou.com | My personal homepage
Project Fearless | My web blog
For a free solution though, `pp` works just as well as PerlApp as far as I've seen. Just search it on CPAN. It compiles and installs pretty easily on Windows and Linux (just do the 'perl Makefile.pl; make; make install').
I actually just use pp for everything now. So I kinda recommend that. The whole Perl Dev Kit is pretty expensive when all you want from it is PerlApp.
Code:
pp --icon myicon.ico source.pl binary.exe-------------
Cuvou.com | My personal homepage
Project Fearless | My web blog
Captainrave
Technical User
Perl2Exe is the best I have used so far. But as mentioned above there are plenty of free to use methods out there.
Well, as chipk said, that's pretty much how all the compilers work afaik.
Like App:
acker, pp and PerlApp really just create an archive that contains your copy of the Perl interpreter, all the modules and source codes that your Perl app uses, and bundles them together into an executable file that can stand on its own. On the first run, it extracts itself to a temporary directory and then runs a standard "perl sourcecode.pl" on the copy of perl.exe that it extracted to temp.
Apps compiled with pp, for instance, can be opened up in WinZip like a normal zip file, and browsed and extracted. AFAIK PerlApp does the same thing as pp, but automatically applies source code obfuscators (which pp can do as an option) so that if your code gets extracted from the binary, it'll be jumbled up and hard to decode unless you have a debugging version of Perl and really know what you're doing. Keeps the source code safe from the average prying eye, though.
I can't say how perl2exe does it but I imagine it follows the same pattern.
Having said that, a GUI application such as one that uses Perl Tk or wxPerl, will automatically be about 3 or 4 megabytes in size simply because they will need to bundle the entire Tk or wxPerl libraries inside themselves, respectively. They don't optimize the code like C or C++ do because Perl binaries aren't truly compiled into machine code.
-------------
Cuvou.com | My personal homepage
Project Fearless | My web blog
Like App:
acker, pp and PerlApp really just create an archive that contains your copy of the Perl interpreter, all the modules and source codes that your Perl app uses, and bundles them together into an executable file that can stand on its own. On the first run, it extracts itself to a temporary directory and then runs a standard "perl sourcecode.pl" on the copy of perl.exe that it extracted to temp.Apps compiled with pp, for instance, can be opened up in WinZip like a normal zip file, and browsed and extracted. AFAIK PerlApp does the same thing as pp, but automatically applies source code obfuscators (which pp can do as an option) so that if your code gets extracted from the binary, it'll be jumbled up and hard to decode unless you have a debugging version of Perl and really know what you're doing. Keeps the source code safe from the average prying eye, though.
I can't say how perl2exe does it but I imagine it follows the same pattern.
Having said that, a GUI application such as one that uses Perl Tk or wxPerl, will automatically be about 3 or 4 megabytes in size simply because they will need to bundle the entire Tk or wxPerl libraries inside themselves, respectively. They don't optimize the code like C or C++ do because Perl binaries aren't truly compiled into machine code.
-------------
Cuvou.com | My personal homepage
Project Fearless | My web blog
- Status
Similar threads