Re: Setting Project Dependencies
Re: Setting Project Dependencies
- Subject: Re: Setting Project Dependencies
- From: Chris Espinosa <email@hidden>
- Date: Sat, 16 Jul 2005 13:49:08 -0700
On Jul 16, 2005, at 12:57 PM, Michael Rice wrote:
I have a project that has a single Aggregate target. I can't figure
out how to set the dependencies among each of the various projects
that form the aggregate. For example:
* Project A has an aggregate target consisting of Project B and
Project C.
* Project B has a single static library target.
* Project C has a single app bundle target that is linked to the
library created by Project B.
If I change the source code in Project B and then build Project A, it
correctly rebuilds Project B, creating a new static library, but does
not relink Project C. What I need is to be able to specify, in Project
A, the dependency of Project C on Project B.
Is there a way to do this or am I out of luck? I'm very new to Xcode,
so I'm not sure this is the appropriate way to setup the build
environment. The reason I setup the build this way is that project
packages for Projects B and C are automatically generated by another
tool, so I can't really modify those projects inside Xcode; I would
need to redo those modifications each time the project is generated by
the tool.
In Project C,
1) Select the top-level project in the Groups & Files list
2) Choose Add to Project...
3) Select Project B, don't copy files.
4) Select the target for the app bundle in Project C and choose Get Info
5) In the General tab, find Direct Dependencies. Click the "+" button
at the bottom, and choose the static library target from Project B.
Now when you build C, it will make sure that B is built first. When
you build A, it will make sure that B is built first, which will bring
in the previous dependency.
_______________________________________________
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