From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-14 09:49:01
----- Original Message -----
From: "Markus Schöpflin" <markus.schoepflin_at_[hidden]>
> From: "Markus Schöpflin" <markus.schoepflin_at_[hidden]>
> It's because you don't have the MSVC toolset set up properly, and it's
> trying to guess what to do. It makes the wrong guess on your system.
> working on instructions for all the toolsets, but we don't have any for
> that one yet. There are two basic ways to set it up:
> 1. Run VCVARS32.bat yourself before building
> 2. Set MSVC_ROOT to point at your installation's VC98 directory
I did run VCVARS32 before, as stated in the documentation. There must
be something else going on.
>From a clean checkout, after invoking VCVARS32.bat, the following works:
.\bjam -sTOOLS="msvc" -sMSVC_ROOT=%MSVCDIR%
If I leave out the MSVC_ROOT variable, it fails. Is there any debug
flag I can set to help in debugging this?
No need. I understand what the problem is, though I'm not sure why it is
that way: the toolset checks for "MSVCDir" because that's what my
VCVARS32.BAT sets, but your VCVARS32.BAT is setting "MSVCDIR". I've fixed
the toolset so it looks for either one. For the next boost release we
probably ought to set up a built-in global variable called ENVIRONMENT or
something which contains the names of all environment variables as they are
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