ansaurus

Question

Error building pch file with CPP definitions

Answer 1

+1 A:

Bit of a stab in the dark here - are you generating a precompiled header file? Have you rebuilt the precompiled header file since you changed the preprocessor symbol? You may be seeing a difference in the symbol as built into the precompiled header, and the symbol as seen in the other compilation units.

1800 INFORMATION 2009-06-06 10:41:46

Upvote because it's a good suggestion but I am cleaning the build and removing the pre-compiled headers.

Roger Nolan 2009-06-06 21:46:57

Answer 2

+1 A:

Please post the invocation line of the compiler, not just the error; it tells us infinitely more. The error you cited is typical when an upstream error confuses the compiler when it's #importing downstream header files; it obviously doesn't mean there are errors in CFBag.h et al.

My suspicion is that when you created a different target, you got a different Prefix Header File for that target, and it's not set up correctly; compare the Prefix Header File build settings for the old and new targets, and compare the files themselves.

One common error is to include Objective-C header files from a C++ project. That doesn't work; you need to turn your .cpp files into .mm files if you want to intermix Objective-C and C++. But C++ should be able to #include CoreFoundation header files.

cdespinosa 2009-06-06 22:41:00

Thanks. I've tried making the new varient by copying the existing build target and setting up a new one from scratch. I've also added the build directive to my original build and I still get the errors.

Roger Nolan 2009-06-07 10:17:29

Answer 3

+2 A:

    -D<Multiple -Dvalues> 
<command-line>: error: macro names must be identifiers
<command-line>: error: ISO C99 requires whitespace after the macro name

It looks like at some point you edited All Configurations of the Preprocessor Macros build setting of your project or target. Different configurations had different values. Rather than pressing Cancel or replacing them uniformly, you somehow confirmed the placeholder text .

Xcode is dutifully passing "<Multiple" and "Values>" as preprocessor definitions, instead of the preprocessor definitions you want.

Go to the target inspector Build tab, find Preprocessor Macros, delete its current value, and replace it with the value you really want.

cdespinosa 2009-06-07 17:33:03

Doh, I completely didn't regiter that :-( Thanks very much. I have no idea how I did that but investigating quickly today, I did notice that when I was trying to delete my COREDATA macro Xcode wasn't overwriting the settings correctly.

Roger Nolan 2009-06-07 21:22:35

Thanks this is the problem. The root cause seems to be adding a compiler flag to Xcode for all configurations when you have different values for other configurations. For example, I define DEBUG for only my debug builds. When I then add COREDATA for all configurations, Xcode converts its <multiple Values> display string into a real value used in the compiler invocation and generates the defect you pointed out.

Roger Nolan 2009-06-08 06:53:59

ansaurus

tags:

views:

answers:

Error building pch file with CPP definitions

related questions