|Think about Loose Coupling|
Re: PAR/pp vs. PerlApp et al.by jdtoronto (Prior)
|on Nov 22, 2006 at 21:42 UTC||Need Help??|
Okay, I'll bite! Since no-one else has.
I have used all these products. PAR is possibly the best of the others. I use PerlApp all day every day and release currently five products using it. I also use PerlTray for creating a service tray application.
perlbin is by crazyinsomniac who seems to have disappeared in recent times, it was last updated in 2002.
perlcc is said to be very experimental, does not provide for binding additional files and has not support for GUI's specifically so that you cannot turn off the console window in Win32.
perl2exe is proprietary and generally seems to lag a little behind the current Perl release.
But there is a reason I use PerlApp, and it isn't just that I have a Komodo licence either! It handles the binding of additional modules and other files very well. You can easily handle extraction from within your code. It also allows you to create applications that dep[end in part on the Perl installed on teh target machine and you can share the contents of packaged applications to reduce total package size for the installation. The Perl Dev Kit (PDK) has a unified suite of applications for creating exe's, tray app's, services, installers and even COM objects. It has good support and all of the little annoyances I found with PAR are dealt with in PerlApp.
Rather than compiler, I use the term "packager".