Re: Multi-project solution in Xcode
Re: Multi-project solution in Xcode
- Subject: Re: Multi-project solution in Xcode
- From: Uli Kusterer <email@hidden>
- Date: Mon, 9 Jul 2007 15:44:54 +0200
On 09.07.2007, at 15:27, Kevin Hoffman wrote:
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?
Just add project dependencies. It's in the Xcode docs, and I haven't
done this in ages (set it up once, then forgot how to do it again),
but I think what you essentially do is make several projects, and
then just drag the projects one project depends on into its "Groups &
Files" list, and then Xcode will build the other projects as well.
Make sure the build configurations have the same names, though, or
it'll be a little random what gets built against what.
You'll probably get better information on this topic on the Xcode
mailing list, though.
Depending on your situation, multiple targets can work just fine,
too. I use that to build variants of the same project, i.e. a full
and a Lite version. But for several projects sharing a library,
project dependencies sound like they'd make more sense.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
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