Re: [Q] Dependencies in Xcode
Re: [Q] Dependencies in Xcode
- Subject: Re: [Q] Dependencies in Xcode
- From: Eric Gorr <email@hidden>
- Date: Tue, 14 Oct 2008 18:35:54 -0400
On Oct 14, 2008, at 6:15 PM, Jean-Daniel Dupas wrote:
Le 15 oct. 08 à 00:04, Eric Gorr a écrit :
I am reading through the Xcode Build System Guide (9/9/2008). On
page 26, there is a multiple target example.
In this example, there is the juicer_aggregate target which
contains three dependencies -juicer_app, blender_app &
mixer_framework.
My question is, is it possible to tell the juicer_aggregate target
that the mixer_framework _must_ be built before the juicer_app &
blender_app targets are built?
The way this works currently is that the juicer_app & blender_app
targets have a dependency on the mixer_framework.
In the case I am dealing with, it would be very useful to not have
to setup the dependency in the juicer_app & blender_app targets,
but to be able to setup an aggregate target which says that the
mixer_framework must be built before the juicer_app & blender_app
targets.
As near as I can determine, what I want to do is not possible. One
simply must setup the dependency in both the juicer_app &
blender_app targets if one wants to make sure that the
mixer_framework is already built when building the juicer_aggregate
target.
If this is confirmed, I plan to submit a feature request.
AFAK, in aggregate targets, subtargets are build in the order they
appears (from top to bottom). Just set mixer_framework as the first
target in your aggregate target (but doing this may failed if you
enabled parallel targets building)
Wanting to enable parallel targets building is the reason - it does
fail and I want it to work. It would reduce my build time by around
50% or more.
The only way it could work is if there was a way to tell the
juicer_aggregate target that the mixer_framework _must_ be built
before juicer_app & blender_app.
Of course, I believe I understand the reason why it doesn't work...if
one tried to build the juicer_app target and the mixer_framework had
been updated, the build of juicer_app would not see the changes to the
mixer_framework and this could lead to all kinds of problems.
However, in my specific case, this isn't a scenario I need to worry
about, but it is likely a scenario that is so rare as to never be
considered important enough to fix.
_______________________________________________
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