Home /Modules/docs/PLATFORM-SUPPORT.md

PLATFORM-SUPPORT.md

docs/PLATFORM-SUPPORT.md · 87 line(s) · markdown

Platform Support and Validation Matrix

This matrix separates intended targets from evidence. A target is not fully supported merely because source code contains a backend.

AreaLinuxmacOSWindows 10+Interpretation
Native C/C++ implementationBuild targetBuild targetBuild targetRequire a fresh native build and tests on each release runner
Terminal / process supportCI exercisedCI exercisedNot established by current Terminal matrixSee Terminal platform notes
User Interface toolkitX11 workflowCocoa workflowWin32/MinGW workflowConfirm latest run on each OS before release claims
Full repository test suiteCI configuredNot all layers necessarily runNot all layers necessarily runKnown failures remain; do not describe the whole repository as green until resolved

Full repository build contract

The root make all target is the authoritative default build. It dispatches the native runtime, XLT compiler, Java 28 bridge, regex/compiler/VM packages, installer checks, tutorial validation, native smoke tests, configuration checks, CommonRails, codecs, churn data checks, antivirus, registry, all eleven premium SLVM runners, and Ballum. The optional database/data-source connector and API server targets remain explicit because they have additional external dependencies.

The default build requires:

Host prerequisites

HostRecommended toolchainAdditional development packages
LinuxGCC/G++ or Clang, GNU MakeOpenSSL development package, X11/XRandR/Xext, FreeType, Fontconfig, pkg-config
macOSXcode Command Line Tools, Apple Clang, GNU MakeHomebrew OpenSSL 3 and pkg-config; Apple frameworks come from the SDK
Windows 10+MSYS2 UCRT64 MinGW-w64 GCC/G++, GNU Make, BashOpenSSL and pkgconf from the matching UCRT64 repository; JDK 28 with JNI headers

Windows builds are supported through MinGW-w64, not MSVC. The current native runtime compatibility layer uses GCC-specific facilities (including #include_next). Run the root build from an MSYS2 UCRT64 shell so the POSIX build utilities used by the Makefiles are available. Winsock is linked through ws2_32; native executables use the .exe suffix.

Example Windows MSYS2 package installation:

pacman -S --needed base-devel mingw-w64-ucrt-x86_64-gcc \
  mingw-w64-ucrt-x86_64-openssl mingw-w64-ucrt-x86_64-pkgconf

Build and validation sequence

After intentional source changes, regenerate the trusted manifest from the repository root before running the fail-closed build gate:

make -C impl regen-manifest
make all

The make all target invokes the repository's default tests and smoke checks; it is not a substitute for a fresh host-specific release qualification. Record the compiler/JDK versions and the actual command output for each OS. Do not mark a platform green based only on source-level portability changes or a successful dry run.

The platform helper scripts have narrower scopes: scripts/build-linux.sh, scripts/build-macos.sh, and build-windows.ps1 build the core runtime and XLT compiler. They do not replace the root make all repository build.

Validation rules

  1. Record OS, compiler/toolchain, build command, and test command for each release candidate.
  2. Mark optional SDK-dependent modules as skipped when appropriate.
  3. A workflow run with zero jobs is not a passing validation.
  4. Report failed and pending runs accurately; do not infer success from old runs.
  5. Require fresh green runs on the exact release commit for every claimed supported platform.

Entry points

This is a validation contract, not a claim that every component is production-ready.