Re: Build errors
Re: Build errors
- Subject: Re: Build errors
- From: Greg Guerin <email@hidden>
- Date: Mon, 11 Sep 2006 13:42:52 -0700
Clarence Badger wrote:
>I guess I didn't stress enough that the code hadn't been changed.
Maybe something else within the project changed. As I recall, Xcode 2.0
projects undergo a conversion when upgraded.
The project-file itself refers to frameworks and settings that affect the
compiler (e.g. location of includes, predefined symbols, etc.), so it's
conceivable that some of this metadata changed, even though none of your
source files changed. Treat the project-file itself as source.
In a simpler time, I would have suggested that you preserve the
preprocessor's output to examine them manually and see if all the defines
are occurring as expected. Correlating the failing line-numbers to the
pre-processed output may show something useful that can lead you to the
ultimate cause. One thing that can cause parse errors is faulty macro
expansion, or no expansion at all, caused by incorrect include-file
locations.
Unfortunately, I don't know exactly how to preserve the preprocessor's
output with Xcode or gcc.
-- GG
_______________________________________________
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