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: Scott Tooker <email@hidden>
- Date: Tue, 6 Nov 2007 11:20:11 -0800
On Nov 6, 2007, at 11:02 AM, Steve Mills wrote:
On Nov 6, 2007, at 12:48:55, Steve Mills wrote:
On Nov 6, 2007, at 12:26:40, Scott Tooker wrote:
As I understand it, you want to add the symlink from the base OS and
then set your SDKROOT appropriately. I can't think of a good
reason to
directly add content from the SDK, since SDKROOT will (effectively)
get prepended to all paths.
As far as the symlink goes, the SDK should have it's symlink
pointing
to the right version, so you should be clear there.
OK, thanks. I guess I'll change them all back again.
So what should the Path Type be? Note that all Xcode 2.4's will be
updated to 2.5, so the Relative to Xcode folder Path Type will be
available. Should that be used to Xcode can locate the .dylib
or .framework in the correct SDK folder? Or is Absolute Path good
enough?
For references into the base system, Absolute Path is just fine. Where
the Absolute Path type starts to burn you is when you are referencing
content that exists under a "well known mobile location" like the
project folder, build results folder, or a source tree.
Scott
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
_______________________________________________
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