variant properties are not transfered to sibling builds

From: Michael Stevens (Michael.Stevens_at_[hidden])
Date: 2003-06-10 09:58:25

 Dear All,

Simply a bug report with test case. Sorry no fix for this as it is a 
little to complex for my current understanding of Boost.build.v2

Bug:

See attached test case. It setup a simple heirachical build problem, 
with one exe and one library in sibling directories. At the base of the 
heirachcy the Jamfile specifies a variant. So we have the following 
structure

project-root.jam:
Jamfile:
variant debug-AA : debug : <define>AA ;
/a
Jamfile:
exe a a.cpp ../b/blib;
/b
Jamfile:
lib blib b.cpp;

Building from the root directory or from the 'a' subdirectory, specifing 
the build variant "debug-AA" exposes the problem . In both cases the the 
library will be built without the specifed <define>AA of the variant.

 --------------050809020406090005020106 Content-Type: application/x-tar;
name="sibling_variant.tar"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="sibling_variant.tar"

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