Eric_Johnson writes:
Thus, all of "c"'s operations have to be complete before "a" can begin.
What "Depends a : c" guarantees is that "a" is not considered built
until "c" is built. It doesn't stop jam from building "a" first.
The order in which build steps are executed depends on the order
in which actions are invoked, all other dependencies being equal.
I've never seen a case where the order in which the "Depends" occurs
actually affects the order in which targets are built. However,
when rules are nested, and actions are implicit, it's sometimes
tricky to see from the jamfiles exactly what the order of action
invocations actually is.
To satisfy your requirement, you could try:
Depends a : b.c ;
Depends b.c : c ;
By making "b.c" depend on "c", you force all actions that take "b.c"
as input to be deferred until "c" is completely built.
---Laura
-------------------------------------------------------------------------
Laura Wingerd lau...@perforce.com Voice: 1-510-864-7400
Perforce Software, Inc. www.perforce.com Fax: 1-510-864-5340
-------------------------------------------------------------------------
2 messages in com.perforce.jammingDepends with two NOTFILE targets
