• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: #define bug in gcc for delta builds?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 19:46:10 +0700

Hi Steve,

My guess now is that Xcode isn't doing dependency tracking for for that header. For example:
foo.h contains the declaration of class foo
foo.cpp contains the implementation of class foo
user.cpp #includes foo.h and uses class foo.

Interesting.

The incremental compile compiles user.cpp and foo.cpp. Then you change comment out the _FOO_ define which causes Xcode to mark foo.cpp as dirty but not user.cpp so when it gets recompiled, they have different ideas about the size of foo.

But if user.cpp and foo.cpp both include foo.h and I comment out the #define (which is in foo.h) surely that would be flagged correctly?


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.

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.

Again, what I am doing seems to follow the rules I understand, but perhaps I am missing something obvious.

Hi Ken,

Have you tried what somebody else suggested: put a #error line in the text which is supposed to be excluded by the #ifdef test?

No not at the moment. It will only tell me what I already know. That both the stuff which should be conditionally excluded and the stuff I actually want to compile is getting compiled at some point in the build.


I guess knowing where that happens in the build order would be a good way to track where the confusion happens and may be useful though.

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


  • Follow-Ups:
    • Re: #define bug in gcc for delta builds?
      • From: Steve Checkoway <email@hidden>
References: 
 >#define bug in gcc for delta builds? (From: Stephen Northcott <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Steve Checkoway <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Stephen Northcott <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Steve Checkoway <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Stephen Northcott <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Steve Checkoway <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Stephen Northcott <email@hidden>)
 >Re: #define bug in gcc for delta builds? (From: Steve Checkoway <email@hidden>)

  • Prev by Date: Re: #define bug in gcc for delta builds?
  • Next by Date: making resource 'MENU' processor independent
  • Previous by thread: Re: #define bug in gcc for delta builds?
  • Next by thread: Re: #define bug in gcc for delta builds?
  • Index(es):
    • Date
    • Thread