Re: variant properties not propogated to siblings

From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-07-14 16:59:13

Michael Stevens <Michael.Stevens_at_[hidden]> writes:

> Hi All,
>
> I've been tracking a bug in BBv2 for a while. It problably beyond my 
> current understanding of the related code releate to property 
> propogation so I will describe the problem here.
>
> The bug appears in all versions from M3-M5 and the current CVS head. It 
> is problably easies described by a minmal build hierachy that exposes 
> the problem
>
> Jamfile
> build-project a ;
> variant debug-AA : debug : <define>AA ;
>
> a/Jamfile
> project
> : requirements <include>"../../include"
> : default-build debug
> ;
> exe a : a.cpp ../b//blib ;
>
> a.cpp
> #ifndef AA
> #error Requires AA
> #endif
> int main () {}
>
> b/Jamfile
> lib blib : b.cpp ;
>
> b/b.cpp
> #ifndef AA
> #error Requires AA
> #endif
>
>
> Building with "bjam -d2 debug-AA" in the project root show the problem. 
> The variant property <define>AA is not propogated to the "b" project.
> Interestingly if the same command is executed with the current directory 
> set to "b" then it does get the property!

What happens when you swap the order of the two lines in the root
Jamfile?

I am guessing this is a result of being insufficiently lazy when
reading Jamfiles.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com