build-test

Dual-compiler testing validates CMake builds across gcc and clang by automating sequential build and test workflows in separate directories. This approach detects cross-compiler regressions and verifies portability before merging changes.

Dual-compiler testing detects regressions by building and running checks for CMake targets with both gcc and clang. It sequentially validates compiled executables to ensure compatibility and catch issues introduced by code changes.

Yes, you need separate build directories, specifically build_ci and build_ci_clang, to test CMake targets with gcc and clang. This separation prevents conflicts and allows accurate dual-compiler validation.

No, you cannot run concurrent builds when validating changes across multiple compilers. Safety rules are implemented to prevent concurrent builds, requiring a sequential workflow for per-target builds and tests.

You should use dual-compiler builds for your CMake project when changing CMake targets and needing to ensure all compiled executables pass basic checks on both gcc and clang. It is applicable to CI workflows and local development.