Re: [jamboost] variant properties are not transfered to sibling builds

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-06-18 07:45:16

Michael Stevens wrote:
> 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 ;

> 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.

Hi Michael,
sorry for the late response.

The only way to achieve the effect you want in current system is via kluge:

rule handle-debug-AA ( property : properties * )
{
return <define>AA ;
}

feature.action <variant>debug-AA : handle-debug-AA ;

However, I think it's really a bug in the current system. It will be fixed in 
Milestone 5.

Thanks,
Volodya