Re: [Boost-build] From where do compiler options come ?

Subject: Re: [Boost-build] From where do compiler options come ?
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2015-09-29 03:05:28

On 29-Sep-15 9:57 AM, Vladimir Prus wrote:
> On 28-Sep-15 11:25 PM, Vladimir Prus wrote:
>> The priority order is roughly this:
>> - default values, here  warnings=on
>> - properties on the command line, none in your case
>> - requirements on projects and metatargets
>>
>> I am surprised you still get -Wall, I'll take look tomorrow.
>
> Edward,
>
> with the patch below, when I run "b2 --debug-building", I see that
> <warnigns>off is in build properties. With msvc, I also see /W0, which
> is the expected warning option. Could you try exactly same patch and see
> whether -Wall is still there?
>
> --- test/Jamfile
> +++ test/Jamfile
> @@ -15,7 +15,7 @@ project
>     ;
>
>   test-suite lambda
> -  : [ run algorithm_test.cpp ]
> +  : [ run algorithm_test.cpp : : : <warnings>off ]
>       [ run bind_tests_simple.cpp ]
>       [ run bind_tests_advanced.cpp ]
>       [ run bind_tests_simple_f_refs.cpp ]

The same patch also eliminates -Wall on Ubuntu with gcc.

- Volodya