Re: [Boost-build] toolset dependent test-suite behavior

Subject: Re: [Boost-build] toolset dependent test-suite behavior
From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2013-06-19 10:58:08

On Wed, Jun 19, 2013 at 11:56 AM, Steven Watanabe <watanabesj_at_[hidden]>wrote:

> AMDG
>
> On 06/10/2013 07:54 AM, Jan Boehme wrote:
> > I want to do something like this:
> >
> > test-suite cxx11_varadic : [ compile-fail varadic.cpp ] : <toolset>mscv ;
> >
> > test-suite cxx11_varadic : [ compile varadic.cpp ] : <toolset>gcc ;
> >
> > Means it's intended the rule called cxx11_varadic doesn't compile using
> > the msvc toolset but compiles fine if toolset gcc is used.
> >
> > Unfortunately I get "No best alternative" errors calling the rule:
> >
> > error: No best alternative for utils/system/tests/c++11/cond_test
> > next alternative: required properties: <threading>multi
> > matched
> > next alternative: required properties: <threading>multi
> > matched
> > ...found 1 target...
> >
>
> This error doesn't seed to correspond to your code.
>

Doesn't compile and compile-fail rules create a target with the same name
(based on the source file's name)?

Shouldn't this work?

test-suite cxx11_varadic : [ compile-fail varadic.cpp : :
variadic_test_fail1 ] : <toolset>mscv ;
test-suite cxx11_varadic : [ compile varadic.cpp : : variadic_test1 ] :
<toolset>gcc ;

> Is there / what would be a proper way to declare something like this?
> >
>
> In Christ,
> Steven Watanabe
>

Regards,
-- 
Felipe Magno de Almeida