interesting read, and it did help me a lot. turns out that "foo" did
have the install name set yo @executablename/../Frameworks/<...> ( not
sure how that got there ;) and the newer "bar" did not. changed that,
and its all working now.
so i guess that means a framework is either compiled to be deployed
externally *or* included in .app bundles, but the app developer cannot
simply choose to do either, as he pleases? odd design choice, i would
have expected the OS to just try a series of locations (such as, in
the app bundle, then ~/Library, then /Library...
anyways, thanx a lot!
marc
On Jun 28, 2008, at 9:43 PM, Greg Guerin wrote:
marc hoffman wrote:
i cannot see any tangible difference between the two projects
(except that one references the other), and they were both added to
the app project in the same way [i tried this with several apps,
both show the same behavior - so i'm fairly certain it's not a
misconfig in my app project].
What is the install-name for each of the frameworks? If you don't
know, use 'otool -L' and 'otool -D' on the lib-file.
See my recent lecture, er posting, regarding link time and install-
names:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
