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: Rick Ballard <email@hidden>
- Date: Tue, 6 Nov 2007 11:37:05 -0800
On Nov 6, 2007, at 11:22 AM, Steve Mills wrote:
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.
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.
Note also that Xcode tries to figure out the appropriate path type for
you so that you don't need to learn complicated rules in the first
place. When you create a reference to content that's under your Xcode
folder, the path type should be set automatically to Relative to Xcode
Folder, while other references should be set to Absolute or Relative
to Enclosing group or whatever the appropriate type for its location
is. If you are seeing Xcode make the wrong decision about the initial
path type, I'd file a bug.
- Rick
_______________________________________________
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