From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-05-12 23:00:26
David Abrahams wrote:
> > Invoke vcvars32.bat before all tool invocations. If vcvars32.bat is
> > not in path, look though default install location for versions 7.1,
> > 7.0 and 6. If compiler is found in any of locations, it will be
> > used.
> it was supposed to work that way in the first place. If it didn't, it
> was just a bug.
OK. Just to confirm: I think the problem with current code is that when no
version is given, it does not look at any default locations. The right
approach would be to search though 7.1, 7.0 and 6.0 paths.
Also, do we need to invoke compiler/linker with the full path? vcvars32.bat
changes PATH, I believe, but there may be another "cl" in PATH...., so full
path is needed. Am I missing something?
And final question: if compiler is in the path, what should be do? Use that
one? Or ignore PATH? Should be use compiler in path even if
using msvc : 6 ;
was used? I tend to ignore PATH at all.
> Note also the issue with the handling of optional
Could you explain what's that issue is about. I do not understand what's
wrong, if anything.
> But anyway, my overall vote on this option is:
OK. That's probably next thing I'll do on V2.
> > 3. Try to sense if vcvars32.bat was already called. If so, use
> > variables it sets to find the path to compiler. If vcvars32.bat is
> > not already called, use logic from (2).
> If it was already called, the compiler is in the path.
But we don't make any use of PATH settings when configuring msvc.... so I
don't get your argument.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk