From: Ali Azarbayejani (ali_at_[hidden])
Date: 2003-05-08 09:14:28
Vladimir Prus wrote:
> I've a question for msvc users. Now, V2 works ok if you specify
> using msvc : 6.5 ;
> in user-config.jam. But if you write
> using msvc ;
> then it will works only if vcvasrs32.bat was called previously. Two people
> already stumbled on it, and I think something should be done. The options are
> 1. Document the the second case ("using msvc ; ") works only if vcvars32.bat
> were called.
> 2. If vcvars32.bat is in path, use that to find the path to compiler. 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.
> 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).
> Can anybody comment on those variants or offer more alternatives?
I would prefer not having to depend on vcvars32.bat at all. Also, I
don't want my build to produce side effects. How about
(1) check default installation locations; if so, use those
(2) check if tools (cl, link) are in PATH; if so, use those
(3) NEVER invoke vcvars32.bat if it's going to make a permanent change
to my Environment; at least I need the option to be able to invoke a
completely non-intrusive build with no side effects.
(4) Documenting and warning about vcvars32.bat are fine and good, and if
a user wants to invoke it manually, it should make (2) work, but don't
do it for me automatically unless it can be done in a way that doesn't
produce side effects.
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