Re: conflicting preprocessor definition found in two precompiled headers, target uses wrong one
Re: conflicting preprocessor definition found in two precompiled headers, target uses wrong one
- Subject: Re: conflicting preprocessor definition found in two precompiled headers, target uses wrong one
- From: Andrew Pontious <email@hidden>
- Date: Tue, 22 May 2007 17:43:58 -0700
On May 16, 2007, at 7:27 PM, Stuart Smith wrote:
[snip]
I can make either target A or target B the active target. They use
A.pch++
and B.pch++, respectively. Regardless of which target is active, if I
right-click YYY, I'll see the "#define YYY 1" line highlighted. This
would
appear to be a bug, because for target B, XXX is 1 and thus YYY is 0.
Also, the Code Sense contextual menu seems to be unaware of targets,
so it
offers both definitions as choices, because the *Project* index
knows about
both.
Is there some way I can find *for a specific target* what value a
preprocessor constant has and how it arrived at that value?
Alternatively,
can I limit Code Sense results to one target?
Unfortunately, no. The Code Sense index is not currently smart enough
to distinguish between targets. It will respect the information in
your current configuration, however.
-- Andrew
_______________________________________________
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