Re: [Boost-build] trouble with test-suite

Subject: Re: [Boost-build] trouble with test-suite
From: Jonathan Brannan (kickace_at_[hidden])
Date: 2009-07-24 15:35:06

It seems to be caused by having the alias the same name as the file I pass
to compile-fail.  Either renaming the alias or giving compile a target with
diffrent name seems to work correctly.

On Fri, Jul 24, 2009 at 3:24 PM, Jonathan Brannan <kickace_at_[hidden]> wrote:

> Well, I wanted 2 things to be run as one command on the cmd line (one
> compile and one compile-fail).
>
> On Fri, Jul 24, 2009 at 1:38 PM, Steven Watanabe <watanabesj_at_[hidden]>wrote:
>
>> AMDG
>>
>> Jonathan Brannan wrote:
>>
>>> I have a simple Jamfile with just this:
>>> import testing ;
>>>
>>> test-suite Simple_String_Compile_Fail_ut :
>>>  [ testing.compile-fail Simple_String_Compile_Fail_ut.cpp /boost//headers
>>> ]
>>>  ;
>>>
>>> and a blank Jamroot
>>>
>>> When I run Simple_String_Compile_Fail_ut
>>> I get :
>>> error: No best alternative for ./Simple_String_Compile_Fail_ut
>>>    next alternative: required properties: (empty)
>>>        matched
>>>    next alternative: required properties: (empty)
>>>        matched
>>>
>>> I've looked at the Jamfiles in boost that use this and it seems to
>>> work with the same syntax.  Is there some magic in my Jamroot I need?
>>>
>>>
>>
>> Best to leave out test-suite entirely.
>>
>> testing.compile-fail Simple_String_Compile_Fail_ut.cpp /boost//headers ;
>>
>> In Christ,
>> Steven Watanabe
>>
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>>
>
>