Aliases or Links in Contents/Resources?
Aliases or Links in Contents/Resources?
- Subject: Aliases or Links in Contents/Resources?
- From: Jerry Krinock <email@hidden>
- Date: Fri, 23 Dec 2005 11:16:43 -0800
- Thread-topic: Aliases or Links in Contents/Resources?
I am adding a "background agent" to my application; it will reside in the
main project's Contents/Resources folder. (I am following what Apple did
with iTunes.app/Contents/Resources/iTunesHelper.app.)
Because it is an application, the background agent package has its own
Contents/Resources folder where it expects to find its resources. It needs
to use some of the same resources that the main app does, but rather than
packaging two copies of these resources I think the design would be cleaner
using hard links, symbolic links or aliases.
So far, experiments show that for an .aiff resource to be accessed by
NSSound, the hard link and the alias work OK but the symbolic link does not.
I'm having trouble with the .icns, but that may be due to Finder vaguaries.
This seems like a question that might have correct answer and many
almost-correct answers which will bite me later. Is there a proper way to
do this cross-reference resources within a compound package?
Jerry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden