Re: [boost] [release] 1.64.0 please test master snapshot..

On 17 March 2017 at 02:08, Tom Kent via Boost wrote:

On Thu, Mar 16, 2017 at 9:36 AM, Mateusz Loskot via Boost < boost@lists.boost.org> wrote:

...

On 16 March 2017 at 13:09, Rene Rivera via Boost wrote:

...

After help from various sources to get the VS2017 building working the latest master snapshot should at least try and build with VS2017. Assuming nothing horrible shows up today we will release the first beta tonight. Hence, please smoke test the latest master snapshot found at:

https://dl.bintray.com/boostorg/master/

Thanks for the snapshot.

I did quick building subset of libraries using VS2017, with ZLIB_SOURCE and BZIP2_SOURCE defined. The build was successful. I did not run any tests though. Brief configuration log copied below.

Kudos to Tom Kent for recent patches towards VS2017 support.

Minor issue: - I run build inside "x64 Native Tools Command Prompt for VS 2017" - That is, using native 64-bit CL.EXE and targetting 64-bit platform. - In config.log, I see b2_msvc_14.10.25017_vcvarsx86_amd64_.cmd - In processes, I see b2 runs CL.EXE 32-bit cross-compiuler targetting 64-bit Would it be possible to run CL.exe 64-bit binary? Given I'm in the VS2017 command prompt configured with native 64-bit toolset...

I think this comes from build/src/tools/msvc.jam:1055. I'm not sure what to do about it though. I guess we need to look at the env variables: PROCESSOR_ARCHITECTURE, Platform, and PreferredToolArchitecture.

PreferredToolArchitecture as the hint would also be consistent with MSBuild. I've tried to force b2 to use 64-bit binary of cl.exe. I added this to project-config.jam using msvc : 14.10 : "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Tools\\MSVC\\14.10.25017\\bin\\HostX64\\x64\\cl.exe" ; But then, it looks like failing to recognise the toolset: b2 toolset=msvc-14.10 F:/boost/tools/build/src/tools\msvc.jam:1103: in configure-really *** argument error * rule generate-setup-cmd ( version : command : parent : options * : cpu : global-setup ? : default-global-setup-options : default-setup ) * called with: ( 14.10.25017 14.10.25017 : C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64 : C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX64 : <command>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX86\x86\cl.exe <command>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe : i386 : : x86 : vcvars32.bat ) * extra argument 14.10.25017 F:/boost/tools/build/src/tools\msvc.jam:811:see definition of rule 'generate-setup-cmd' being called F:/boost/tools/build/src/tools\msvc.jam:201: in configure F:/boost/tools/build/src/tools\msvc.jam:153: in msvc.init F:/boost/tools/build/src/build\toolset.jam:43: in toolset.using F:/boost/tools/build/src/build\project.jam:1052: in using project-config.jam:6: in modules.load F:/boost/tools/build/src\build-system.jam:249: in load-config F:/boost/tools/build/src\build-system.jam:412: in load-configuration-files F:/boost/tools/build/src\build-system.jam:524: in load F:\boost\tools\build\src/kernel\modules.jam:295: in import F:\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build F:\boost\boost-build.jam:17: in module scope F:\boost> Best regards, -- Mateusz Loskot, http://mateusz.loskot.net