Product: Platform_Toolchain_QNX, QNX cross-toolchain scaffold (repository Platform_Toolchain_QNX). Layer: build infrastructure, not linked into any product and not safety-rated.

Scaffold for a real QNX cross-toolchain (host tools + target sysroot from the QNX Software Development Platform). No toolchain is present here yet — QNX SDP is a licensed BlackBerry product that cannot be fetched, downloaded, or vendored by this project. This project holds the structure, docs, and CMake integration so that dropping in a real SDP later is a drop-in, not a redesign.

Status: scaffold only

bin/, lib/, include/, sdp/ are empty (gitignored). setup.sh exits with a clear error until given a real SDP install to work from — it is not a downloader.

Once you have a licensed SDP

./setup.sh /path/to/qnx-sdp-root

symlinks bin/qcc etc. from the SDP's own host/<platform>/.../usr/bin/, and records QNX_TARGET=<sdp-root>/target/qnx7 for the CMake toolchain file. Then:

cmake -S ../../Platform_RTE -B build-qnx \
    -DCMAKE_TOOLCHAIN_FILE=cmake/Toolchain-QNX.cmake \
    -DQNX_HOST=$(pwd)/bin -DQNX_TARGET=/path/to/qnx-sdp-root/target/qnx7/x86_64

(Same QNX_HOST/QNX_TARGET contract Platform_RTE/cmake/Toolchain-QNX.cmake already expects — this project only supplies the paths.) ./verify.sh becomes meaningful once a real SDP is wired in — it will cross-compile a trivial hello-world via qcc, mirroring Platform_Toolchain_Linux's verify.sh.

Interface exposed to other products

Interface	Form	Consumed by
Toolchain: cmake/Toolchain-QNX.cmake (delegates to Platform_RTE cmake/Toolchain-QNX.cmake)	-DCMAKE_TOOLCHAIN_FILE=<path> passed to any CMake build	Every C product that needs a cross-build for QNX (needs a licensed SDP)

Nothing links against this project. It is consumed only by CMake and by the RBC_Test_Env build scripts (build_toolchains.sh).

Related products

Sibling toolchains: Platform_Toolchain_MacOS, Platform_Toolchain_Linux, Platform_Toolchain_FreeRTOS. Working notes: CLAUDE.md.