Reference
Platform support
Distinguish native host support, implemented target profiles, available artifacts, and real boot evidence.
Native release-target contracts
Section titled “Native release-target contracts”| Archive target | Native qualification host | Binary compatibility contract |
|---|---|---|
x86_64-unknown-linux-gnu |
Native Linux x86-64 | glibc 2.36 or newer |
aarch64-unknown-linux-gnu |
Native Linux ARM64 | glibc 2.36 or newer |
aarch64-apple-darwin |
Native macOS Apple silicon | macOS 13 or newer |
The current AROS tools release has archives for the three hosts above. macOS Intel is not a native archive or package-manager target. See release status for current versions.
The host mapping is implemented in
host_compiler.rs.
Release checks inspect Linux GLIBC symbol requirements and macOS deployment
targets as well as running binaries natively.
AROS target profiles
Section titled “AROS target profiles”| Built-in profile | Target CPU | Platform | Compiler target triple |
|---|---|---|---|
pc-x86_64 |
x86-64 | PC | x86_64-unknown-aros |
arm-raspi |
ARM, hard float | Raspberry Pi | arm-unknown-aros |
rpi-aarch64 |
AArch64 | Raspberry Pi | aarch64-unknown-aros |
opensbi-riscv64 |
RISC-V 64 | OpenSBI | riscv64-unknown-aros |
A checkout’s aros-targets.toml, when present, replaces the
built-in profile contract.
Compiler selection is separately validated by the
CMake toolchain.
The opensbi-riscv64 profile has no matching published toolchain archive.
No RISC-V image or boot release is available. Mesa 26 translation currently
rejects this profile; its target-side LLVM/MCJIT backend is not qualified.
Physical boards
Section titled “Physical boards”The board schema models Pi 3, Pi 4, Pi 5 and Milk-V Titan. Model-specific DTBs, legacy KOBJ objects, firmware and transports are separate requirements. USB-ECM is reviewed only for Pi 4; Milk-V uses the OpenSBI/UEFI backend. See the board matrix.
The aros test implementation uses qemu-system-x86_64 and PC boot paths.
It is not a multi-architecture emulator frontend. Physical boards need their
own boot evidence.
The native PC BIOS ISO path has a fresh-build and QEMU user-mode qualification on macOS ARM64, plus a separate strict llvmpipe/LLVM-11 shader/JIT run. See the qualified inputs and limits. This is not a physical-board or UEFI qualification.
Component-specific limits
Section titled “Component-specific limits”| Component | Implemented boundary |
|---|---|
| Transpiler | Supported MetaMake semantics and explicit coverage reports; not arbitrary GNU Make execution |
| Verifier | architecture coverage profile; no core/distribution reachability profile |
| AHI runner | x86-64, ARM and AArch64 modes |
| ROM tool | PKG create/list/extract |
| External applications | Compiler/SDK reuse; no application packaging frontend |
| Board debugging | External serial terminal; JTAG/SWD and power fields are descriptive |
Standalone tools links these claims to their implementations.
Not currently supported
Section titled “Not currently supported”- Windows as a native release host.
- macOS Intel (
x86_64-apple-darwin) as a native archive or package-manager host. - Published Linux binaries on hosts below glibc 2.36, or macOS below 13.
- A general claim of complete translated products from entirely pristine upstream AROS.
- A blanket boot guarantee for every configured board or named profile.
Source builds on another host may be an experiment, but are not thereby a supported release target.