Wayland on Screen
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.
- libepoll
- libtimerfd
- libsignalfd
- libeventfd
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 QNX's public Git server at https://github.com/qnx/weston. The native QNX Screen backend implementation is in the qnx-sdp8-11.0.0 branch. For information on deployment and installation on your QNX system, go to the README.md located in the qnx folder.
- 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.