Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
OS Components & Operations
Building Embedded Systems
The Building Embedded Systems guide is intended for developers who are developing or building BSPs for QNX OS embedded systems.
Sample Buildfiles
This appendix contains sample buildfiles that you can modify to support your hardware platform and your implementation requirements.
Temporary in-memory filesystem
You can use your buildfile to create a temporary filesystem based on shared memory objects.

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components & Operations
  - Boot Optimization Guide
    The Boot Optimization Guide describes techniques you can use to reduce the time from your board's initial power on until you have a fully functional QNX system running on the board.
  - Building Embedded Systems
    The Building Embedded Systems guide is intended for developers who are developing or building BSPs for QNX OS embedded systems.
    - Overview
      QNX systems are built from the QNX OS standard release components, the architecture- and board-specific files provided in QNX BSPs, and customer and third-party components.
    - Working with QNX BSPs
      Before you attempt to write a new BSP or modify an existing one, it is helpful to know how to use a BSP.
    - Initial Program Loaders (IPLs)
      IPLs first set up the minimum environment needed to execute their compiled C code, then find the OS image and load it into memory, and then jump to the QNX startup code.
    - Startup Programs
      The first program to run in a bootable OS image is the startup program; it completes the system configuration, then launches the OS kernel.
    - Kernel Callouts
      Kernel callouts are standalone pieces of code (or code fragments) that the kernel uses to perform hardware-specific functions. These callouts don't need to be statically linked to the kernel.
    - System Page
      The system page contains essential information about the system, including the system page's size, information about the hardware platform (including IRQs and the CPUs), the cache size, and the location of kernel callouts in memory.
    - OS Images
      OS images are files that contains the OS, your executables, and any data files that might be related to your programs.
    - OS Image Buildfiles
      You can edit OS image buildfiles to configure OS images.
    - IPL Library
      The IPL library contains a set of routines for building a custom IPL.
    - Startup Library
      The startup library contains a rich set of routines ranging from high-level functions called by main() to utility functions for performing specific startup tasks.
    - Debugging QNX Embedded Systems
      The microkernel architecture of QNX OS means that debugging QNX embedded systems can be different from debugging other embedded systems.
    - Sample Buildfiles
      This appendix contains sample buildfiles that you can modify to support your hardware platform and your implementation requirements.
      - Shared libraries
        Your buildfile must tell the build process to include in the image all of the shared objects required by the drivers you'll be running.
      - Using multiple consoles
        If your system supports multiple consoles or multiple serial ports, you can run the shell on each console and serial port.
      - Minimal configuration
        This buildfile does the minimum necessary to give you a shell prompt on the first serial port.
      - Temporary in-memory filesystem
        You can use your buildfile to create a temporary filesystem based on shared memory objects.
      - Flash filesystem
        This buildfile starts up the flash filesystem on an x86 board.
      - Disk filesystem
        This buildfile includes support for a filesystem for rotating media.
      - TCP/IP with network filesystem
        This buildfile starts up an Ethernet driver, the TCP/IP stack, and the network filesystem.
    - Glossary
  - Customizing a BSP
    While QNX provides Board Support Packages (BSPs) for many common platforms and their individual variants, in some cases, you need a BSP for a board that QNX does not provide. If this is the case, you can modify a QNX BSP or develop your own.
  - Device Publishers Developer's Guide
  - High Availability Framework Developer's Guide
  - High-Performance Networking Stack (io-sock) User's Guide
    This guide contains instructions for implementing and using the QNX OS High-Performance Networking Stack and its manager, io-sock.
  - PCI Server User's Guide
  - Performance Tuning User's Guide
  - QNX Filesystem for Safety User's Guide
  - QNX Process Launch and Monitor Service User's Guide
    The QNX Process Launch and Monitor Service (QPLMS) user's guide is intended for developers who are implementing the service in a QNX OS-based system.
  - SMMUMAN User's Guide
  - System Analysis Toolkit (SAT) User's Guide
  - Technotes
  - User's Guide
    The QNX OS User's Guide is intended for all users of a QNX OS system, from system administrators to end users.
- Graphics
- Programming
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX software in Amazon Web Services (AWS) and Microsoft Azure (Azure).
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor and QNX Hypervisor for Safety
The QNX Hypervisor and QNX Hypervisor for Safety products allow you to run multiple OSs on a target system so you can separate critical and non-critical functions, support a wide variety of applications, and reduce hardware costs.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Temporary in-memory filesystem

QNX SDP8.0Building Embedded SystemsConfigurationDeveloper

You can use your buildfile to create a temporary filesystem based on shared memory objects.

QNX OS provides a simple Shared Memory Object filesystem that allows read/write files to be placed under /dev/shmem (see Shared Memory Object filesystem in the QNX OS User's Guide). You can link /dev/shmem to the /tmp directory to use it store data in temporary files.

Note:

This buildfile example provided here is useful for demonstration systems that do not have a persistent filesystem. However, it is not a full-featured filesystem (e.g., mkdir is not supported) and should not be used as /tmp for a production system.

You can include the following instruction in a script file within your buildfile:

[+script] startup-script = {
    procmgr_symlink /dev/shmem/ /tmp
    ...

This instruction sets /tmp as a symbolic link in the process manager's pathname table; this symbolic link points to the /dev/shmem directory. Because this directory is where shared memory objects are stored, this link lets you create a temporary filesystem based on shared memory objects.

For an explanation on why it's best to use procmgr_symlink to create the link, as well as guidance on using an alternative mechanism to provide a temporary in-memory filesystem for a production system, see the mkifs buildfile examples in the Utilities Reference.

Page updated: June 11, 2026