split workflows in linux and windows #20
Workflow file for this run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # 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. | ||
| # See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-single-platform.yml | ||
| name: CMake on multiple platforms | ||
| on: | ||
| #push: | ||
| # branches: [ $default-branch ] | ||
| pull_request: | ||
| branches: [ "main" , "54-add-a-runtime-compilation-version-of-the-library-for-nvidia-gpus" ] | ||
| jobs: | ||
| build: | ||
| runs-on: [self-hosted, linux, x64] | ||
| strategy: | ||
| # 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. | ||
| fail-fast: false | ||
| # Set up a matrix to run the following 3 configurations: | ||
| # 1. <Windows, Release, latest MSVC compiler toolchain on the default runner image, default generator> | ||
| # 2. <Linux, Release, latest GCC compiler toolchain on the default runner image, default generator> | ||
| # 3. <Linux, Release, latest Clang compiler toolchain on the default runner image, default generator> | ||
| # | ||
| # To add more build types (Release, Debug, RelWithDebInfo, etc.) customize the build_type list. | ||
| matrix: | ||
| build_type: [Release] | ||
| cpp_compiler: [g++,clang++] | ||
| include: | ||
| - os: linux | ||
| cpp_compiler: g++ | ||
| # - os: jetsonnanoorin | ||
| # cpp_compiler: clang++ | ||
| exclude: | ||
| - os: linux | ||
| cpp_compiler: clang++ | ||
| #- os: windows-latest | ||
| # cpp_compiler: clang | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Set reusable strings (linux) | ||
| # Turn repeated input strings (such as the build output directory) into step outputs. These step outputs can be used throughout the workflow file. | ||
| id: stringslinux | ||
| run: | | ||
| echo "build-output-dir=${{github.workspace}}/build" >> "$GITHUB_OUTPUT" | ||
| - name: Configure CMake | ||
| run: | | ||
| cmake -G "Ninja" -B ${{steps.strings.outputs.build-output-dir}} | ||
| -DCMAKE_CXX_COMPILER=${{matrix.cpp_compiler}} | ||
| -DCMAKE_BUILD_TYPE=${{matrix.build_type}} | ||
| -S ${{github.workspace}}; | ||
| - name: Build | ||
| # 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). | ||
| run: > | ||
| cmake --build ${{ steps.strings.outputs.build-output-dir }} --config ${{ matrix.build_type }} | ||
| - name: Test | ||
| working-directory: ${{ steps.strings.outputs.build-output-dir }} | ||
| # 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). | ||
| # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail | ||
| run: ctest --build-config ${{ matrix.build_type }} --output-junit test_results.xml | ||
| - name: JUnit Report Action | ||
| uses: mikepenz/action-junit-report@v5 | ||
| if: success() || failure() # always run even if the previous step fails | ||
| with: | ||
| report_paths: '**/build/test_results.xml' | ||
| include_passed: true | ||
| detailed_summary: true | ||
