Re: Link errors
Re: Link errors
- Subject: Re: Link errors
- From: Steve Mills <email@hidden>
- Date: Tue, 7 Feb 2006 09:23:08 -0600
On Feb 6, 2006, at 23:56, Chris Espinosa wrote:
As Peter says, these are common system symbols that are usually
found in the system libraries you link with. ZeroLink hides link
errors until runtime; it's more useful when you're making code
changes to a running program than when you're doing configuration.
And the main reason that your Intel side would get these errors
would be if you didn't or couldn't link with Intel libraries, i.e.
you have not set the SDK to 10.4 (Universal).
Then something is hosed. All the projects are using the 10.4u.sdk and
the Debug config's architecture is set to $(NATIVE_ARCH). Oh wait.
Somehow a couple libraries that were moved over from a previous
subproject (which is now integrated into the main project) are coming
from the 10.3.9.sdk instead of /System/blah. However, I'm still
getting the same link errors as I was getting after turning off Allow
ZeroLink. Included are a bunch of SSL routines, and we have /usr/
liblibssl.0.9.dylib in the project and included in the targets, as
well as Security.framework and others. Arg. I guess I'll try another
clean and build. Bleah.
Let me make sure I'm doing this correctly: When adding a system lib
or framework, I navigate to the current OS's folder (/usr/lib or /
System/Library/Frameworks) and add them from there. Xcode then maps
the lib or framework with the project's current .sdk, right? So when
I Get Info on a lib or framework, its path should always be an
absolute path to the current OS file and not to the .sdk, right?
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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