Re: Forcing Xcode to prefer a specific dylib
Re: Forcing Xcode to prefer a specific dylib
- Subject: Re: Forcing Xcode to prefer a specific dylib
- From: Jean-Daniel Dupas <email@hidden>
- Date: Thu, 17 Apr 2008 17:12:01 +0200
Le 17 avr. 08 à 16:43, Jerry a écrit :
On 17 Apr 2008, at 13:04, Jean-Daniel Dupas wrote:
Compile on 10.4… I don't understand why choosing SDK = 10.4 in the
projet settings on Xcode 3 (or even on Xcode 2.5) is an hassle ?
I have the same problem, but we also need to use Core Text if it's
available so we have to build on 10.5.
What did you try with install_name_tool ?
Changing the libcurl path from /usr/lib/libcurl.4.dylib to /usr/lib/
libcurl.3.dylib in the final product should work too.
install_name_tool -change /usr/lib/libcurl.4.dylib /usr/lib/libcurl.
3.dylib finalProduct
This doesn't work - it complains about the compatibility version
being wrong at runtime.
My solution was to download the libcurl sources, build 'em, and link
statically. That's a whole new world of pain, but it works. We have
to do this for Windows anyway, so we already had the source.
Jerry
That's what I'm doing too. The fact that UNIX libraries does not
declare functions using the availability macros make them unusable for
cross version projects.
"whole new world of pain" like how to tell Xcode to use the static
library instead of the dylib. (my solution is to not name my static
library libcurl.a but something like libscurl.a. It avoid conflict
with the system library).
And if you need sources of a Darwin component (like curl), you can
often find them on the Apple site: http://www.opensource.apple.com/darwinsource/10.5.2/
_______________________________________________
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