Home
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 OS applications and systems.
Developing QNX Projects
To use the QNX Toolkit to write applications targeted for QNX OS systems, you must define projects, which are folders in the filesystem. A VS Code workspace is a collection of these folders and VS Code settings defined by the .code-workspace file. QNX projects are saved to a folder defined in a your configuration (default location is ~/qnxprojects).
Creating a project
You can create several different types of projects.

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 OS applications and systems.
- About the QNX Toolkit
- Using the Target Navigator
  The QNX development environment consists of a host and a target machine.
- Developing QNX Projects
  To use the QNX Toolkit to write applications targeted for QNX OS systems, you must define projects, which are folders in the filesystem. A VS Code workspace is a collection of these folders and VS Code settings defined by the .code-workspace file. QNX projects are saved to a folder defined in a your configuration (default location is ~/qnxprojects).
  - Creating a project
    You can create several different types of projects.
  - Configuring an existing project
    Once you've created a project, you can configure it using the QNX Toolkit.
- Debugging and Launching
- Using the System Profiler
  You can use the System Profiler to render different types of trace analysis, such as graphs and tables.
- References
  The reference topics provide information about QNX Toolkit features and workflows that isn't covered in the other chapters.
- Glossary
  To make best use of the QNX Toolkit, we recommend that you become familiar with the following terms, which are used throughout the user interface and documentation.
- Typographical Conventions, Support, and Licensing
  This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Creating a project

Updated: November 27, 2023

You can create several different types of projects.

The following project types are available:


Project Type	`Recommended usage`
QNX Recursive Makefile	To create an application or library project which uses QNX's recursive make build system.
Simple Makefile	To build a QNX OS application or utility using a traditional makefile.
None	To create an empty QNX project.
QNX CMake Project	To create an application or library project which uses the CMake build system, in conjunction with the QNX compiler tool chain.
Other	To create a custom project.

Create a QNX recursive makefile project

To create a QNX recursive makefile project:

From the command palette, click Create New QNX Project.
Enter a name for the project.
Select QNX Recursive Makefile.
Select the project language.
Select artifact type (Executable, Shared Library, or Shared Library and Test Executable). The project is created and you can view the directory structure in the Workspace.

Create a simple makefile project

You can create a simple, GNU-style makefile.

To create a simple makefile project:

From the command palette, click Create New QNX Project.
Enter a name for the project.
Select Simple Makefile.
Select the project language.
Select artifact type (Executable, Shared Library, or Shared Library and Test Executable). The project is created and you can view the directory structure in the Workspace.

Create a QNX CMake Project

You can create a QNX CMake project. This type of project uses the CMake build system, in conjunction with the QNX compiler toolchain.

To create a QNX CMake project:

From the command palette, click Create New QNX Project.
Enter a name for the project.
Select QNX CMake Project.
Select project language.
Select artifact type (Executable, Shared Library, and Shared Library and Test Executable). The project is created and you can view the directory structure in the Workspace.