Packaging up a perl program on win32

chorg has asked for the wisdom of the Perl Monks concerning the following question:

I love *nix! However, I have put on my tight top and short skirt and gone out to do some work for those high paying Windows people :)

What I need to do is make an app on win2k using Perl and give it to people in the company. However, being that most people are not Perl programmers, my managers and the like, may not have perl installed (horrors!) What steps would I need to take to provide an executable that I could just send to someone to use?
_______________________________________________
"Intelligence is a tool used achieve goals, however goals are not always chosen wisely..."

Comment on Packaging up a perl program on win32

Replies are listed 'Best First'.
Re: Packaging up a perl program on win32 by epoptai (Curate) on Feb 10, 2001 at 22:53 UTC
It's not perfect but check out IndigoStar's free perl2exe	[reply]
Re: Re: Packaging up a perl program on win32 by OeufMayo (Curate) on Feb 10, 2001 at 23:45 UTC
epoptai is right, but if your question is related to the other one you posted, be aware that Win32::GUI is not 100% reliable with perl2exe. -- Briac <kbd>-- PerlMonger::Paris(http => 'paris.pm.org');</kbd>	[reply]
(tye)Re: Packaging up a perl program on win32 by tye (Sage) on Feb 11, 2001 at 09:10 UTC
Within an organization, you can probably just pack up the script with pl2bat but change the two calls to perl to be calls to \\chorg-w2k\perl\bin\perl (assuming your desktop is called chorg-w2k and you make a read-only share of the directory where you installed perl and call that share "perl"). The way most WinNT/Win2K shops are set up, that will work just fine for most people you work with. As you produce more neat scripts in Perl, more people will install it on their machine or you can get a standard shared directory for Perl on one of the central file servers. Around here, just about everyone has perl installed (all of the developers do because our development tools require it). But the standard Perl doesn't include Tk so my Tk utilities run the local copy of Perl and then check if the needed modules are installed. If not, they switch to my shared copy of Perl. The cmd.exe of WinNT/Win2K is finally powerful enough that you can even detect whether they have Perl installed before you try to run your shared copy. - tye (but my friends call me "Tye")	[reply]