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: Matt DeFoor <email@hidden>
- Date: Wed, 31 Aug 2005 09:41:21 -0400
Scott Tooker wrote:
I've been working on this very problem (Xcode being to aggressive about
resolving symlinks), and I'm hopeful that in the next version of Xcode
file references will be able to point to symlinks correctly (instead of
getting resolved too early).
By far, the most important case I've run into is having a file
reference point to a symlink that represents the current library (like
below).
Are there other common uses of symlinks in paths that you have been
trying to get working in Xcode (but Xcode feverishly refuses to use the
unresolved path)?
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:
This email sent to email@hidden