Boost logo

Boost-Build :

From: Phillip Seaver (phil_at_[hidden])
Date: 2005-11-23 14:38:57

Vladimir Prus wrote:

>Sorry for not being very helpful with coding this, but I promise to commit the
>patch even if <pch*> features are hardcoded here ;-) I'll add new feature
>attribute if and when we'll have another case where propagation to direct
>dependents only is desired.
I've mentioned it before (and there have been past discussions about
it), but I would like to be able to add a library as a dependency to
another library without the includes and defines being propagated to
users of the other library. For example (taken from :-) )

lib a : $(ASrc) : : : <include>./include/a ;
lib b : $(BSrc) a : : : <include>./include/b ;
lib c : $(CSrc) b : : : <include>./include/c ;
exe D : $(DSrc) c ;

I would prefer that ./include/a not be added to the compile lines for c
and d. It would make the command-lines shorter and avoid incorrect
header includes. If I wanted to propagate a's requirements from b to c,
I could just use <use>:

lib b : $(BSrc) a : : : <include>./include/b <use>a ;

Phillip Seaver

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at