Boost Build and -Wall
I see that in Boost Build <warnings>on translates to -Wall. What value do I specify for <warnings> to get the compiler-default warnings level? -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
On Thu, Aug 28, 2014 at 1:50 PM, Mathias Gaunard < mathias.gaunard@ens-lyon.org> wrote:
On 28/08/2014 22:12, Emil Dotchevski wrote:
I see that in Boost Build <warnings>on translates to -Wall. What value do I specify for <warnings> to get the compiler-default warnings level?
<warnings>off ?
That would turn of all warnings, rather than use the compiler-default. -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
On 08/29/2014 12:12 AM, Emil Dotchevski wrote:
I see that in Boost Build <warnings>on translates to -Wall. What value do I specify for <warnings> to get the compiler-default warnings level?
Emil, there's no way to do it - the assumption was that you can just not specify <warnings> property for the compiler default to take effect. If parent project has explicit "<warnings>on" as requirement, a child project can cancel it using "-<warnings>on" as requirement. If there's another situation where it would not work, could you describe it? Certainly implementing what you ask for is not hard (see untested patch below), but it would be interesting to know your use case. - Volodya diff --git a/src/tools/builtin.jam b/src/tools/builtin.jam index d62680a..7f68ea8 100644 --- a/src/tools/builtin.jam +++ b/src/tools/builtin.jam @@ -166,6 +166,7 @@ feature.feature warnings : on # Enable default/"reasonable" warning level for the tool. all # Enable all possible warnings issued by the tool. off # Disable all warnings issued by the tool. + default # Just use compiler defaults : incidental propagated ; feature.feature warnings-as-errors :
On Thu, Aug 28, 2014 at 9:33 PM, Vladimir Prus
On 08/29/2014 12:12 AM, Emil Dotchevski wrote:
I see that in Boost Build <warnings>on translates to -Wall. What value do I specify for <warnings> to get the compiler-default warnings level?
there's no way to do it - the assumption was that you can just not specify <warnings> property for the compiler default to take effect.
If parent project has explicit "<warnings>on" as requirement, a child project can cancel it using "-<warnings>on" as requirement.
This is very helpful, thank you! -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
participants (3)
-
Emil Dotchevski -
Mathias Gaunard -
Vladimir Prus