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 18:23:03 +0700
Hi Ken,
Thanks for your reply.
I would do a clean build and record the build commands, then do an
incremental build and compare the build commands for the relevant
translation units (the one where the class is implemented and the
one where it's being used). Do the build commands differ between
the clean and incremental builds?
Will do.
Second, if this involves header files and preprocessing, I suspect
problems with precompiled headers. You could try disabling their
use to see if that makes the problem go away.
Basically it's a #define which is in the header file of a specific
class.
That #define is only ever referenced in that .header file itself and
in the .cpp file it is the header file for.
Those two files only deal with that single class.
Any other part of the program that uses that class will specifically
include that same header file which either has the define there or
commented out (depending on which 'version' I want to compile).
Is what I am doing there frowned upon? Perhaps I am being dumb.
I really don't use #defines that way very much. It certainly works in
a similar case without issues in the same project.
So perhaps I am unaware of some pitfall?
Sorry if I am wasting people's time here, but I think what I am doing
is legal. It seems logical to me.
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