[platypus-dev] Re: platypus in installer
- From: Sveinbjorn Thordarson <sveinbt@xxxxx>
- To: platypus-dev@xxxxxxxxxxxxx
- Date: Wed, 18 Jan 2006 12:31:32 +0000
On Jan 18, 2006, at 12:23 PM, Vincent Neyt wrote:
I have been using your wonderful platypus software. I am working on
a cd-rom that has an Apache Tomcat on it. Users have to install it
and once it is up and running people can use my dynamic web
application. For mac users, I have found a way to bundle the whole
startup shell stuff in one nice Platypus app, so that users simply
have to click the app to start everything up.
Now when i create the app, it works like a charm. but then when I
compile my installer, and run that installer and start the app from
the directory it has been installed in, it never works, and i cant
get it to.
from your help file i have inserted the code to change the working
directory to the directory where the app is, so that shouldnt be
the problem.
the only thing i can imagine that might be causing this, is that
maybe when I create the app, the directory structure is hard coded
into the executable portion of the app, and doesn't work whenever
it is installed into another directory.
Do you have any idea what the problem could be and how to solve it?
The only path that's hardcoded into Platypus apps is the standard
application bundle directory structure, i.e.
MyApp.app/Contents/
MyApp.app/Contents/Resources
MyApp.app/Contents/MacOS
and so on. It receives the path to the application bundle is
received in the first argument to the script. In order to access the
contents of the application bundle, you need to change your working
directory to the first argument -- this puts you inside MyApp.app.
Does your Platypus app output anything? Take a look at the system
logs in Console.app. I'd recommend that you try making your script
output debugging info, e.g. 'echo $CWD', test everything carefully in
your script code.
Cheers,
Sveinbjorn Thordarson
Other related posts:
