Re: [Boost-build] <build>no propagation

From: J. van der Wulp (jwulp_at_[hidden])
Date: 2006-11-24 15:48:36

Hello Vladimir,

Vladimir Prus wrote:

>> The output of a clean build of the project that is attached gives:
> 
> Thanks. I have reproduced the problem and hopefully fix it tomorrow.

That would be great; you have all done an amazing job so far with Boost 
Build v2.

> But, just to clarify -- is it fine for your that if <build>no is propagated, then 
> nothing at all will be built? Including any install targets you might have -- 
> nothing.

Yes, I think it is the most intuitive. That is, if executable A cannot 
be build due to propagation of <build>no and executable B can be build, 
then it would be nice if executable B is installed. For example:

exe A : A.cpp some-library-with-build-no ;
exe B : B.cpp ;

stage install
       : A
         B
       : <location>/something/bin
       ;

For our application I do not care about any library that A depends on 
cannot be build and/or installed. Our toolset currently only builds and 
installs those libraries that are actually needed by the tools thanks to 
Boost Build (which is a great feature I think).

Thanks a lot,

Jeroen