Re: [Boost-build] [v2] warnings=off is not working

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-13 10:59:05

On Friday 10 February 2006 21:26, David Abrahams wrote:

> >> Dave, do you have a minimal example reproducing the problem?
> >
> > I'm afraid not.  I was building the Boost.Python tests, though, so it
> > should be easy enough to reproduce.
>
> Maybe this gives you a clue.  Notice that the first TU is /W0 and the
> second one is /W4:

>       call "C:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32.BAT"
>  >nul cl /Zm800 -nologo -TP  /Z7 /Od /Ob0 /W0 /GR /MDd /GB /EHs 
> @"..\..\..\bin.v2\libs\python\test\select_from_python_test.test\msvc-6.0\de
>bug\type_id.obj.rsp" -c
> -Fo"..\..\..\bin.v2\libs\python\test\select_from_python_test.test\msvc-6.0\
>debug\type_id.obj"
.......
>       call "C:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32.BAT"
>  >nul cl /Zm800 -nologo -TP  /Z7 /Od /Ob0 /W4 /GR /MDd /GB /EHs 
> @"..\..\..\bin.v2\libs\python\build\msvc-6.0\debug\slice.obj.rsp" -c
> -Fo"..\..\..\bin.v2\libs\python\build\msvc-6.0\debug\slice.obj"
>
>   slice.cpp

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.

- Volodya