I actually gave up and use cygwin for myself and have strawberry perl to make distributables. Strawberry works good because it doesn't require any cygwin dll's and doesn't require the full path.
The cons of strawberry are: 1. 2 processes when it runs. This can cause orphaned processes depending on how you kill it. 2. alarm doesn't work 3. chmod doesn't work Pro's 1. icon and fileversion can be set A con of cygwin is that if a different version of cygwin is on the target machine then it wont work if any process is running. All of the cons for strawberry are there for all win32 perl's > -----Original Message----- > From: Chris Mason [mailto:[EMAIL PROTECTED] > Sent: Friday, November 07, 2008 9:21 AM > To: Robert Davis > Cc: par@perl.org > Subject: Re: :Packer Problem under Cygwin > > Hi Robert, > > Thankyou! > That seemed to do the trick, but when trying to distribute a program I > would struggle to get the end user to invoke my program by having to > specify the full path. > > Based on your suggestion I did the following: > > set PATH=$PATH:. > > Which also has the same effect and it works with this. > > I don't know the inner workings of PAR to understand why it needs this, > but adding "." to the path is never a good idea. Is anyone able to > provide any insight into why this might be happening? > > Thanks, > Chris > > Robert Davis wrote: > > Try giving the full path c:/exedir/test.exe or ./test.exe > > I ran into this problem and never figured out what the difference was. > > > > > >> -----Original Message----- > >> From: Chris Mason [mailto:[EMAIL PROTECTED] > >> Sent: Friday, November 07, 2008 7:29 AM > >> To: par@perl.org > >> Subject: PAR::Packer Problem under Cygwin > >> > >> Hi All, > >> > >> I am hoping that you can answer what I think is a very simple question > >> regarding PAR::Packer. I am using the "pp" utility to package up a > > Perl > >> program under Cygwin on Windows XP using the following syntax: > >> > >> pp -o test.exe test.pl > >> > >> This produces test.exe which depends on various cygwin dlls. If I > >> attempt to run test.exe by double clicking on it from within Windows > > it > >> works fine, but if I attempt to run it from a Windows command prompt > >> (cmd.exe) then I get the following output: > >> > >> Usage: test [ -Alib.par ] [ -Idir ] [ -Mmodule ] [ src.par ] [ > > program.pl ] > >> test [ -B|-b ] [-Ooutfile] src.par > >> > >> I can't think what the difference is between running a program by > > double > >> clicking on it versus running it from a command prompt? Has anyone > > else > >> seen this problem before or know what I am going wrong? > >> > >> Thanks, > >> Chris > >
