Re: [Boost-build] explicitly-specified values of non-free feature <threading> conflict

Subject: Re: [Boost-build] explicitly-specified values of non-free feature <threading> conflict
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-01-22 16:17:59

AMDG

On 01/22/2018 06:53 AM, Phillip Seaver via Boost-build wrote:
> On 1/17/18 12:46 PM, Steven Watanabe via Boost-build wrote:
>> <snip>
>> Proposed solution:
>> - Boost.Build should ignore non-free usage requirements
>>   and issue a warning.
> 
> Sorry to come in late to the discussion -- I fell behind on keeping up
> with this group.  I don't remember if I try to use a non-free feature in
> usage requirements, but it would be nice if you could.

  It would be nice, but it's really complicated
and I don't have a consistent model of what
ought to happen.

>Â  However, if it
> doesn't support it, I think it should be an error.
> 

  It should be, but for now I'm compromising with
a warning to avoid breaking everything.

In Christ,
Steven Watanabe