Re: How to ensure that nested project targets get built ?
Re: How to ensure that nested project targets get built ?
- Subject: Re: How to ensure that nested project targets get built ?
- From: Paul Russell <email@hidden>
- Date: Fri, 2 Oct 2009 18:03:37 +0100
Thanks - that was *exactly* what I was looking for. And it's also
there in Xcode 3.2 of course.
Paul
On 2 Oct 2009, at 15:49, Martin Redington wrote:
You're missing something obvious (or at least it's obvious in Xcode
3.1 and earlier).
In your parent project, Get Info on your target, and in the General
tab (assuming 3.2 still has one), under direct dependencies, click the
add button.
All the other targets from the parent, and any as yet unadded targets
from sub-projects should be listed.
Add the target that build libfoo.a, and you should be (almost) all
set. You will probably want to add a copy files phase to the parent
target that copies the libfoo.a into an appropriate place in the main
target project.
On Fri, Oct 2, 2009 at 3:39 PM, Paul Russell <email@hidden>
wrote:
Suppose I have a project, test_foo.xcodeproj, and a nested project,
foo.xcodeproj, which builds a library libfoo.a, and libfoo.a is
linked to
the executable test_foo built in test_foo.xcodeproj. How do I make
sure that
when I build and run test_foo, that libfoo.a gets rebuilt
automatically if
needed ? There doesn't seem to be any way to introduce a dependency
from a
nested project to its parent project, as you would if everything
were in a
single project ? Or am I missing somtehing obvious ?
Paul
P.S. This is Xcode 3.2.
_______________________________________________
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