Re: Projects and Targets
Re: Projects and Targets
- Subject: Re: Projects and Targets
- From: James Bucanek <email@hidden>
- Date: Thu, 9 Aug 2007 21:59:08 -0700
Simon Raisin <mailto:email@hidden> wrote (Thursday, August
9, 2007 7:50 PM -0400):
I just finished reading the "Targets" section of the Xcode User's Guide and
it appears as though I could simply create one "master" project and create
targets for each the assets that are currently contained within their own
Xcode project. It would be great if I could access all of my source code
from one location.
Q1) Is the the second option even possible?
It's more than possible, I think it's the recommended technique.
I have several projects that build multiple products. Some
produce sub-products (helper binaries, frameworks, plug-ins,
help files) that later get included in an application target.
Some produce completely independent products (i.e. a client
application and a server application) that just happen to share
common source files.
The best feature of this arrangement (in my opinion) is that all
of the targets share a single set of build settings, which makes
maintaining build settings across multiple products actually sane.
Q2) What is the recommended way of handing this type of situation?
The biggest decision is probably how to organize your source
files. For overlapping products, I usually create a "Common"
folder that contains all shared source files, then separate
subfolders for the source files unique to each target. But there
are certainly no rules, and you choose the organization that
best fits your needs.
James Bucanek
____________________________________________________________________
Author of Beginning Xcode ISBN: 047175479X
<http://www.beginningxcode.com/>
_______________________________________________
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