When it looks for files to include in the OS image it is building, mkifs uses the path
set by the MKIFS_PATH environment variable. If MKIFS_PATH isn't set, it searches
its default paths.
The mkifs search paths
When it builds an image, by default mkifs searches for components along the path set
in the MKIFS_PATH environment variable.
If MKIFS_PATH is not set, mkifs searches for the components in:
- the current working directory, if the component's filename contains a slash (but doesn't
start with one)
- the directories listed below (The PROCESSOR environment variable is set by a
buildfile attribute; see “Specifying the board architecture”)
- Binaries (esh, ls, etc.)
- ${QNX_TARGET}/${PROCESSOR}/bin
- ${QNX_TARGET}/${PROCESSOR}/usr/bin
- ${QNX_TARGET}/${PROCESSOR}/sbin
- ${QNX_TARGET}/${PROCESSOR}/usr/sbin
- OSs (procnto*, etc.)
- ${QNX_TARGET}/${PROCESSOR}/boot/sys
- Libraries and shared objects
- ${QNX_TARGET}/${PROCESSOR}/lib
- ${QNX_TARGET}/${PROCESSOR}/usr/lib
- Shared objects
- ${QNX_TARGET}/${PROCESSOR}/lib/dll
For information about how to change where mkifs searches for the components it places
in the OS image it is building, see “Changing where mkifs looks for files” below.