Re: -framework vs add framework, dynamic search paths
Re: -framework vs add framework, dynamic search paths
- Subject: Re: -framework vs add framework, dynamic search paths
- From: Chris Espinosa <email@hidden>
- Date: Mon, 27 Jul 2009 12:59:40 -0700
On Jul 27, 2009, at 11:32 AM, Thijs Koerselman wrote:
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?
Xcode does indeed add the path to the framework to the target's
Framework Search Paths build setting, which then causes that path to
be passed in an -F directive. If you are linking via Other Linker
Flags, you need to manually add the path to the framework in Framework
Search Paths.
Chris
_______________________________________________
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