Opened 6 years ago

Last modified 6 years ago

#12862 new Bugs

build boost with Visual Studio 2017 RC without sdk 10

Reported by: zoruamonster@… Owned by:
Milestone: To Be Determined Component: Building Boost
Version: Boost 1.63.0 Severity: Problem
Keywords: cl Cc:

Description

I have installed Visual Studio 2017 with 7.1SDK

After run b2 i got error "cl" not found. Many times! If i run b2 with Visual Studio CMD i got error:

**********************************************************************
** Visual Studio 2017 RC Developer Command Prompt v15.0.26206.0
** Copyright (c) 2016 Microsoft Corporation
**********************************************************************

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community>cd c:\boost

c:\BOOST>b2
C:/BOOST/tools/build/src/tools\msvc.jam:834: in generate-setup-cmd
*** argument error
* rule maybe-rewrite-setup ( toolset : setup-script : setup-options : version :
rewrite-setup ? )
* called with: ( msvc :  :  : default :  )
* missing argument setup-script
C:/BOOST/tools/build/src/tools\msvc.jam:746:see definition of rule 'maybe-rewrit
e-setup' being called
C:/BOOST/tools/build/src/tools\msvc.jam:1076: in configure-really
C:/BOOST/tools/build/src/tools\msvc.jam:201: in configure
C:/BOOST/tools/build/src/tools\msvc.jam:153: in msvc.init
C:/BOOST/tools/build/src/build\toolset.jam:43: in toolset.using
C:/BOOST/tools/build/src/build\project.jam:1052: in using
project-config.jam:3: in modules.load
C:/BOOST/tools/build/src\build-system.jam:249: in load-config
C:/BOOST/tools/build/src\build-system.jam:412: in load-configuration-files
C:/BOOST/tools/build/src\build-system.jam:524: in load
C:\BOOST\tools\build\src/kernel\modules.jam:295: in import
C:\BOOST\tools\build\src/kernel/bootstrap.jam:139: in boost-build
C:\BOOST\boost-build.jam:17: in module scope

c:\BOOST>

Change History (7)

comment:1 by anonymous, 6 years ago

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

comment:2 by anonymous, 6 years ago

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"

comment:3 by cingelmarekmt@…, 6 years ago

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).

comment:4 by Torsten@…, 6 years ago

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.

comment:5 by cingelmarekmt@…, 6 years ago

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

comment:6 by anonymous, 6 years ago

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

comment:7 by anonymous, 6 years ago

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.

Note: See TracTickets for help on using tickets.