Re: Creating Standalone Win32 Executable
by Anonymous Monk on Jul 20, 2012 at 08:20 UTC
|
That sounds suspicious, what did you install exactly?
After you build an exe with pp -x ... try it out locally by first using set path= then myexe.exe
| [reply] [d/l] |
|
Thanks for the reply. I actually did not use the -x option. I did 'pp -o a.exe b.perl'. I installed the module 'PAR-Packer-1.013'
| [reply] |
|
| [reply] |
|
I installed the module 'PAR-Packer-1.013' You said that in your original post, you should be more specific
| [reply] |
|
|
Re: Creating Standalone Win32 Executable
by marto (Cardinal) on Jul 20, 2012 at 09:15 UTC
|
I received your /msg asking for help with this. I had read the post, and the replies, I'm not sure what I can add to the existing answers, but here we go.
Consider running with the -x option:
pp -x myscript.pl
Then test the executable created. Please read and understand the pp documentation and http://par.perl.org. If you have further problems please provide more details.
| [reply] [d/l] |
|
Hi... I got it running in the client machine after copying the per514.dll file from my machine to the current folder of the client machine where there is no Perl installation :) However, please let me know if somehow I could make the dll file included in the exe itself.
By the way, it seems pp does check for all the dependencies and included them while making the exe.
| [reply] |
|
| [reply] [d/l] |
|
-l, --link=FILE|LIBRARY
Add the given shared library (a.k.a. shared object or DLL) into th
+e packed file. Also accepts names under library paths; i.e. -l ncurse
+s means the same thing as -l libncurses.so or -l /usr/local/lib/libnc
+urses.so in most Unixes. May be specified multiple times.
| [reply] [d/l] |
|
|
|
|
|
Re: Creating Standalone Win32 Executable
by Anonymous Monk on Jul 21, 2012 at 06:52 UTC
|
| [reply] |