On Apr 14, 2004, at 11:21 PM, Steven Palm wrote:
I am trying to use PAR to build a MacOS X application bundle of a program developed using wxPerl.
If I use "pp -o myprog myprog.pl", it creates a binary that runs OK on my development machine. However, if I try to give it any commandline parameters, it starts to launch and then dies giving me this error:
RegisterProcess failed (error = -50) Abort trap
Also, if I attempt to put this created binary into an application bundle I get the same error in the console.log.
I was able to change my application bundle to use a shell script instead of launching the 'pp' created binary directly. This launches it (still no support for command line params, but not important at this stage), but still there are issues...
It seems the standalone binary created by 'pp' doesn't respect the DYLD_LIBRARY_PATH variable set by the shell. This is my launcher script in the myprog.app bundle:
#!/bin/sh
MYPATH="${0/myprog/}"
RESPATH="${MYPATH/MacOS/Resources}"
FWPATH="${MYPATH/MacOS/Frameworks}"export DYLD_LIBRARY_PATH=$FWPATH cd "$RESPATH" exec ./myprog
Where myprog is the 'pp' created standalone executable. I get dyld: errors claiming that it cannot open the library from it's original location on the development machine (/usr/local/lib in this case).
If I put the myprog.pl into my .../Resources directory along with all required perl modules as well, it works as expected and fetches it's shared libraries from the application bundle's framework directory.
Closer, but still not quite there yet....
