| Hello,
We're working on a multi-platform game engine with several libraries and applications. Until now, we've used one project per library, with only one target inside each project (and several build configurations). Dependencies are setup between projects. I've read the trade-offs of having one vs. several projects in the Xcode Workspace Guide, and I'm wondering if we should go the one project way. Basically I'd like to have the same behavior we have with VS on Windows: one big solution file, containing all .vcproj, with indexing working across all of them, and dependencies set up nicely. But maybe trying to get closer to VS is not the spirit :) I'm a bit confused with how things are supposed to work in Xcode. I'm not sure whether one Xcode project with multiple targets achieves my goal? Can targets include only a subset of the source files included in a project? Are targets meant to build different products? Or just different versions of the same product? Overall there are more than 3K source files. Is this ok for a Xcode project, working with 2.66 Core 2 Duo iMacs with 2Gb RAM? Is it possible to keep separate projects and to create one that includes them? It's handy sometimes to be able to open just a subset of the whole project.
Thanks. |