On Aug 9, 2005, at 4:31 PM, Timothy J. Wood wrote: Another option is project references in Xcode. One issue with this is that building the a target via its 'normal' project uses the settings in that project file, but building it via the referencing project uses the settings from the referencing project. This is either a feature or bug depending on your state of mind -- either way, it is worth noting :) (of course, I haven't yet tried this in 2.1, since we typically use the script I mention above).
This behavior has in fact changed in Xcode 2.1. Instead of passing the settings from the referencing project down to the referenced project, the referenced project is built using the configuration that matches the name of the active configuration in the referencing project.
Whew. That's a lot of "referenced" and "referencing" for one sentence. Let me try that again, with a more concrete example...
Let's assume you have an Application project, and one or more Framework projects that it references (and depends on), and you build the Application using a particular configuration, say the "Release" configuration. If the Framework project(s) need to be rebuilt, Xcode will build each of those projects using the settings in their project files corresponding to the "Release" configuration. This should be the same as opening each of the referenced projects individually, setting the configuration to "release", and building them.
-Mark
|