Boost Users :

I adjusted the auto_link.hpp and project-config.jam files to use vc141 and 14.1 instead of vc150 and 15.0. I had to also change visual.hpp as this was already headed down the “15.0” route. Now I have binaries built with and named after the 141 toolset. Thanks.

Chris.

The toolset of VS15 is not v150 but v141. This is because current plans are to keep binary compatibility with v14x toolsets. STL and CRT headers might change, the compiler will gain new C++ features, but everything built with v14x can be linked together like a happy family.

I built both x86 and x64 flavours of Boost 1.62 with Visual Studio 2017 RC using this approach:

1.       Boostrap from a shell configured using the x86 vcvars or x64 vcvars.

2.       Update the project-config.jam to include:
using msvc : 15.0 : <path to x86 or x64 cl.exe>

I had to make a small change to the auto_link.hpp:

# elif defined (BOOST_MSVC) && (BOOST_MSVC < 1910)

                // vc14:

#  define BOOST_LIB_TOOLSET “vc140”

# elif defined (BOOST_MSVC)

                // vc15:

#  define BOOST_LIB_TOOLSET “vc150”

Issues for me:

·         I failed to update the MSVC toolset detection in tools/build/src/tools/msvc.jam (hence fixing the version in project-config.jam)

·         For the x64 build, passing address-model=64 on the b2 command line didn’t work so I had to delete bin.v2 and stage folders between the x86 and x64 builds.

Chris.

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify the sender immediately and then destroy it.