Hi Tim & Michael,<br><br>Thanks for looking into this. The idea to install the applet to ../MacOS works fine. Now I just have to get the linking fixed and the bundle should be working.<br><br>Thanks a lot.<br><br>Cheers,<br>
Tobias <br><br><div class="gmail_quote">On Fri, May 29, 2009 at 8:23 PM, Timothy M. Shead <span dir="ltr"><<a href="mailto:tshead@sandia.gov" target="_blank">tshead@sandia.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>Michael Jackson wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
On May 29, 2009, at 11:49 AM, Timothy M. Shead wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tobias Sauerwein wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Everyone<br>
In my attempt to get cmake/cpack to produce a propper OS X bundle, I hit a problem. We use a launcher script written in applescript which is compiled in the build process. Before producing the bundle with cpack we simply copied the compiled 'applet' file over to the actual bundle. When I set CPACK_BUNDLE_STARTUP_COMMAND to point to the applet it is getting copied over but renamed to the bundle name. Can I prevent that somehow or can I run a script right after cmake/cpack has finished putting the bundle together to do some final touches?<br>
</blockquote>
Tobias:<br>
<br>
My experience when I was writing the bundle generator was that the startup command only worked if it matched the bundle name. From your question there must be some way to control what gets executed when a user double-clicks the bundle. Info.plist?<br>
<br>
Cheers,<br>
Tim<br>
<br>
-- <br>
Timothy M. Shead<br>
Data Analysis & Visualization (1424)<br>
Sandia National Laboratories<br>
505-284-0139<br>
</blockquote>
<br>
from inside the info.plist:<br>
<br>
<key>CFBundleExecutable</key><br>
<string>QImporter_debug</string><br>
<br>
You can set that to what ever you want. I'm pretty sure that the executable _should_ be in the "MacOS" directory otherwise you can probably put in a relative path: "../bin/myexecutable"<br>
</blockquote>
<br></div>
Cool ... so I think a workable solution for Tobias would be to leave CPACK_BUNDLE_STARTUP_COMMAND empty, ensure that the Info.plist specified with CPACK_BUNDLE_PLIST runs the correct applet file, then use<br>
<br>
INSTALL(FILES /path/to/applet DESTINATION ../MacOS/applet)<br>
<br>
to put the applet where it belongs in the bundle, without renaming it.<br>
<br>
Since the bundle generator relies on the user to generate their own Info.plist anyway, it sounds as if renaming the startup command is heavy-handed and should be replaced with a straight copy.<div><div></div><div>
<br>
<br>
Cheers,<br>
Tim<br>
<br>
-- <br>
Timothy M. Shead<br>
Data Analysis & Visualization (1424)<br>
Sandia National Laboratories<br>
505-284-0139<br>
<br>
</div></div></blockquote></div><br>