From: Ali Azarbayejani (ali_at_[hidden])
Date: 2003-03-26 12:39:34
David Abrahams wrote:
> Ali Azarbayejani <ali_at_[hidden]> writes:
> > David Abrahams wrote:
> >> Ali Azarbayejani <ali_at_[hidden]> writes:
> >> > Doesn't <library> (or <link-to>) in Usage Requirements *already*
> >> > propagate (while <include> or <define> do not? or do they?) ?
> >> I have no clue. The definition of <library> is:
> >> feature library : : free dependency ;
> >> so it is not "propagated", but on the other hand "propagated" also
> >> denotes travel in the other direction: from dependents to
> >> dependencies.
> > Property <library> in Usage Requirements is continuously propagated
> > upward (I don't know by what mechanism, but I know it is, because it
> > ends up in the link line).
> Which direction is "up" (towards dependents or dependencies)?
Towards dependents. I.e. if exe a depends on lib b and lib b depends
on lib c, then <library> in c's usage requirements will cause c to get
linked into a.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk