Re: [jamboost] Stupid msvc toolset?

From: John Maddock (john_at_[hidden])
Date: 2005-11-12 12:03:43

> Sorry in advance if my questions are going to upset you even more...

:-)

>> Why oh why does the msvc toolset inject the compilers own include
>> paths into the command line?
>
> It does? AFAICT it just runs vcvars32 before the compile and never
> inserts any compiler specific includes. Is there some specific
> instance that I can see what you are talking about?

Yep, try:

cd libs/tr1/test
$ bjam -d2 run_random
...found 656 targets...
...updating 10 targets...
vc-C++ 
..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1\debug\threading-m
ulti\run_random.obj

"cl" /Zm800 -nologo /EHsc -c /Z7 /Od /Ob0 /EHsc /GR /MDd /Op /wd4675 
/Zc
:forScope /Zc:wchar_t -I"..\..\..\bin\boost\libs\tr1\test" -I"C:\Program 
Files
\Microsoft Visual Studio .NET 
003\VC7\include" -I"c:\data\boost\develop\boost"
-Fo"..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1\debug\threading-m
ulti\run_random.obj" -Tp"c:\data\boost\develop\boost\libs\tr1\test\run_random.c
pp"

run_random.cpp
command-file-dump 
..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1\debug\
threading-multi\run_random.CMD

IF EXIST 
"..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1\debug\thre
ading-multi\run_random.CMD" DEL 
"..\..\..\bin\boost\libs\tr1\test\run_random.tes
t\vc-7_1\debug\threading-multi\run_random.CMD"
echo 
"..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1\debug\threadin
g-multi\run_random.obj">>..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1
\debug\threading-multi\run_random.CMD

vc-Link 
..\..\..\bin\boost\libs\tr1\test\run_random.test\vc-7_1\debug\threading-
multi\run_random.exe

"link" /nologo /DEBUG /subsystem:console 
/out:"..\..\..\bin\boost\libs\t
r1\test\run_random.test\vc-7_1\debug\threading-multi\run_random.exe" 
/LIBPATH
:"C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\lib" 
@"..\..\..\bin\b
oost\libs\tr1\test\run_random.test\vc-7_1\debug\threading-multi\run_random.CMD"

Note that both the compile and link commands have had VC++ directories 
explicitly added to them.

BTW, the shell I use has had vcvars32.bat already run (in case that makes 
any difference).

Thanks!

John.