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 Miner <email@hidden>
- Date: Wed, 29 Jul 2009 16:47:06 +0200
Am 27.07.2009 um 20:32 schrieb Thijs Koerselman:
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.
This is because the install location encoded into the framework is /
MyFramework.framework/Versions/A/etc. Because of this code linked
against this framework expects to find it there. You can't just put
it anywhere. Have a search for LD_DYLIB_INSTALL_NAME or -install_name.
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.
The compiler and linker will look where you are telling them to. Even
so, it will still build an executable
that expects to find the frameworks it is linked against in certain
places.
My guess is that XCode does some housekeeping when adding a
framework to the project,
when you launch your app from Xcode, it sets a DYLD_FRAMEWORK_PATH
environment variable which cause other libraries, potentially those
still in development to be used at run time rather than anything
installed. Otherwise you'd have lengthy build cycles as you
reinstalled your (still under development) frameworks after
every change.
_______________________________________________
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