RAX v0.1.2

Prebuilt RAX C/C++ SDKs contain shared and static libraries, rax.h, the header-only C++17 wrapper rax.hpp, CMake/pkg-config metadata, and build provenance.

• Select the archive matching your host architecture and OS/toolchain ABI.
• x86-64 binaries use the baseline x86-64 CPU target. AArch64 binaries use the generic target.
• Linux x86-64 is built on Ubuntu 22.04; AArch64 on Ubuntu 24.04. These are the tested Linux runtime baselines, not a promise of compatibility with older glibc. Exact symbol requirements are in build-info.json.
• macOS targets deployment version 11.0; runtime tests run on macOS 15.
• Windows binaries target MSVC with the dynamic CRT; Windows ARM64 is an experimental candidate. GNU/MinGW libraries are not included in this release matrix.
• Experimental candidate archives can additionally cover Linux RISC-V, PowerPC64 (both byte orders), s390x, and x86-64/AArch64 musl. Candidates are included only when their complete SDK execution gates pass; absence means that lane did not deliver a validated artifact for this release.
• GNU/Linux candidates are cross-built in a pinned Rust/Debian container and tested with QEMU user emulation and target sysroots. This is not physical-hardware validation. musl candidates build and execute in native pinned Rust/Alpine containers and use the dynamic musl CRT for both library variants.
• These SDKs use the interpreter. JIT, KVM, HVF, and trace features are disabled.
• Both C and C++ consumers are compiled and executed against shared and static libraries after SDK relocation. Rust C API tests must also pass without ignored or filtered cases before publishing. Build metadata identifies experimental status, execution mode, toolchain, and test counts.

Every SDK is accompanied by a -debug archive built from the same compilation, holding the debug information split out of the shipped libraries: librax.so.debug plus the unstripped librax.a on Linux, librax.dylib.dSYM plus the unstripped librax.a on macOS, and rax.pdb on Windows. The SDK archive alone is enough to build and run; download the matching -debug archive when you need symbols in a debugger or crash report. build-info.json lists the sidecars under debug_info and the level under debug. That level is Cargo's limited: function names, source files and line numbers, which covers symbolicated backtraces, profilers and crash reports, but not local variable inspection.

Each archive has an adjacent SHA-256 checksum and an internal file checksum manifest. See the included README for linking instructions. Shared libraries still depend on OS libraries; static archives require the documented system link dependencies.