pub const DUCKDB_PLATFORMS: &[&str];Expand description
Every platform identifier validate_platform recognises.
This is DUCKDB_CI_PLATFORMS — the architectures the community-extension
CI builds — plus names that appear in real, accepted description.yml
files and are therefore not errors:
windows_amd64_rtools, the name olderDuckDBreleases gave the R-tools Windows build.DuckDBPlatform()in v1.5.5’sduckdb/common/platform.hppmapsDUCKDB_PLATFORM_RTOOLSto the_mingwsuffix instead, so current builds reportwindows_amd64_mingw; the old name is not in the distribution matrix either, but 84 of the 346 extensions induckdb/community-extensions(commit5ae7df8, 2026-09-23) still exclude it.windows_arm64_mingw, which v1.5.5’sDuckDBPlatform()produces for a MinGW build on arm64 (_mingwpostfix on thearm64arch). Not in the distribution matrix; three of those 346 extensions exclude it.- The group names in
DUCKDB_PLATFORM_GROUPS—linux,osx,wasm,windows— which are the top-level keys ofdistribution_matrix.jsonand appear in at least one published extension’s exclusion list. They are accepted, not meaningful: seeDUCKDB_PLATFORM_GROUPS.
An extension must either build for all of the non-opt-in CI platforms or
declare the ones it cannot in extension.excluded_platforms.
linux_amd64_gcc4 is not here — see DUCKDB_RETIRED_PLATFORMS.