Re: Private frameworks
Re: Private frameworks
- Subject: Re: Private frameworks
- From: Eric Albert <email@hidden>
- Date: Sat, 12 Nov 2005 14:22:49 -0800
On Nov 12, 2005, at 11:55 AM, Red Marble Games wrote:
My app has a couple of frameworks that I prefer to include in the
application bundle rather than installing into ~/Library/Frameworks.
I have added them to the project and to the Frameworks directory in
the app's bundle, and can build and link just fine, but when I try to
run the app, dyld can't find them -- the console message says it's
looking in ~/Library/Frameworks. I assumed the app would be smart
enough to look in its own Contents/Frameworks -- is there some setting
I have to enable to get the proper behavior? Sorry for the newbish
question, but I have looked all over and read a lot of documentation
and can't seem to figure this out.
See "Creating a Private Embedded Framework" at
<http://developer.apple.com/documentation/MacOSX/Conceptual/
BPFrameworks/Tasks/CreatingFrameworks.html>. Basically, you want to
set the "install name" of each of the frameworks to point inside your
application package, and then dyld will find them at runtime.
Here are two tips which might come in handy while you're doing this:
-You can use 'otool -L' to see which install names a given binary will
look for at runtime
-You can use 'otool -D' to see the install name for a library or
framework
-You can use 'install_name_tool' to change the install name of a
library or framework, or to point a binary to a different install name
for a library or framework it links against
Hope this helps,
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden