Re: XCode Project Organization Question
Re: XCode Project Organization Question
- Subject: Re: XCode Project Organization Question
- From: Joar Wingfors <email@hidden>
- Date: Sun, 15 Mar 2009 18:25:15 -0700
On 15 mar 2009, at 15.12, Richard L. Aurbach wrote:
[Q] Is it best to use one large project with multiple targets (one
per application) or multiple projects (each with a single target) to
manage the suite?
<snip>
In CodeWarrior, each application in the suite has a project of it
own. In addition, there is a project that consists solely of
references to these application-projects that contains a target that
builds the entire suite.
You can model your project either way. If this layout is known to your
team already, it might be easiest to just replicate it using the same
layout of projects and targets in Xcode.
In Xcode, it appears that the most obvious approach is to create a
single large project with one target for each application (and debug/
release configurations for each). Is this a good strategy? What are
the pluses and minuses? What sort of experience do others have in
this regard? And if I use a single large multi-target project, what
is the best way to automate a full-suite build?
For automation:
Create "aggregate" targets that reference all other targets that you
want to include in the build (Such aggregate targets are typically
called "All", "All, No Tests", etc.), and then build that target using
the command line utility "xcodebuild"
j o a r
_______________________________________________
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