On Tue, Feb 26, 2019 at 7:13 AM Mateusz Loskot via Boost-Testing <boost-testing@lists.boost.org> wrote:

On Tue, 26 Feb 2019 at 14:02, Tom Kent via Boost-Testing
<boost-testing@lists.boost.org> wrote:
> I was hoping to start running regression tests for the upcoming Visual Studio 2019 (toolset 14.2) and got stumped by an issue.
> I've set a user-config.jam:
> using msvc : 14.2 ;

Is this toolset even supported?

As I explained in https://lists.boost.org/Archives/boost/2019/02/245143.php,
I had to 'fake' it as 14.1 in project-config.jam:

using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual
Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe"

I was able to get the regression tests to run using this workaround in user-config.jam.

Here's what the config_info is:

https://www.boost.org/development/tests/develop/developer/output/teeks99-test02-boost-bin-v2-libs-config-test-config_info-test-msvc-14-1-debug-address-model-64-link-static-runtime-link-static.html

I'm disappointed that we can't have general support for future versions of msvc. We don't seem to have this problem with pre-release versions of GCC/Clang.

https://www.boost.org/development/tests/develop/developer/output/teeks99-02-dc9-2a-Docker-64on64-boost-bin-v2-libs-config-test-config_info-test-clang-linux-9~c++2a-debug-visibility-hidden.html

Tom