From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-28 07:24:13
On Tuesday 28 February 2006 14:42, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> > On Saturday 18 February 2006 17:27, David Abrahams wrote:
> >> > Running "bjam" with --debug-building showed me that the <warnings>off
> >> > was just not propagated to the boost_python targets, and the reason
> >> > was the the "warnings" feature was no marked as propagated. Fixed in
> >> > CVS now, let me know if this fixes to problems for you.
> >> I'm afraid not.
> >> bjam --v2 warnings=off msvc-8.0
> >> in libs/iterator/test still shows warnings.
> > Hmm, when I run:
> > bjam --v2 warnings=off -n msvc | grep "W4"
> > there, I see nothing. And nothing with "W3", either. Without
> > "warnings=off", all command lines include "W4".
> OK, then "no warnings" is clearly not the default for msvc-8.0
> The toolset should be explicitly passing /W0 when warnings=off.
Well, it passes /W0. I think the only way to fix this up is to know which file
you see warnings on, and the exact command line for that file, and what
command line does not causes the warning.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk