Bjam broken on windows with VS2017?
My lappie has vs2017 installed, latest (15.4) version, from some days ago. I did the following: 1. Put a clean copy of the boost 1.65.1 source in c: root. 2. issue 'bootstrap.bat' in c:\boost_1_65_1\ (ordinary prompt, no vs thingy). This creates a project-config.jam msvc file. 3. Copied (overwrote project-config.jam) the below contents as project-config.jam to c:\boost_1_65_1\ =======start======= import option ; using clang : 6.0 : "C:\\Program Files\\LLVM\\bin\\clang++.exe" : <compileflags>-fmsc-version=1911 <compileflags>-DBOOST_USE_WINAPI_VERSION=0x1000 <compileflags>-DBOOST_USE_WINDOWS_H=1 <compileflags>-D_WIN32_WINNT=0x1000 <compileflags>-DNOMINMAX <ranlib>"C:\\Program Files\\LLVM\\bin\\llvm-ranlib.exe" <archiver>"C:\\Program Files\\LLVM\\bin\\llvm-ar.exe" <linkflags>-fuse-ld=lld <linkflags>-flto=thin ; option.set keep-going : false ; =======end======== 4. issue 'bjam -d0 --clean' The script of that, and the result is below: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Users\User>cd \ C:\>cd boost_1_65_1 C:\boost_1_65_1>bootstrap.bat Building Boost.Build engine Bootstrapping is done. To build, run: .\b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/build/doc/html/index.html C:\boost_1_65_1>bjam -d0 --clean 'C:/Program' is not recognized as an internal or external command, operable program or batch file. etc.. etc... the rest is history? Any ideas? degski
On 15 October 2017 at 16:56, degski
Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved.
What's weird is that the latest version is actually 10.0.16299.0 (as per my install of VS2017), although I would think that doesn't matter. degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798
On 2017-10-15 16:13, degski via Boost wrote:
On 15 October 2017 at 16:56, degski
wrote: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved.
What's weird is that the latest version is actually 10.0.16299.0 (as per my install of VS2017), although I would think that doesn't matter.
It's not all that weird. Rumor has it that the next Windows 10 release - Fall Creators Update - could be due next week. Can we expect that to be version 10.0.16299.0? Bo Persson
On 15 October 2017 at 17:55, Bo Persson via Boost
It's not all that weird. Rumor has it that the next Windows 10 release - Fall Creators Update - could be due next week.
Can we expect that to be version 10.0.16299.0?
The IDE defaults to 10.0.16299.0 on the creation of a new project... The console defaulting to 10.0.15063 looks like a bug to me (I'll send a bug-rep). Ah, that Fall Creators Update. Looking forward to more useless gems like Paint3D (good old Paint, though, *is* usefull), that then also become the default for a number of file-types. degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798
participants (2)
-
Bo Persson
-
degski