|
| 1 | +# This starter workflow is for a CMake project running on multiple platforms. There is a different starter workflow if you just want a single platform. |
| 2 | +# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-single-platform.yml |
| 3 | +name: CMake on Windows |
| 4 | + |
| 5 | +on: |
| 6 | + push: |
| 7 | + branches: [ "master" ] |
| 8 | + pull_request: |
| 9 | + branches: [ "master" ] |
| 10 | + |
| 11 | +jobs: |
| 12 | + build: |
| 13 | + runs-on: ${{ matrix.os }} |
| 14 | + |
| 15 | + strategy: |
| 16 | + # Set fail-fast to false to ensure that feedback is delivered for all matrix combinations. Consider changing this to true when your workflow is stable. |
| 17 | + fail-fast: false |
| 18 | + |
| 19 | + # Set up a matrix to run the following 3 configurations: |
| 20 | + # 1. <Windows, Release, latest MSVC compiler toolchain on the default runner image, default generator> |
| 21 | + # 3. <Linux, Release, latest Clang compiler toolchain on the default runner image, default generator> |
| 22 | + # |
| 23 | + # To add more build types (Release, Debug, RelWithDebInfo, etc.) customize the build_type list. |
| 24 | + matrix: |
| 25 | + os: [windows-latest] |
| 26 | + build_type: [Release] |
| 27 | + c_compiler: [cl] |
| 28 | + include: |
| 29 | + - os: windows-latest |
| 30 | + c_compiler: cl |
| 31 | + cpp_compiler: cl |
| 32 | + exclude: |
| 33 | + - os: windows-latest |
| 34 | + c_compiler: gcc |
| 35 | + - os: windows-latest |
| 36 | + c_compiler: clang |
| 37 | + - os: ubuntu-latest |
| 38 | + c_compiler: cl |
| 39 | + |
| 40 | + steps: |
| 41 | + - uses: actions/checkout@v4 |
| 42 | + |
| 43 | + - name: Set reusable strings |
| 44 | + # Turn repeated input strings (such as the build output directory) into step outputs. These step outputs can be used throughout the workflow file. |
| 45 | + id: strings |
| 46 | + shell: bash |
| 47 | + run: | |
| 48 | + echo "build-output-dir=${{ github.workspace }}/build" >> "$GITHUB_OUTPUT" |
| 49 | +
|
| 50 | + - name: Configure CMake |
| 51 | + # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make. |
| 52 | + # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type |
| 53 | + run: > |
| 54 | + cmake -B ${{ steps.strings.outputs.build-output-dir }} |
| 55 | + -DCMAKE_CXX_COMPILER=${{ matrix.cpp_compiler }} |
| 56 | + -DCMAKE_C_COMPILER=${{ matrix.c_compiler }} |
| 57 | + -DCMAKE_BUILD_TYPE=${{ matrix.build_type }} |
| 58 | + -S ${{ github.workspace }} |
| 59 | +
|
| 60 | + - name: Build |
| 61 | + # Build your program with the given configuration. Note that --config is needed because the default Windows generator is a multi-config generator (Visual Studio generator). |
| 62 | + run: cmake --build ${{ steps.strings.outputs.build-output-dir }} --config ${{ matrix.build_type }} |
| 63 | + |
| 64 | + - name: Test |
| 65 | + working-directory: ${{ steps.strings.outputs.build-output-dir }} |
| 66 | + # Execute tests defined by the CMake configuration. Note that --build-config is needed because the default Windows generator is a multi-config generator (Visual Studio generator). |
| 67 | + # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail |
| 68 | + run: ctest --build-config ${{ matrix.build_type }} |
0 commit comments