The os2.build buildfile is given below. Note that this image filesystem is always read-only.
# set search path for files
[search=/usr/qnx630/target/qnx6/ppcbe/bin:/usr/qnx630/target/qnx6/ppcbe/sbin:/usr/qnx630/target/qnx6/ppcbe/usr/bin:/usr/qnx630/target/qnx6/ppcbe/usr/sbin]
# code=uip means that the code will be run from the image filesystem
# (Use In Place).
#
# +raw means to not strip the programs in any way
[data=copy code=uip]
[perms=+r,+x]
# my files to include
# these files will reside directly under the mountpoint as specified
# with the mount command
[+raw] /raw/hd=hd
/unraw/hd=hd
devc-ser8250
io-net
# these files will be placed
/bin/use=use
Unlike the build script for a bootable OS image, the XIP script doesn't have a boot section, nor does it have a boot script. If you run mkifs -v on this buildfile, you'll see that the first entry is the image filesystem header rather than the startup code normally found in a bootable image.