variant properties not propogated to siblings

From: Michael Stevens (Michael.Stevens_at_[hidden])
Date: 2003-07-14 15:04:47

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!

Attached is a simple archive of the same files.

All the best, 
Michael

 --------------080008000007060207000508 Content-Type: application/zip;
name="variant_siblings.zip"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="variant_siblings.zip"

[Attachment content not displayed.] --------------080008000007060207000508--