Le 27 nov. 08 à 10:35, Luke Evans a écrit :
I've had a need, for the first time, to have a private framework in
a bundle that gets loaded into an app.
Now, I've done a bit of framework wrangling in the past, and thought
it might involve getting the installation path in the framework
build/packaging right in order to do this.
When the usual @executable_path/../Frameworks didn't work
(presumably because I'm in a bundle now, loaded from a location
elsewhere in the files system than the app bundle), I read about
@loader_path and assumed that an installation path of
@loader_path/../Frameworks would do the job here. Indeed this
causes the bundle to load properly, whereas before I was getting an
error about finding the framework's executable image. However, when
I first make a call to a framework things crash and burn.
Could you detail a little more "crash and burn" ? (crash log, message,
anything usefull…)
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
