Re: Xcode 2.5 can't #include_next <stdarg.h>
Re: Xcode 2.5 can't #include_next <stdarg.h>
- Subject: Re: Xcode 2.5 can't #include_next <stdarg.h>
- From: Steve Mills <email@hidden>
- Date: Mon, 5 Nov 2007 09:45:19 -0600
On Nov 3, 2007, at 21:09:44, Chris Hanson wrote:
On Nov 2, 2007, at 10:39 AM, Steve Mills wrote:
It was when opening the 2.4 project in 2.5, then changing the libs
to come from /Xcode2.5/SDKs/MacOSX10.4u.sdk/usr/lib/ instead of /
usr/lib/.
Don't do this; the libraries should continue to come from /usr/lib,
not from the SDK directory.
Essentially, the rule is: Add items to Xcode from the root
filesystem, let Xcode pull them from your specified SDK for you.
It works this way because essentially all of the tools that Xcode
uses implement a mechanism like -isysroot, which tells the tool
(like the compiler or the linker) to use a different directory
than / for its root. Thus when you specify $(DEVELOPER_SDK_DIR)/
MacOSX10.5.sdk as your SDK, you're really saying to the tool set
"use this directory instead of / when looking for headers and
libraries."
Now I'm confused. I used a support incident to figure out why our app
would not load in some of the 10.5 seeds. During that exchange I was
told to use the sdk libs, NOT the OS libs.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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