vc-7_1 and intel-win32 still broken for ST builds?

From: Andreas Huber (ahd6974-spamgroupstrap_at_[hidden])
Date: 2004-11-24 18:49:32

Hi there

It seems that the vc-7_1 and the intel-win32 toolsets still do the wrong 
thing for targets with a <threading>single requirement.

My (stripped-down) Jamfile looks as follows (see the PingPongSingle 
target):

subproject libs/fsm/example ;

rule fsm-st-example-build (
target-name : directory : sources + : additional-options * )
{
exe $(target-name)
: $(directory)/$(sources).cpp
: <threading>single
$(additional-options)
;

return <exe>$(target-name) ;
}

stage run
: [ fsm-st-example-build PingPongSingle : PingPong : PingPong ]
: common-variant-tag
<target>stage
<target>all
;

The issued compiler command looks as follows:

[snip]
CALL "C:\Program Files\Microsoft Visual Studio .NET 
2003\VC7\bin\VCVARS32.BAT" >nul
"C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin\cl" 
/Zm800 -nologo /EHsc -c /Z7 /Od /Ob0 /EHsc /GR /MDd /Op /Zc:forScope 
/Zc:wchar_t -I"..\..\..\bin\boost\libs\fsm\example" -I"D:\Andreas\My 
Documents\fsm\boost_1_32_0" -Fo"..\..\..\bin\boost\libs\fsm\example\PingPongSingle.exe\vc-7_1\debug\threading-multi\PingPong.obj" 
-Tp"D:\Andreas\My 
Documents\fsm\boost_1_32_0\libs\fsm\example\PingPong/PingPong.cpp"
[snip]

As a workaround, is there any way to stop bjam from issuing /MDd?

Thanks & Regards,

-- 
Andreas Huber
When replying by private email, please remove the words spam and trap 
from the address shown in the header.