Re: XCode 2.1 and building for 10.2.8
Re: XCode 2.1 and building for 10.2.8
- Subject: Re: XCode 2.1 and building for 10.2.8
- From: Daniel Hazelbaker <email@hidden>
- Date: Wed, 31 Aug 2005 08:24:57 -0700
If I understand your problem correctly, and that you are still
having it, what I have had to do in the past with similar problems is
to drag the "older" version of the library (i.e. /usr/lib/
libssl-0.9.dylib) into the library list. Obviously this is not the
correct solution (and -lssl should work with SDKROOT set, not sure
why it isn't), but it does work.
It is possible that this is an ld bug in not properly dealing
with the -isysroot (or whatever its called) parameter to tell it
where to get the system libraries from and not directly an XCode
problem, but that is entirely speculation.
Daniel
On Aug 31, 2005, at 6:41 AM, Matt DeFoor wrote:
I pretty much only do this with dylibs in /usr/lib. However, Sean's
suggestion of adding -lcrypto and -lssl have not resolved the
problem entirely. The binary will build and link, but otool -L
reveals that it is linked against:
/usr/lib/libcrypto.0.9.7.dylib
/usr/lib/libssl.0.9.7.dylib
Obviously, this is not what I want. I have specified Mac OS X
10.2.8 as the cross develop target SDK, yet XCode insists on
linking things incorrectly. I'm probably just doing something wrong.
In the past I've been able to cobble a method together in XCode 1.2
on 10.3.9 to build for 10.2.8, but I'd like to stick with one
version of XCode for all project builds if possible.
--
/* Matt DeFoor */
Listening to the sound of silence
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40highdesertchurch.com
This email sent to email@hidden
_______________________________________________
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