waf checking - fail on warnings?

[Matthew Selsky]

On Mon, Aug 26, 2019 at 10:51:58PM -0700, Hal Murray via devel wrote:
> > A relatively quick search suggests mandatory=True as an argument.
> 
> That makes waf fail if the code chunk doesn't work.

You want "mandatory=False" since this is a probe, not a requirement.

And you want to pass "-Werror" (I'm not certain how off the top of my head) to the compiler so that warnings are fatal. waf sees the compiler exit zero with or without warnings, so they look the same.

> I'm trying to make the code chunk not-work if it gets a warning, but then let 
> waf put a comment in config.h to indicate that a feature test didn't work 
> rather than put a #define to indicate that it did work.



Thanks,
-Matt