Re: [Boost-build] Target alternatives problem

Subject: Re: [Boost-build] Target alternatives problem
From: Alexander Sack (pisymbol_at_[hidden])
Date: 2009-01-20 09:19:25

On Mon, Jan 19, 2009 at 7:44 PM, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> AMDG
>
> Ian Emmons wrote:
>>
>> I have a pre-built library that I am trying to declare in site-config.jam,
>> but I am having problems.  The <search> feature for the library varies
>> depending on the toolset, so I am using target alternatives for the
>> declaration.  The three target alternatives are shown below.
>>
>> My jam file has a lib target with "/site-config//BerkeleyDB" in its list
>> of sources.  When I build it with the command line "bjam toolset=msvc-9.0
>> address-model=64 variant=debug", I get the following output:
>>
>>   error: No best alternative for /BerkeleyDB
>>       next alternative: required properties: <toolset>msvc-9.0
>>           not matched
>>       next alternative: required properties: <toolset>msvc-8.0
>>           not matched
>>       next alternative: required properties: <toolset>msvc-7.1
>>           not matched
>>   ...found 192 targets...
>>   ...updating 44 targets...
>>
>> Why doesn't boost.build find a match?  Is it significant that my lib
>> target specifies "/site-config//BerkeleyDB", but the error message complains
>> about just "/BerkeleyDB"?  I am using bjam 03.1.17 and the version of
>> boost.build that comes with Boost libraries 1.37.0.  My user-config.jam is
>> also shown below.  Any help you might have is greatly appreciated.
>
> Subfeatures are not currently expanded properly in target requirements.
> Try <toolset>msvc <toolset-msvc:version>9.0

Is this buried in the select-alternatives() stuff?

-aps