|
|
Boost Testing : |
From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2006-11-13 23:09:31
Rene Rivera writes:
> Aleksey Gurtovoy wrote:
> > Rene Rivera writes:
> >> I'm not sure what the effect, or non-effect, of running multiple
> >> vcvars scripts in the same env are.
> >
> > Doesn't Boost.Build itself have to run the corresponding 'vcvars'
> > before invoking the compiler?
>
> It does... But since env variables are inherited it may be that the
> 6.5 vcvars script is not dealing with another set of vars being set.
Looking closer at 'regression.py', I misspoke: 'vcvars32.bat' call in
question does not affect the script's own environment and thus is
highly unlikely to have anything to do with the issue.
The results of this one, however...
> I mean run "bjam --v2 --debug-configuration".
>
> It will show things like:
>
> msvc: condition: '<toolset>msvc-7.1/<architecture>/<address-model>',
> msvc: condition: '<toolset>msvc-7.1/<architecture>/<address-model>32',
> msvc: condition: '<toolset>msvc-7.1/<architecture>x86/<address-model>',
> msvc: condition:
> '<toolset>msvc-7.1/<architecture>x86/<address-model>32', command: 'call
> "C:\Program Files\Microsoft Visual Studio .NET
> 2003\Vc7\bin\vcvars32.bat" >nul
> '
... are interesting:
notice: found boost-build.jam at D:\Users\lesha\trunk.scripts_boost_regression\boost\tools\build\v2\boost-build.jam
notice: loading Boost.Build from D:\Users\lesha\trunk.scripts_boost_regression\boost\tools\build\v2\kernel
notice: loading site-config.jam from D:\Users\lesha\trunk.scripts_boost_regression\boost\tools\build\v2\.\site-config.jam
notice: loading user-config.jam from D:\Users\lesha\trunk.scripts_boost_regression\user-config.jam
notice: msvc-7.1 detected, command: 'C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe'
notice: msvc-7.0 detected, command: 'c:\Program Files\Microsoft Visual Studio .NET\Vc7\bin\cl.exe'
notice: msvc-6.0 detected, command: 'C:\Program Files\Microsoft Visual Studio\VC98\Bin\CL.EXE'
msvc: condition: '<toolset>msvc-6.5/<architecture>/<address-model>',
msvc: condition: '<toolset>msvc-6.5/<architecture>/<address-model>32',
msvc: condition: '<toolset>msvc-6.5/<architecture>x86/<address-model>',
msvc: condition: '<toolset>msvc-6.5/<architecture>x86/<address-model>32',
command: 'call "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat" >nul
' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
msvc: condition: '<toolset>msvc-7.0/<architecture>/<address-model>',
msvc: condition: '<toolset>msvc-7.0/<architecture>/<address-model>32',
msvc: condition: '<toolset>msvc-7.0/<architecture>x86/<address-model>',
msvc: condition: '<toolset>msvc-7.0/<architecture>x86/<address-model>32',
command: 'call "c:\Program Files\Microsoft Visual Studio .NET\Vc7\bin\vcvars32.bat" >nul
'
msvc: condition: '<toolset>msvc-7.1/<architecture>/<address-model>',
msvc: condition: '<toolset>msvc-7.1/<architecture>/<address-model>32',
msvc: condition: '<toolset>msvc-7.1/<architecture>x86/<address-model>',
msvc: condition: '<toolset>msvc-7.1/<architecture>x86/<address-model>32',
command: 'call "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat" >nul
> The point is to check that it's matching the correct vcvars to each
> vc version.
Seems like for some reason it doesn't.
-- Aleksey Gurtovoy MetaCommunications Engineering