Policy reviewed 2026-09-28 in war-room/toolchains.toml. Runner, container and condition come from the workflow YAML. Validation records whether a platform has been proven, not merely configured.
Compiler policy#
The reusable workflows build with stable Rust, which moves. MSRV is a per-consumer input: empty skips the check, auto reads rust-version from Cargo.toml.
Every compiling job runs setup-llvm, which installs clang and lld and fails unless they match the LLVM major of the rustc in use. MSRV jobs get the older rustc's LLVM. The rollout is still in progress; see the LLVM campaign.
Reference measurement: rustc 1.98.1 (LLVM 22), clang/lld 22.1.8 and Luau 0.740, measured on Linux for L3i. A reference point, not an organization-wide pin.
Target matrix#
| Platform | Target | Baseline | Compiler | Validation |
|---|---|---|---|---|
| Linux x86_64 | x86_64-unknown-linux-gnu | CentOS Stream 9 / EL9; glibc 2.34 | Stream clang/lld must match rustc LLVM major | unknown |
| PortMaster ARM64 (opt-in) | aarch64-unknown-linux-gnu | EL9 aarch64 sysroot; glibc 2.34 | clang/lld + cross-language thin LTO | blocked |
| Android ARM64 (opt-in) | aarch64-linux-android | NDK r27c / Android API 23 | NDK target clang; host LLVM setup also runs | unknown |
| macOS ARM64 | aarch64-apple-darwin | macos-latest hosted runner | LLVM's official macOS ARM64 release, clang and lld matched to rustc | unknown |
| macOS x86_64 | x86_64-apple-darwin | macos-26-intel hosted runner | conda-forge clang / lld matched to rustc | unknown |
| Windows x86_64 | x86_64-pc-windows-msvc | windows-2025-vs2026 hosted runner | Upstream LLVM; clang-cl / lld-link for MSVC | unknown |
Linux x86_64#
The floor is deliberate: RHEL/AlmaLinux 9, Ubuntu 22.04, Debian 12 and newer. CentOS Stream and stable Rust move independently, so when their LLVM majors drift apart the build fails loudly on purpose.
- Job: rustGlobalBuild / release-linux
- Runner:
ubuntu-latest - Container:
ghcr.io/dreamweave-mp/stroggforge-linux-x86_64-el9-builder:v72 - Condition:
— - Strategy:
{"fail-fast":false,"matrix":{"app_names":"${{ fromJson(inputs.binary_names) }}"}}
PortMaster ARM64 (opt-in)#
Opt in with enable_portmaster. Builds now target glibc 2.34; the EL8 floor of 2.28 is gone. Nobody has run the new artifact on a device yet, so which handhelds it supports is an open question.
- Job: rustGlobalBuild / release-portmaster
- Runner:
ubuntu-latest - Container:
ghcr.io/dreamweave-mp/stroggforge-portmaster-aarch64-el9-builder:v72 - Condition:
inputs.enable_portmaster - Strategy:
{"fail-fast":false,"matrix":{"app_names":"${{ fromJson(inputs.binary_names) }}"}}
Android ARM64 (opt-in)#
Opt in with enable_android. You get a native ELF, not an APK. Matching the host's LLVM says nothing about whether NDK bitcode links with l3i's.
- Job: rustGlobalBuild / release-android
- Runner:
ubuntu-latest - Container:
— - Condition:
inputs.enable_android - Strategy:
{"fail-fast":false,"matrix":{"app_names":"${{ fromJson(inputs.binary_names) }}"}}
macOS ARM64#
Upstream LLVM from LLVM's own release archive, never Apple clang, whose version numbers are not LLVM's. Intentional difference: Apple consumers link with clang and lld but leave out -Clinker-plugin-lto, because rustc passes it GNU -plugin-opt arguments that ld64.lld rejects. The deployment floor follows the hosted runner image.
- Job: rustGlobalBuild / release
- Runner:
${{ matrix.os }} - Container:
— - Condition:
— - Strategy:
{"fail-fast":false,"matrix":{"os":["macos-latest","macos-26-intel","windows-2025-vs2026"],"app_names":"${{ fromJson(inputs.binary_names) }}"}}
macOS x86_64#
Built on its own Intel runner rather than trusting the ARM binary under Rosetta. LLVM publishes no Intel macOS build and Homebrew no longer bottles current LLVM for Intel, so the toolchain comes from conda-forge through a standalone micromamba, in its nocfg builds: the default ones linked jess 0.1.0 against conda's libc++ through an rpath into the runner's temp folder. Same linker-plugin-lto exception as ARM64.
- Job: rustGlobalBuild / release
- Runner:
${{ matrix.os }} - Container:
— - Condition:
— - Strategy:
{"fail-fast":false,"matrix":{"os":["macos-latest","macos-26-intel","windows-2025-vs2026"],"app_names":"${{ fromJson(inputs.binary_names) }}"}}
Windows x86_64#
LLVM comes from the upstream release archive, and C++ builds with clang-cl and links with lld-link. Intentional difference: setup-llvm pins CARGO_BUILD_TARGET to the host triple, so target rustflags stop reaching proc macros, which rustc refuses to build with -Clinker-plugin-lto on MSVC. The side effect is that output lands in target/
- Job: rustGlobalBuild / release
- Runner:
${{ matrix.os }} - Container:
— - Condition:
— - Strategy:
{"fail-fast":false,"matrix":{"os":["macos-latest","macos-26-intel","windows-2025-vs2026"],"app_names":"${{ fromJson(inputs.binary_names) }}"}}
Retired baselines are in the history.