Re: msvc toolset config deduction broken.

From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-07-17 19:01:46

"klapshin" <klapshin_at_[hidden]> writes:

> --- In jamboost_at_[hidden], David Abrahams <gclbb-jamboost_at_m...>
> wrote:
>
>> I have no environment variables set to point to any msvc
>> installations. My msvc installations are all in the default places.
>
> Not even VS71COMNTOOLS? This one should be there, because in 7.1
> vcvars32.bat will not work without this variable.

OK, I have that one.

>> When I got done with the msvc toolset, this worked automatically. Now
>> building the hello, world example in examples-v2 fails to call the
>> compiler setup vcvars32.bat or use any explicit paths, so of course
>> compilation fails.
>
> When did it start happening? About a month ago I submitted patch which
> was supposed to improve automatic compiler discovery. It was rather
> innocent change -- use %ProgramFiles% if available (otherwise fallback
> to c:\Program Files), use VS71COMNTOOLS for 7.1 if possible.
>
> Does it fail for all 3 versions of msvc? What are the values of
> %ProgramFiles% and %VS71COMNTOOLS% on your system (if present).
>
> Does "fails to call vcvars.32" means it does not even try to call?

Yep. But now I'm not so sure it ever worked. It works when I do 

bjam msvc-6.5

I guess the real question is, given that I have msvc-6.5 msvc-7 and
msvc-7.1 registered, why does it try to use the 'msvc' toolset when I
just do

bjam

??

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com