[Boost-build] Why specify a compiler executable when using <setup>?

Subject: [Boost-build] Why specify a compiler executable when using <setup>?
From: Andreas Huber (ahd6974-spamboostorgtrap_at_[hidden])
Date: 2009-12-08 06:09:32

With the following user-config.jam ...

using msvc : 9.0~stlport5.2 : "C:/Program Files/Microsoft Visual Studio 
9.0/VC/bin/cl.exe" :
<compileflags>-D_CRT_SECURE_NO_WARNINGS
<setup>"%BUILDROOTPATH%Msvc90StlPort.bat" ;

... the following command line works as expected:

bjam -a -d2

(everything is rebuilt by calling "%BUILDROOTPATH%Msvc90StlPort.bat" before 
each cl command).

However, if I use the following user-config.jam ...

using msvc : 9.0~stlport5.2 :  :
<compileflags>-D_CRT_SECURE_NO_WARNINGS
<setup>"%BUILDROOTPATH%Msvc90StlPort.bat" ;

with the same command line I get a ton of errors saying that cl is not 
recognized, which isn't surprising as the log no longer shows calls to 
"%BUILDROOTPATH%Msvc90StlPort.bat".

I'm wondering why I have to specify a compiler executable? My understanding 
of <setup> is that it should set *everything* (including PATH) so that all 
tools can be found, no?

Thanks,

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