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 17:03:21 +0700
Since header files get copied verbatim into any file that includes
them (and then preprocessed, of course), my first thought is that
you're including this header from two different source files and
that's causing unexpected behavior. Furthermore, it's possible that
one source file defines _FOO_ and the other does not which could
lead to the data offset issues you mentioned, especially if what you
are conditionally defining is part of a struct or class definition.
Hi Steve,
It's actually outside the class definition at the top of the file.
And it's the one and only instance of that header file in the whole
project.
But yes, it is referenced in more than one place.
However to my mind it would be constantly re-defined by that, at worst.
I have tried it both inside and outside the main #ifndef for that .h
file.
It's also a very specific define: #define _USE_BAD_VBO_METHOD
Not something I am likely to be using elsewhere, and I have done a
search for that just in case.
Does that shed any more light on it? Am I doing something stupid?
Cheers,
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