From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-17 03:28:39
On Thursday 16 December 2004 19:38, Toon Knapen wrote:
> A public header file of library B that includes a header file of library
> A induces a header- (or propagating) dependency from library B to A.
> Because all code that includes this header file of library B will need
> to be able to find the specified header files of A too.
> If only source files of library B include headersof library A, the
> dependency is non-propagating.
> The latter kind of dependency will result in soth like
> lib libB : b.cpp : <include>path_to_A ;
> Users of 'libB' will 'inherit' the requirement to include 'path_to_A'.
Seems to me that explicitly specifying include paths like this is contrary to
the idea of usage requirements. We should have <use>A and get <include>
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