-framework vs add framework, dynamic search paths
-framework vs add framework, dynamic search paths
- Subject: -framework vs add framework, dynamic search paths
- From: Thijs Koerselman <email@hidden>
- Date: Mon, 27 Jul 2009 20:32:42 +0200
Hi,
I've developed this plugin (carbon loadable bundle) which uses one of my own frameworks. Before, I just added the frameworks to my projects in XCode and everything was fine. Recently I started using the -framework linker flag instead, and now my plugin can't find my framework anymore at runtime. Linkage and compilation is all good.
It seems that my plugin, when loaded, now only looks at the volume root, so I get an error about a missing image at /MyFramework.framework/Versions/A/etc.
The framework normally resides in /Library/Frameworks and apparently that's where the linker finds it when the plugin is being compiled. I now need to copy my framework to the root in order to make it work.
My guess is that XCode does some housekeeping when adding a framework to the project, which isn't done when I link to the framework with just the linker flag. What am I missing here?
Cheers, Thijs
_______________________________________________
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