Multi-project solution in Xcode
Multi-project solution in Xcode
- Subject: Multi-project solution in Xcode
- From: "Kevin Hoffman" <email@hidden>
- Date: Mon, 9 Jul 2007 09:27:00 -0400
- Thread-topic: Multi-project solution in Xcode
Greetings,
I'm basically looking for a best practice in terms of dealing with
multiple related projects within Xcode. For some background, if I was
building a suite of applications in Visual Studio 2005 that might
interact with a common database, might share a library, or be otherwise
related in design - I would create a solution and then have all the
projects be contained within that solution. When I build, all the
executables/libraries are built, etc. What I'm looking for is the
best-practice equivalent of this in Xcode. If it doesn't make sense to
do multiple output targets within Xcode, then what's the alternative?
I've played around with this a little bit by creating multiple targets,
but I find it very difficult keeping track of which files belong to
which output target - is there a good way of managing this, or am I just
doing it incorrectly?
Thanks for any tips,
Kevin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden