Just a note on this, remember to untick the main app target in Xcode
when adding other foundations tools like this or they will
automatically be added into the resources folder when your package is
built.
Untick the target when adding the file and then create a copy files
build phase to the "Executables" folder seems to be the right way to
do it.
Now to see if the tool actually works from there :D
On 2/21/08, Chris Suter <email@hidden> wrote:
>
> On 22/02/2008, at 7:41 AM, Nick Zitzmann wrote:
>
> > Just place it in either the Contents/MacOS or Contents/Resources
> > folder in your bundle & use NSBundle to get its path. It's pretty
> > simple, actually...
>
> With the advent of code-signing, auxiliary tools should not be placed
> in Contents/Resources. If it's a simple tool, it should be placed in
> Contents/MacOS. If it is itself a bundle, it should be placed in the
> Contents folder.
>
>
> - Chris
>
>
>
--
e-mail: email@hidden
web: http://shinydevelopment.com
Shiny Development Ltd. is registered in England, Registration Number:
05805802. Registered Office: 4 Claridge Court, Lower Kings Road,
Berkhamsted, Herts., HP4 2AF.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
