I use perl2exe. You can get a basic version for $49, or the Pro version for $149.
I looked at the ActiveState product a couple of years ago when it was young, and I preferred perl2exe because it was cheaper and more reliable, and it produced smaller EXEs. Of course ActiveState may have come a way since then... I've also found the author pretty responsive when I've emailed him questions. It's at http://www.indigostar.com/perl2exe.htm Keep in mind that both of these "compilers" are really just packagers; they don't give you any size or performance advantages over naked perl scripts. I use perl2exe because it lets me not care about the version of Perl that might be on a foreign system, it lets me use obscure (uninstalled) modules on foreign systems, and it (I hope) obscures my source code when that is needed. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Vandiver Sent: Monday, February 18, 2002 1:21 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Boston.pm] activestate perl On Mon, 2002-02-18 at 01:09, [EMAIL PROTECTED] wrote: > [snip] > I'd like to know if there'll be some cheese at the end before > I go too far down the tunnel. I have and use their PDK semi-regularly (thanks to their educational discount). It takes in a .pl file, and dumps a windows executable out the other end; no other tools are needed. The files that it creates are rather large (~ 1meg for a rather bare bones program) but that is to be expected as it needs to squeeze your source, most (if not all) of the perl interpreter, and all modules that your script uses into one file. Actually, the statistic of ~1 meg was for PDK 3.0, and they claim to have managed to shrink the output files down quite a bit since then. Best o' luck, - Alex V. -- Networking -- only one letter away from not working.
