From d021eae1cf9806282745935391a5ca282f4b5999 Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Wed, 15 Dec 2021 20:10:48 +0300 Subject: support VS 2022 --- .github/workflows/boost_toolsets.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to '.github/workflows/boost_toolsets.yml') diff --git a/.github/workflows/boost_toolsets.yml b/.github/workflows/boost_toolsets.yml index ba027c6..d7c6fc4 100644 --- a/.github/workflows/boost_toolsets.yml +++ b/.github/workflows/boost_toolsets.yml @@ -15,10 +15,11 @@ jobs: boost-version: [1.58.0, 1.65.0, 1.72.0] toolset: [auto, clang, clang-cl, gcc, mingw, msvc] cygwin: [0, 1] - os: [ubuntu-latest, windows-2016, windows-2019] + os: [ubuntu-latest, windows-2016, windows-2019, windows-2022] include: # Prettier run names. + - {os: windows-2022, name: Windows 2022} - {os: windows-2019, name: Windows 2019} - {os: windows-2016, name: Windows 2016} - {os: ubuntu-latest, name: Ubuntu} @@ -42,6 +43,10 @@ jobs: # This was fixed for 1.61 in this commit: # https://github.com/boostorg/test/commit/c94ef6982e2ebe77f9376579547c228f0d62e45f. # On Linux/Cygwin, everything should be fine though. + - toolset: clang + boost-version: 1.58.0 + os: windows-2022 + libraries: filesystem program_options regex system - toolset: clang boost-version: 1.58.0 os: windows-2019 @@ -58,7 +63,8 @@ jobs: # Cygwin: no MSVC/clang-cl. - {cygwin: 1, toolset: msvc} - {cygwin: 1, toolset: clang-cl} - # Cygwin is the same on Windows Server 2016 & 2019. + # Cygwin is the same on different Windows versions. + - {os: windows-2019, cygwin: 1} - {os: windows-2016, cygwin: 1} # clang-cl is only supported by Boost.Build since 1.69 (see the # boost_clang_windows.yml workflow). -- cgit v1.2.3