Direct Dependencies clarification
Direct Dependencies clarification
- Subject: Direct Dependencies clarification
- From: Matt Gough <email@hidden>
- Date: Tue, 22 Jul 2008 19:36:54 +0200
Our app makes use of several dylibs created by sub-projects, such as:
strings.dylib (Strings.xcodeproj Target:strings)
graphics.dylib (Graphics.xcodeproj Target:graphics)
The graphics.dylib is also dependant on strings.dylib, so the graphics
target has strings as a Direct Dependency, the app is dependent on
strings and graphics.
i.e
MyApp
/ \
/ \
graphics strings
/
/
strings
In my App's target settings, should I add both strings and graphics as
Direct Dependancies, or just graphics (since strings is 'inherited' by
the dependency on graphics)?
The problem with just adding graphics is that obviously if ever
graphics does not become dependent on strings, MyApp would not build
anymore.
So what really is the meaning of 'Direct' in this context? Is it any
target that is explicitly used by the target's binary, instead of
implicitly?
Is there any harm in having the same target appearing multiple times
in the same dependency tree?
E.g imagine an even lower level target 'maths' that MyApp, graphics
and strings all depend on. If it was a Direct Dependency in each of
those targets, it would appear 4 times in the dependency tree for MyApp.
MyApp
/ | \
/ maths \
graphics strings
/ \ |
/ \ maths
strings maths
|
maths
Should I care?
Thanks
Matt Gough
_______________________________________________
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