|
|
Boost Testing : |
From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2006-11-13 04:16:02
Rene Rivera writes:
> Aleksey Gurtovoy wrote:
> > Rene Rivera writes:
> >> AlisdairM wrote:
> >>> There are suddenly a lot of unexpected passes for VC6.5, and looking at
> >>> the output it seems that vcvars from Visual Studio 2003 is being used
> >>> to set the paths.
> >> Weird.
> >
> > FWIW, we build bjam with Visual Studio 2003 (on every cycle), which
> > involves running the corresponding "vcvars32.bat" from the same
> > "regression.py" session that then proceeds with the regression tests
> > themselves. Could this be the culprit?
>
> Yes it could. 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?
> >> Could someone who has 6.5 test if this is a problem in general?
> >> "bjam --v2 --show-configuration" output would be of particular
> >> interest.
> >
> >>From which directory?
>
> Any, but to prevent things from trying to build it's best to do it from
> the root/tools/build/v2 directory.
Okay, here's what we get:
notice: <toolset>msvc-6.5
notice: <toolset>msvc-7.0
notice: <toolset>msvc-7.1
notice: <toolset>borland-5.6.4
notice: <toolset>borland-5.8.1
notice: <toolset>borland-5.8.2
notice: <toolset>cw-8.3
error: no Jamfile in current directory found, and no target references specified.
-- Aleksey Gurtovoy MetaCommunications Engineering