Re: Copying an Xcode project
Re: Copying an Xcode project
- Subject: Re: Copying an Xcode project
- From: Steve Baxter <email@hidden>
- Date: Wed, 25 Jan 2006 17:04:47 +0000
We use xcconfig files to manage settings across all the projects - it
works perfectly! Some projects have some different paths (for third
party code), but mostly the only custom setting is the product name.
Having multiple projects also means that we can work better as a team
- if everyone was modifying the core "project" it would be a
nightmare. This way, everyone works on their own modules.
As always, YMMV, but multiple projects works well for us!
CHEERS,
STEVE.
On 25 Jan 2006, at 13:28, j o a r wrote:
On 25 jan 2006, at 14.10, Steve Baxter wrote:
The modules stand alone - it would be very confusing to have every
source file for every module all in one enormous project with 70
targets!
Think that's a lot of targets? You should have seen our project
before I changed it... :-)
How would it be more confusing? Xcode allows you to group and
filter the files you work with.
The day you need to change something in all those projects - as a
completely unbelievably hypothetical example, let's say that Xcode
2.3 requires you to upgrade all project files - you're going to
regret not using targets.
The new xcconfig files have made target management soo much easier!
I basically needn't maintain any per-target settings, it's all done
via macro expansion in the per-target xcconfig files.
Anyway, that's my €0.02 worth.
j o a r
Stephen Baxter
Software Development Manager
Improvision
email@hidden
+44-2476-692229
_______________________________________________
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