Complex XCode projects

[icklefrelp]

I currently have my code set up to build as multiple projects for example:-

<RTRacing>
--<RTCore>
----RTCore.xcodeproj (common dynamic library in C++)
--<CoreTest>
----CoreTest.xcodeproj (simple Cocoa app in Obj-C++ which links with RTCore.dylib)
--<...> (other related projects)

What I'm wanting to do is to have one project file at the RTRacing level with which encompasses the other projects.

I tried importing the sub projects into my root level project but it doesn't seem to behave the way I want it to (The way Visual Studio's Solutions can contain multiple projects).

Reading the XCode Documentation, it suggest I can have a project set up, which builds multiple targets, so I have been persuing this approach. I setup an empty project in XCode, and created two targets RTCore and CoreTest. RTCore builds fine, but when building CoreTest I'm getting thousands of what look like Objective-C errors precompiling AppKit.h e.g.

error: expected unqualified-id before '@' token
error: expected constructor, destructor, or type conversion before '*' token
error: 'NSString' was not declared in this scope

The Target looks to be setup as it is in the stand alone project, and all source files are exactly the same as the stand alone version (.cpp & .mm), but I must have missed something. Can anybody help?

Many Thanks

Claire

[OneSadCookie]

This might be relevant: http://tips.onesadcookie.net/tips/published/Writing+Precompiled+Headers+for+Xcode

[icklefrelp]

It certainly did end up being relevent. I'm not actually using the .pch files (they are essentially empty) but it seems that GCC_PREFIX_HEADER is getting set to $(SYSTEM_LIBRARY_DIR)/Frameworks/AppKit.framework/Headers/AppKit.h when I add new Cocoa Application Targets to my project. I'm not really sure why this is happening or if this is correct behaviour.

Regardless I changed the prefix header to point to CoreTest/CoreTest_Prefix.pch
and it builds fine.

Thanks for the tip :)