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 ../safeAPIFreamwork -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 safeAPIFreamwork/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 LinuxMacOSToolchain's verify.sh.

Scope

100% dependent on a licensed SDP being supplied — nothing is vendored or installed automatically. Untested against a real SDP (none was available during this project's development); the CMake integration mirrors safeAPIFreamwork/cmake/Toolchain-QNX.cmake's existing variable contract but hasn't been exercised end-to-end the way the other three toolchain projects were.