Re: Linking statically when a dylib exists
Re: Linking statically when a dylib exists
- Subject: Re: Linking statically when a dylib exists
- From: Chris Espinosa <email@hidden>
- Date: Fri, 15 Jul 2005 07:56:22 -0700
On Jul 15, 2005, at 3:21 AM, Jerry wrote:
I know this has been asked before, but not as far as I know since
XCode 2 so maybe something has changed...
Is there any solution to the problem of XCode linking to foo.dylib if
you add libfoo.a to your project? Removing the dylib is not a
particularly good option as other applications on the system rely on
it, and I'd like to avoid fragile solutions such as shell script build
phases.
This is baked-in gcc behavior, and the only way I've found in Xcode to
override it is to add the full path to the file, including extension,
in a -l directive in Other Linker Flags (e.g. -l/usr/local/lib/foo.a)
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