Opened 10 years ago
#6883 new Bugs
build.bat not using the 32-bit Visual Studio 2010 installation path
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | To Be Determined | Component: | Building Boost |
| Version: | Boost 1.49.0 | Severity: | Problem |
| Keywords: | build.bat VC10 | Cc: |
Description
See also #6846 (bootstrap)
I had the same problems there but didn't want to overtake ownership on that trac issue.
With Visual Studio 2010, in a Visual Studio Command Prompt, bootstrap will fail. It cannot find any of the headers. I am looking at the build.bat and I think it's latching on to %ProgramFiles% to set the paths. Like this:
if EXIST "%ProgramFiles%\Microsoft Visual Studio 10.0\VC\VCVARSALL.BAT" (
set "BOOST_JAM_TOOLSET=vc10" set "BOOST_JAM_TOOLSET_ROOT=%ProgramFiles%\Microsoft Visual Studio 10.0\VC\"
I used the recommended installation path for my edition and it put vcvarsall.bat in: C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC
Unfortunately %ProgramFiles% comes up with the 64-bit path "C:\Program Files" -- note the omission of "(x86)" in there. So dead right there.
I should note I can work fine if I call vcvarsall.bat manually before running bootstrap.
I don't have a firm recommendation here one what to do. Perhaps you can probe the registry for installation keys for Visual Studio, and from there derive the path. If you don't have an installation handy on which to experiment I can submit myself to some probes.
