| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The job set CC/CXX env alongside the authoritative -D CMAKE_C_COMPILER / -D CMAKE_CXX_COMPILER configure flags, which already select the compiler; the env block was redundant. No behavior change (verified on the parallel UrlLib cleanup: both the gcc and clang Linux jobs stay green with the env removed). The Run Tests step's env (TSAN_OPTIONS / JSC_useConcurrentGC) is unaffected. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
This PR simplifies the reusable Linux build workflow by removing a redundant job-level CC/CXX environment override, relying solely on the existing CMake -D CMAKE_C_COMPILER / -D CMAKE_CXX_COMPILER configuration inputs to select the toolchain.
Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Context
build-linux.yml set job-level CC/CXX env alongside the -D CMAKE_C_COMPILER / -D CMAKE_CXX_COMPILER configure flags. The -D flags already select the compiler for both the gcc and clang matrix legs, so the env block was redundant.
No behavior change: on the parallel UrlLib CI cleanup both the gcc and clang Linux jobs stayed green with the env removed. The Run Tests step's env (TSAN_OPTIONS / JSC_useConcurrentGC) is untouched.
Part of a small cross-repo consistency pass — UrlLib landed the same cleanup. BabylonNative was checked and intentionally left alone: its build-linux.yml env is load-bearing there (its configure passes no -D compiler flags).
[Created by Copilot on behalf of @bghgary]