aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/.github
diff options
context:
space:
mode:
authorEgor Tensin <Egor.Tensin@gmail.com>2022-01-07 01:21:34 +0300
committerEgor Tensin <Egor.Tensin@gmail.com>2022-01-07 01:22:44 +0300
commit5715229463b1e6e0bf1fd25b0521436ffe0bded4 (patch)
tree4555856dcbbcd6a7e664c7a6ff61b6b30927ada7 /.github
parentworkflows: remove remnants of Cygwin jobs (diff)
downloadcmake-common-5715229463b1e6e0bf1fd25b0521436ffe0bded4.tar.gz
cmake-common-5715229463b1e6e0bf1fd25b0521436ffe0bded4.zip
workflows: reduce number of jobs further
Diffstat (limited to '')
-rw-r--r--.github/workflows/boost_toolsets.yml8
-rw-r--r--.github/workflows/example_toolsets.yml8
2 files changed, 16 insertions, 0 deletions
diff --git a/.github/workflows/boost_toolsets.yml b/.github/workflows/boost_toolsets.yml
index 3259284..2a5dbf9 100644
--- a/.github/workflows/boost_toolsets.yml
+++ b/.github/workflows/boost_toolsets.yml
@@ -47,6 +47,14 @@ jobs:
# Ubuntu: no MSVC/clang-cl.
- {os: ubuntu-latest, toolset: msvc}
- {os: ubuntu-latest, toolset: clang-cl}
+ # Optimization: MinGW-w64 should be the same on different Windows
+ # versions. Clang on the other hand relies on the Microsoft linker
+ # (at least it did at some point), so it makes sense to test it
+ # against different Visual Studio versions.
+ - {os: windows-2016, toolset: gcc}
+ - {os: windows-2019, toolset: gcc}
+ - {os: windows-2016, toolset: mingw}
+ - {os: windows-2019, toolset: mingw}
# clang-cl is only supported by Boost.Build since 1.69 (see the
# boost_clang_windows.yml workflow).
- {toolset: clang-cl, boost-version: 1.58.0}
diff --git a/.github/workflows/example_toolsets.yml b/.github/workflows/example_toolsets.yml
index b4f5fc7..dd6096f 100644
--- a/.github/workflows/example_toolsets.yml
+++ b/.github/workflows/example_toolsets.yml
@@ -53,6 +53,14 @@ jobs:
# Ubuntu: no MSVC/clang-cl.
- {os: ubuntu-latest, toolset: msvc}
- {os: ubuntu-latest, toolset: clang-cl}
+ # Optimization: MinGW-w64 should be the same on different Windows
+ # versions. Clang on the other hand relies on the Microsoft linker
+ # (at least it did at some point), so it makes sense to test it
+ # against different Visual Studio versions.
+ - {os: windows-2016, toolset: gcc}
+ - {os: windows-2019, toolset: gcc}
+ - {os: windows-2016, toolset: mingw}
+ - {os: windows-2019, toolset: mingw}
runs-on: '${{ matrix.os }}'