Re: Using projects & targets efficiently
Re: Using projects & targets efficiently
- Subject: Re: Using projects & targets efficiently
- From: Chris Espinosa <email@hidden>
- Date: Wed, 4 Nov 2009 08:32:56 -0800
On Nov 4, 2009, at 12:58 AM, Guillaume Billard wrote: 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?
Yes, that's specifically what targets are for. Are targets meant to build different products?
Yes -- for example, your project can have three application targets, or a target for an app, another for a framework, and three more for plug-ins. Or just different versions of the same product?
If you want different versions of the same product, often Build Configurations are a better way to do that, if the difference is only in build settings and conditional compilation, not the set of source files used to create the 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?
That shouldn't be a problem. 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.
Chris |
_______________________________________________
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