Re: #define bug in gcc for delta builds?
Re: #define bug in gcc for delta builds?
- Subject: Re: #define bug in gcc for delta builds?
- From: Stephen Northcott <email@hidden>
- Date: Wed, 4 Feb 2009 20:01:42 +0700
Is the header file included in the Xcode project? I don't know if
it has to be included in the particular target or not, but I seem
to recall that it doesn't.
No. It is only included in the two or three files that reference it.
You need to include it in the project (but apparently not in the
target). That's what's causing Xcode to not do dependency tracking
for it and causing the problems you're seeing.
Ok. I think I understand that.
When you say include it in XCode, can you treat me like a dumb-ass and
explain what you mean.
It's part of the XCode project. It's actually a header file created in
XCode and written there...
Ultimately it will be moved to the Common Includes, but for now I
didn't want it to force the whole project to be rebuilt each time I
changed it.
I don't know what you mean by Common Includes.
Just my own files for keeping headers and defines in one place once
code is finalized.
I suspect in effect I am shadowing XCode's dependency tracking there.
Again, what I am doing seems to follow the rules I understand, but
perhaps I am missing something obvious.
You're following the c++ rules, but apparently not the Xcode rules.
Hmm.. This brings to mind the age old argument about what is a
"feature" and what is a "bug". ;-)
Thanks for spending so much time discussing this.
I am amazed that I haven't been bitten by this before.
Kind regards,
Stephen.
_______________________________________________
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