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.
Programming
Programmer's Guide
The QNX OS Programmer's Guide covers a variety of topics that might interest developers who are building applications that will run under the QNX OS.
Conventions for Recursive Makefiles and Directories
In this chapter, we'll look at the supplementary files used in the QNX OS development environment. Although we use the standard make command to create libraries and executables, we also use some of our own conventions in the Makefile syntax.
Using the standard macros and include files
The qtargets.mk include file
The qtargets.mk include file has the linking and installation rules.

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
- Graphics
- Programming
  - Getting Started with the QNX OS
    Getting Started with the QNX OS: A Guide for Realtime Programmers is intended to introduce you to the QNX OS and help you develop applications and resource managers for it.
  - Programmer's Guide
    The QNX OS Programmer's Guide covers a variety of topics that might interest developers who are building applications that will run under the QNX OS.
    - Compiling and Debugging
      Let's start by looking at some things you should consider when you start to write a program for the QNX OS.
    - QNX OS Architecture and Concepts
      The QNX OS architecture consists of the microkernel and several cooperating processes. These processes communicate with each other via various forms of interprocess communication (IPC). Message passing is the primary form of IPC in QNX OS.
    - Processes
      Your applications should be written in a way that reflects the architecture of the QNX OS—as a set of cooperating processes. In this chapter, we see how to start processes (also known as creating processes) from code, how to terminate them, and how to detect their termination.
    - Multicore Processing
      Multiprocessing systems, whether discrete or multicore, can greatly improve your applications' performance.
    - Working with Access Control Lists (ACLs)
      Some filesystems, such as the Power-Safe (fs-qnx6.so) and QNX compressed filesystems, extend file permissions with Access Control Lists, which are based on the withdrawn IEEE POSIX 1003.1e and 1003.2c draft standards.
    - Understanding the Microkernel's Concept of Time
      Whether you're working with timers or simply getting the time of day, it's important that you understand how the OS works with time.
    - Handling Hardware Interrupts
      This chapter explains the QNX OS mechanisms for quickly reacting to hardware events.
    - Working with Memory
      (or The Persistence of Memory, with a nod to Salvador Dali) In the Process Manager chapter of the System Architecture guide, we looked at how the OS manages memory. This chapter describes how you can work with memory.
    - Freedom from Hardware and Platform Dependencies
      The QNX OS can run on many different hardware platforms. The way in which applications can access peripheral devices and how data is stored varies between platforms. This chapter explains our solutions for minimizing the impact of such platform dependencies.
    - Conventions for Recursive Makefiles and Directories
      In this chapter, we'll look at the supplementary files used in the QNX OS development environment. Although we use the standard make command to create libraries and executables, we also use some of our own conventions in the Makefile syntax.
      - Structure of a multiplatform source tree
      - Specifying options
      - Using the standard macros and include files
        The qconfig.mk include file
        Since the common makefiles have a lot of defaults based on the names of various directories, you can simplify the common.mk include file if you choose your directory names to match what the common makefiles want.
        The qdepfile.mk include file
        The qdepfile.mk include file provides support for dependency list generation to the qcc compiler.
        The qrules.mk include file
        The qrules.mk include file defines the macros used for compiling.
        The qtargets.mk include file
        The qtargets.mk include file has the linking and installation rules.
      - Advanced topics
      - Examples of creating Makefiles
        If you use our directory structure, you should use the addvariant command to create it. This section gives some examples of creating Makefiles for a single application, as well as for a library and an application.
    - Glossary
  - Writing a Resource Manager
- 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 OS in the Amazon cloud environment.
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 User's Guide
This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX Hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
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.

The qtargets.mk include file

QNX SDP8.0Programmer's GuideDeveloper

The qtargets.mk include file has the linking and installation rules.

You can inspect and/or set the following macros when you use qtargets.mk:

INSTALLDIR

The subdirectory where the executable or library is to be installed. Defaults to bin for executables, and lib/dll for DLLs. If you set it to /dev/null, then no installation is done.

USEFILE

The file containing the usage message for the application. Defaults to none for archives and shared objects and to $(PROJECT_ROOT)/$(NAME).use for executables. The application-specific makefile can set the macro to a null string, in which case nothing is added to the executable.

LINKS

A space-separated list of symbolic link names that are aliases for the image being installed. They're placed in the same directory as the image. The default is none.

PRE_TARGET, POST_TARGET

Extra targets to add as dependencies to the all target before and after the main target.

PRE_CLEAN, POST_CLEAN

Extra commands to run before and after the clean target.

PRE_ICLEAN, POST_ICLEAN

Extra commands to run before and after the iclean target.

PRE_HINSTALL, POST_HINSTALL

Extra commands to run before and after the hinstall target.

PRE_CINSTALL, POST_CINSTALL

Extra commands to run before and after the cinstall target.

PRE_INSTALL, POST_INSTALL

Extra commands to run before and after the install target.

PRE_BUILD, POST_BUILD

Extra commands to run before and after building the image.

SO_VERSION

The SONAME version number to use when building a shared object (the default is 1).

Note:

In this release, the version number is required for the internal name of the shared object, so setting this macro is mandatory. For more information, see Specifying an internal name.

PINFO

Information to go into the *.pinfo file.

For example, you can use the PINFO NAME option to keep a permanent record of the original filename of a binary. If you use this option, the name that you specify appears in the information from the use -i filename command. Otherwise, the information from use -i contains the NAME entry specified outside of the PINFO define.

For more information about PINFO, see the hook_pinfo() function described below for the GNU configure command.

Page updated: March 05, 2025