FROM : Jean-Daniel Dupas
DATE : Thu Feb 21 22:02:52 2008
Le 21 févr. 08 à 21:41, Nick Zitzmann a écrit :
>
> On Feb 21, 2008, at 10:09 AM, Dave Verwer wrote:
>
>> This is unfortunate because it seems that it does exactly what I
>> need,
>> so I had the thought to bundle it inside my app package and use it
>> from there. I realise I could cobble together the core audio
>> frameworks to do what I want as well but why reinvent the wheel eh?
>>
>> Are there any best practices when bundling foundation tools?
>
>
> 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...
>
> Nick Zitzmann
> <http://www.chronosnet.com/>
As you ask about good practice, you should note this (from the Code
Signing Release Notes):
Do not put helper applications, plugins, and other separately signed
code into the Resources directory of a bundle. The Resources directory
is directly sealed to the main executable. Put plugins into the Plug-
Ins directory. Put helper tools into the executable directory. Put
helper applications (with their own bundles) into the support directory._______________________________________________
Cocoa-dev mailing list (<email_removed>)
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_removed>
This email sent to <email_removed>
DATE : Thu Feb 21 22:02:52 2008
Le 21 févr. 08 à 21:41, Nick Zitzmann a écrit :
>
> On Feb 21, 2008, at 10:09 AM, Dave Verwer wrote:
>
>> This is unfortunate because it seems that it does exactly what I
>> need,
>> so I had the thought to bundle it inside my app package and use it
>> from there. I realise I could cobble together the core audio
>> frameworks to do what I want as well but why reinvent the wheel eh?
>>
>> Are there any best practices when bundling foundation tools?
>
>
> 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...
>
> Nick Zitzmann
> <http://www.chronosnet.com/>
As you ask about good practice, you should note this (from the Code
Signing Release Notes):
Do not put helper applications, plugins, and other separately signed
code into the Resources directory of a bundle. The Resources directory
is directly sealed to the main executable. Put plugins into the Plug-
Ins directory. Put helper tools into the executable directory. Put
helper applications (with their own bundles) into the support directory._______________________________________________
Cocoa-dev mailing list (<email_removed>)
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_removed>
This email sent to <email_removed>
| Related mails | Author | Date |
|---|---|---|
| Dave Verwer | Feb 21, 18:09 | |
| Nick Zitzmann | Feb 21, 21:41 | |
| Jean-Daniel Dupas | Feb 21, 22:02 |






Cocoa mail archive

