Hi, just tested this on develop... Am Dienstag, 21. März 2017, 19:44:25 CET schrieb Olaf van der Spek via Boost:
'"C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/vcvarsall.bat"' is not recognized as an internal or extern al command, operable program or batch file.
The compiler autodetection from a plain cmd shell is broken. That is line 715 of msvc.jam, current local shell_ret = [ SHELL "$(cl_path) 14.10 -PathToCompiler" ] ; Manually calling the helper script "cl_path.cmd" results in: cl_path.cmd 14.10 -PathToCompiler Join-Path : Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NULL ist. ... Full output attached, unfortunately in a German shell. git bisect on this command gives: 00c23580afdd519fa716ee32d6dba500e6b1e991 is the first bad commit which is commit 00c23580afdd519fa716ee32d6dba500e6b1e991 Author: Arkadiy Shapkin <arkady.shapkin@gmail.com> Date: Sun Mar 19 00:59:40 2017 +0800 Check Visual Studio 2017+ version in script * Fixed `build.bat` stack overflow on some machines by splitting up to several files * CSharp script simplified and now will check VC++ toolset version or https://github.com/boostorg/build/commit/ 00c23580afdd519fa716ee32d6dba500e6b1e991 This seems to have gone terribly wrong. The old script before this commits faithfully outputs the correct compiler from a plain windows command shell. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany