LibretroAdmin b3db825a74 tests/cheaders: check aarch64 under clang as well as gcc ...

Of the five lanes the header break took down, two compile with clang --
Android arm64 on NDK clang, macOS arm64 on Apple clang -- and two with
GNU. The lane only had gcc, so a divergence that clang alone rejects
would still reach CI. clang borrows the gcc cross sysroot, so it costs
one more invocation per header and nothing to install; the lane skips it
and says so if clang cannot reach the sysroot. Verified by putting the
broken header back with the two front ends' order swapped: clang reports
it on its own.

MSVC still has no real front end behind it, only the grep for the
const-initializer rule. clang's MSVC target needs a Windows SDK for even
assert.h, so it cannot run here. The header comment now says that
plainly rather than leaving the impression MSVC is covered: that one rule
is the only MSVC-specific breakage seen so far, and anything else it
rejects still reaches CI unchecked.

2026-09-22 03:26:55 +02:00

..

build.sh

tests/cheaders: check aarch64 under clang as well as gcc

2026-09-22 03:26:55 +02:00