You will no doubt get a few more specific responses, but all I'm aware of concerning compiled perl code is on Win32, and perlcc of which both will include required modules. You can get PerlApp from ActiveState and perlcc is part of the default distro. To get more information on perlcc try: perldoc perlcc on the command line.
IMHO I would research the possibility of installing Perl on your servers or maybe look at a NFS/Samba solution though that may certainly be difficult with the plethora of platforms you work with.
BlackJudas | [reply]
[d/l] |
Thanks for the recommendation with perlcc, it looks like it will do the job.
I would love to have perl on all of the servers (life would be so much easier...) Alas I don’t get to control that.
Could you elaborate a little more on the nfs/samba solution your talking about? Do you mean for the test I am writing or the perl install? I had never thought about this before, but It would make things a lot simpler...
Thanks for your help.
Josh
| [reply] |
"If i use LWP::Simple will it still work on a machine that doesn’t have perl installed?"
I don't know about this specific module, although it *should* work just fine, at least with ActiveState's PerlApp
I have had very good luck with Net::Syslog, Net::Ping, Net::Telnet, Getopt::Long, and several other modules when "compiling" (probably better stated as Packaging) with PerlApp.
I have stated before, and will reiterate now, that ActiveState's PerlApp is well worth the money of the Perl Dev Kit if you are doing many small apps for Win32 systems that will be distributed to many people. Unix's have the advantage of having Perl "native" (most of the time) and that way as long as you package the modules with the script you should be OK (obviously it would still need to be tested :), but for Win32, go with PerlApp for wide distribution.
"Nothing is sure but death and taxes" I say combine the two and its death to all taxes! | [reply] |
I've tried both PDK (PerlApp) from ActiveState and Perl2Exe from IndigoStar. Here are a few of the things I've found:
Perl2Exe compiles code for more platforms than PerlApp.
Programs compiled with Perl2Exe have smaller file sizes than those compiled with PerlApp.
Programs compiled with Perl2Exe have smaller memory foot prints than those compiled with PerlApp.
Programs compiled with PerlApp tend to load in memory faster than those compiled with Perl2Exe.
Programs compiled with Perl2Exe garbage collect faster than those compiled with PerlApp.
Neither product has very good tech support (I've received more help here than at either site).
Perl2Exe is less expensive than PerlApp.
One thing to keep in mind is that I evaluated the products before I purchased. Both products say they do not require purchase before running at production quality. I took this to mean that the products would not get better upon purchase. My final decision was Perl2Exe. I have never had trouble with Perl2Exe not getting a library to compile (and be portable).
This is just my experience. Others may have experienced different. | [reply] |