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.
Graphics
Screen Graphics Subsystem Developer's Guide
QNX Screen Graphics Subsystem is a graphics framework that provides all the functionality necessary to develop interactive user experiences.
Wayland on Screen
Running Wayland on the Screen Graphics Subsystem provides a C library implementation of the core Wayland communication library.

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
  - Gestures Library Reference
    The Gestures library provides gesture recognizers to detect gestures through touch events that occur when you place one or more fingers on a touch screen.
  - Image Library Reference
  - Input Events Library Reference
    The Input Events library provides the framework necessary for Screen Graphics Subsystem to communicate with your touch driver.
  - OpenWF Configuration Developer's Guide
    If you are integrating a new display, you must configure and provide the parameters of your display based on its specifications via the OpenWF Display Configuration API (Wfdcfg Library).
  - Screen Graphics Subsystem Developer's Guide
    QNX Screen Graphics Subsystem is a graphics framework that provides all the functionality necessary to develop interactive user experiences.
    - Application Development
      The Screen Graphics Subsystem is based on a client/server model where an application is a client that's requesting graphics services from the server (Screen). It includes a composited windowing system as one of these services, which means all application rendering is performed on off-screen buffers, which then can be later used to update the display.
    - Buffers
      A buffer is an area of memory that stores pixel data. Multiple buffers can be associated with a window or stream, but only one buffer can be associated with a pixmap.
    - Rendering
      Rendering refers to the generation of an image.
    - Windowing
      Windows are used to display content and to combine content produced by different renderers. Each of the different renderers can be in the same process, or in another process or processes.
    - Resource Sharing
      Resource sharing allows the access of buffers and their content within the same application and process, or between different applications and processes.
    - Displaying the contents of windows
      Displays are used to show the contents of your windows on physical hardware such as a computer monitor or a touchscreen display.
    - Cursor Movement
      There is more than one way to set up cursor movement between multiple displays.
    - Input
      One key aspect of Screen that enables the development of fully interactive user experiences is the functionality to support input events and to deliver input and notifications back to applications.
    - Event Handling
      Screen events, which include both input and general events, are associated with a given context and are generally handled in your main application's loop.
    - Asynchronous Notifications
      Applications can request to be asynchronously notified of specific Screen events by way of a sigevent.
    - Permissions and Privileges
    - Security policies
      This section on Screen security policies is intended for system integrators who are responsible for implementing and enforcing security policies that create and maintain a trusted execution environment.
    - Utilities and binaries
      Screen includes some utilities and binaries to help with calibration, debugging, and demonstrating features.
    - Debugging
      Debugging graphics isn't easy. Figuring out where the problem is can be challenging because of the many aspects and components when it comes to graphics. The goal of this chapter is to show the tools and techniques that you can use to help with your investigation.
    - Wayland on Screen
      Running Wayland on the Screen Graphics Subsystem provides a C library implementation of the core Wayland communication library.
    - Screen library reference
      Two important aspects to note when using Screen are function safety and function execution types.
    - Configuring Screen
      You configure libraries, drivers, and Screen parameters using the configuration file, graphics.conf.
    - Glossary
  - Video Capture Developer's Guide
    The video capture framework provides applications the ability to capture frames from a video input source. These frames can be passed to a graphics component such as Screen for display.
- 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 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.
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.

Wayland on Screen

Graphics and Screen4.0 (8.x)Screen Graphics Subsystem Developer's GuideAPIProgrammingUtilities

Running Wayland on the Screen Graphics Subsystem provides a C library implementation of the core Wayland communication library.

The implementation is an inter-process communication library that translates protocol definitions, defined in XML, to a C language API that both Wayland clients and servers can use. For more information, refer to the online Wayland documentation available at https://wayland.freedesktop.org/docs/html/index.html. This document covers information specific to Screen.

Components

The core Wayland components are provided in the package com.qnx.${baselineId}.target.screen.wayland, where ${baselineId} refers to the SDP version.

To use Wayland on Screen, you need to link the following libraries:

libepoll
libtimerfd
libsignalfd
libeventfd

You can find these libraries in the com.qnx.${baselineId}.target.screen.notify_fd package. You also need to link the libffi library available with QNX SDP.

Weston

Wayland is not a compositor; to utilize Wayland, you need to design or choose an existing implementation such as Weston. Weston is ported to QNX with a Screen native backend implementation; similar to the X11 backend for Wayland. This allows Weston to run natively on QNX and interface with Screen to display content on your target display.

To get started with Wayland on QNX Screen, refer to the README.md on QNX's public Git server at https://github.com/qnx/weston.

Note:

Weston is not a replacement for Screen. The Screen backend in Weston allows it to composite Wayland windows onto a Screen native root window. Screen permissions, security, window management, etc. all apply to the root window. Screen must be configured accordingly, based on your system requirements.
You cannot mix Wayland windows with Screen windows. Screen windows cannot be composited in the context of a Wayland compositor, and vice versa.

Page updated: August 09, 2024