BUG or unknown feature in pp: dll files are not extracted
-a is for data, -l is for dlls
... cygwin1.dll ...
mingw perl uses
$ perl -V:sh sh='/bin/sh';
IIRC cygwin uses the same thing (but its been a long while since I cygwin)
win32 perl uses
$ perl -V:sh sh='cmd /x /c';
So once you pack with par/pp into an .exe, it can't find /bin/sh, because it doesn't exist (the .exe doesn't know about the cygwin enviroment/$PATH etc, its a win32 program), or /bin/sh doesn't know how to call a .batch file
In short, avoid the shell, or call the right shell
I haven't the time to post a working example , but I you should be able to gain some wisdom by reading these
Re: Problem in creating exe using PAR module, Re^2: Packaging Perl Programs (is) Painful, Re: Building a Mojolicious app with PAR::Packer
Re: Pack multiple scripts in executables with one shared core dll
Re: system() implementation on Windows (again), Re^3: system() implementation on Windows (again)
http://blogs.msdn.com/b/twistylittlepassagesallalike/archive/2011/04/23/everyone-quotes-arguments-the-wrong-way.aspx# Everyone quotes command line arguments the wrong way
In reply to Re^3: Par Packer - gui option problems
by Anonymous Monk
in thread Par Packer - gui option problems
by Dirk80
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |