For the most part, BSPs for QNX SDP 6.6 work the same way as they did under previous QNX OS versions. Some important changes have been introduced, however.
Prior to the release of SDP 6.6, QNX did not always supply prebuilt binaries and libraries for its BSPs. If the source code for a BSP component was included with the BSP, QNX didn't supply prebuilt binaries and libraries for that component. If the source code for a component was not included with a BSP, QNX supplied prebuilt binaries and libraries for that component.
Starting with QNX SDP 6.6, QNX supplies prebuilt binaries and libraries for all BSP components (device drivers, libraries, utilities, etc.). These are prebuilt and packaged with the BSP, regardless of whether or not the source code for those components is included with the BSP. This new packaging model ensures that our customers receive exactly the same checksum-compatible BSP components that we tested. Even if you choose to modify a BSP component by changing the source code and building your own version, you'll always have a copy of the original BSP version available in the BSP archive.
As with previous QNX OS versions, with QNX SDP 6.6, when a BSP is built, the entire contents of the BSP's /prebuilt directory gets copied into its /install directory. This means that all BSP components mentioned above can be found in the /install directory. This directory is the first one searched when a target IFS image is generated.
However, the binaries, libraries, and utilities that get built from the source code included with the BSP are no longer copied to the /install directory by default. This means that if you want to modify the BSP source code, making changes to specific device drivers or other components, you must execute a make install command when building that code. This command is required so that the resultant binaries, libraries, and utilities get copied into the BSP's /install directory, where they can be found and included when the IFS image is built.