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: Tue, 6 Nov 2007 13:22:15 -0600
On Nov 6, 2007, at 13:14:15, Rick Ballard wrote:
The Relative to Xcode folder path type should only be used for
references to content inside the Xcode folder. Since the generally
recommended practice has been for your project to contain a
reference to the file in your system, it should be an absolute path.
The SDK comes into play after a reference has been resolved to a
file on disk, so the path type won't affect how the SDK is applied.
If you were to add a file directly from an SDK to your project, as
DTS originally suggested, you would in that case want it to be a
Relative to Xcode folder path type. As Scott said, that's not been
our recommendation, and shouldn't be necessary, though I suspect
that it should actually work – the fact that the file type of such
references get set to "compiled.mach-o" instead of "compiled.mach-
o.dylib" is likely just a bug that hasn't generally been a problem
due to the fact that this isn't common practice.
Thank you very much. Now I need to type up these rules, print it out,
and hang it where I can find it again the next time I add stuff to a
project. :) Another reason why that suggestion of having Xcode present
a list of addable objects (a la the "Locate the app" list you get when
opening a script) would be a *great* feature to have.
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