You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 19, 2026. It is now read-only.
We need to rework the ninja script compiler naming scheme. We need to create scripts for 4 compilers:
MSVC
gcc
clang-cl (Windows)
clang (Posix)
Because we now have platform-specific versions of .srcfiles, we don't actually need multiple flags. The normal CFlags options will be for the default compiler for the specific platform, and the CLANG flags will be for any additional flags when running either clang-cl.exe (using .srcfiles.win.yaml) or clang.exe (using .srcfiles.max.yaml or .srcfiles.unix.yaml).
What we DO need are compiler-specific .ninja scripts, and that means one for clang-cl.exe and another one for clang.exe.
Description:
We need to rework the ninja script compiler naming scheme. We need to create scripts for 4 compilers:
Because we now have platform-specific versions of .srcfiles, we don't actually need multiple flags. The normal CFlags options will be for the default compiler for the specific platform, and the CLANG flags will be for any additional flags when running either clang-cl.exe (using
.srcfiles.win.yaml) or clang.exe (using.srcfiles.max.yamlor.srcfiles.unix.yaml).What we DO need are compiler-specific .ninja scripts, and that means one for clang-cl.exe and another one for clang.exe.