Re: [Boost-build] Problem with disabling warnings on gcc

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-03 07:36:14

On Wednesday 01 March 2006 23:00, Reece Dunn wrote:
> Emil Dotchevski wrote:
> >I'm building under cygwin/gcc, which works great except for a small
> > problem with warnings: I am specifying <cxxflags>-Wno-non-virtual-dtor,
> > but when launching g++ boost-build passes that flag before -Wall. So
> > basically, no warnings are disabled because -Wall re-enables them all.
>
> It would probably be best to get the command line expansions to place
> <cxxflags>, <cflags>, etc. at the end of the command line to support this
> usage and other situations where the user wants flags passed directly to
> the compiler to override those set by BBv2.
>
> >As far as I can
> >tell I do not specify <warnings>all anywhere in my jamfiles.
>
> BBv2 defaults to <warnings>all. After consideration (and the fact that CW
> generates a gazillion warnings in this case) it would be best to set the
> default to <warnings>on.

There's also gazillion warnings with msvc. We indeed should do something about 
it, but I'm not sure if making <warnings>on default, or making <warnings>all 
translate to less agreesive switches on CW and MSVC is the best solution. At 
least on gcc, all warnings from -Wall are reasonable.

- Volodya