Boost C++ Libraries: Ticket #12862: build boost with Visual Studio 2017 RC without sdk 10

anonymous — Thu, 23 Feb 2017 04:45:25 GMT

Need very fast help please !! sorry bad english)))

anonymous — Fri, 24 Feb 2017 22:20:45 GMT

b2 doesn't seem to be able to find cl.exe for 2017 on its own. You can provide the path by updating the project-config.jam to include:

using msvc : : <path to x86 or x64 cl.exe>

This should be something like "c:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.24911\bin\HostX64\x64\cl.exe"

cingelmarekmt@… — Wed, 29 Mar 2017 17:45:50 GMT

Hello, my problem :(

Run in Developer command prompt VS 2017

b2 -a -q -d1 -j8 address-model=64 toolset=msvc-14.1 --build-type=complete

project-config.jam ... import option ; using msvc : 14.1 : C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe; option.set keep-going : false; ...

Log: c:\sdk\boost_1_63_0>b2 -a -q -d1 -j8 address-model=64 toolset=msvc-14.1 C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe --build-type=complete notice: could not find main target C:\Program notice: assuming it is a name of file to create. notice: could not find main target Files notice: assuming it is a name of file to create. notice: could not find main target (x86)\Microsoft notice: assuming it is a name of file to create. notice: could not find main target Visual notice: assuming it is a name of file to create. notice: could not find main target Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe notice: assuming it is a name of file to create. Performing configuration checks

32-bit : yes (cached)
arm : no (cached)
mips1 : no (cached)
power : no (cached)
sparc : no (cached)
x86 : yes (cached)

Still not work, please give me a hint (- 64-bit not in a log).

Torsten@… — Thu, 30 Mar 2017 18:16:24 GMT

I have the very same problem here. I can run cl (or cl.exe) from the Developer Command Prompt for VS 2017. Using the suggested workaround and adding the full path (in quotes) to cl.exe (using "where cl.exe") in the project-config.jam, seems to fix the problem.

cingelmarekmt@… — Sun, 02 Apr 2017 10:24:18 GMT

I must open in "x64 Native Tools Command Prompt for VS 2017", now working OK.

anonymous — Wed, 12 Apr 2017 22:02:10 GMT

Some problem here, even with the "x64 Native Tools Command Prompt for VS 2017" command prompt.

anonymous — Thu, 13 Apr 2017 03:37:27 GMT

I had the same problem. I added the line

using msvc : 14.1 : "E:\Program Files (x86)\Visual Studio 2017\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe" ;

to my project-config.jam and ran

./b2 -j8 address-model=64 toolset=msvc-14.1

from the x64 Native Tools Command Prompt and I'm compiling away.