conflicting preprocessor definition found in two precompiled headers, target uses wrong one
conflicting preprocessor definition found in two precompiled headers, target uses wrong one
- Subject: conflicting preprocessor definition found in two precompiled headers, target uses wrong one
- From: Stuart Smith <email@hidden>
- Date: Wed, 16 May 2007 13:26:27 -0700
- Thread-topic: conflicting preprocessor definition found in two precompiled headers, target uses wrong one
I have a target TA which has its "Prefix Header" ( GCC_PREFIX_HEADER]) set
to
A.pch++
which includes the definition
#define XXX 0
other targets in the same project use A.pch++, some use B.pch++.
B.pch++ has this line:
#define XXX 1.
When I build target TA, I find that XXX evaluates to the wrong value, 1.
When I right-click on XXX in a source file and choose "Jump to Definition",
a popup appears which gives me too choices:
#define XXX (A.pch++)
#define XXX (B.pch++)
How can this happen? I though a target can only include one precompiled
header. How can I find out what is reading B.pch++?
(Xcode 2.4.1, IDE 762.0, Core 762.0, ToolSupport 764.0, Mac OS X 10.4.9
8P2137.)
thanks, Stuart
_______________________________________________
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