Duncan Murdoch wrote:
>
> 1. Is it possible to install scripts in subdirectories of script/
> within the .par file? I'd like to run them as
>
> parl foo.par subdir/baz.pl
>
> This will let us keep the same organization of scripts as we have now.
this is very similar on how I did par-packaging last time.
I have some utility scripts for one directory, so I wrote some "wrapper"
script, which calls either of selected scripts, which checks its
executable name and selects the script to run. ("busybox" strategy)
So I got several executables which unpacks into the same directory
within %TEMP%\par\... thus saving the space.
(these scripts even had VIM packaged within their PAR!)
>
> 3. Can pp be packaged into a self-contained .exe file, or a .par
> file? I tried, but when I was using it it complained. I did
>
> pp.bat -o pp.exe pp
>
> and then in the same directory under CMD.EXE things look okay, but
> when running elsewhere under Cygwin, I see
>
> $ pp rwver.pl
> Module/ScanDeps.pm did not return a true value at PAR/Packer.pm line 35.
> BEGIN failed--compilation aborted at PAR/Packer.pm line 35.
> Compilation failed in require at pp.pm line 5.
> BEGIN failed--compilation aborted at pp.pm line 5.
> Compilation failed in require at script/pp line 5.
> BEGIN failed--compilation aborted at script/pp line 5.
>
> Is Cygwin the problem here?
I'm not able to answer your concrete answer due to lack of PAR+cygwin
experience, but I want to say that you must be extremely careful when
using Perl's from two different world's - cygwin's perl is incompatible
with AS perl.
(note that you can build extensions for AS perl with GCC from cygwin,
but you must 1. change Config.pm properly and 0. use -mno-cygwin option)
Best regards,
Vadim.
