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

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. I did a quick check running all five command windows on two VMs, one running a 64-bit win2012R2 and one running a 32-bit win7. On 64-bit windows install C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2017\Visual Studio Tools Developer Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat" Sets: PROCESSOR_ARCHITECTURE=AMD64 x64 Native Tools Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars64.bat" Sets: Platform=x64 PROCESSOR_ARCHITECTURE=AMD64 x64_x86 Cross Tools Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsamd64_x86.bat" Sets: Platform=x86 PreferredToolArchitecture=x64 PROCESSOR_ARCHITECTURE=AMD64 x86 Native Tools Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars32.bat" Sets: Platform=x86 PROCESSOR_ARCHITECTURE=AMD64 x86_x64 Cross Tools Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsx86_amd64.bat" Sets: Platform=x64 PROCESSOR_ARCHITECTURE=AMD64 On Windows 7 - 32 Bit Install C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2017\Visual Studio Tools Developer Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat" Sets: PROCESSOR_ARCHITECTURE=x86 x64 Native Tools Command Prompt for VS 2017 (cl.exe doesn't run!) Runs: %comspec% /k "C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat" Sets: Platform=x64 PROCESSOR_ARCHITECTURE=x86 x64_x86 Cross Tools Command Prompt for VS 2017 (cl.exe doesn't run!) Runs: %comspec% /k "C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsamd64_x86.bat" Sets: Platform=x86 PreferredToolArchitecture=x64 PROCESSOR_ARCHITECTURE=x86 x86 Native Tools Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars32.bat" Sets: Platform=x86 PROCESSOR_ARCHITECTURE=x86 x86_x64 Cross Tools Command Prompt for VS 2017 Runs: %comspec% /k "C:\Program Files\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsx86_amd64.bat" Sets: Platform=x64 PROCESSOR_ARCHITECTURE=x86 The full output of the DOS "set" command for each shell is in this gist: https://gist.github.com/teeks99/627dce6f298ba02592643f03fe36a68b Tom