We are happy to announce the full availability of Qt Safe Renderer (QSR) 2.1 release. QSR 2.1 also has been certified by TUV.
Release Content
QSR 2.1 feature set has been discussed in previous blog posts, but here's a summary:
- Qt Safe Renderer Runtime and Qt Safe Renderer Tooling are divided into separate projects. See the updated building instructions on Building Qt Safe Renderer.
- Qt Safe Renderer building is only supported with CMake. Qt Safe Renderer examples can be still built also with qmake.
- Qt Safe Renderer building for INTEGRITY is supported. See Building for INTEGRITY.
- Evaluation package for NXP i.MX 8QuadMax
- Rendering output verification for NXP i.MX 8 Multisensory Enablement Kit (MEK) provides the output verification adaptation and new calccrc library for NXP i.MX 8.
- Event handler adaptation fixes for POSIX corrects the event handler adaptation and provides the timer functionality for animations and output verification.
- DRM graphics adaptation for NXP i.MX 8 Multisensory Enablement Kit (MEK) provides hardware overlay support for NXP i.MX 8.
- Animation data memory optimization implements memory pool allocation for animation data at startup. It replaces static memory allocation.
- The Event Sender example that you can use for sending events to Qt Cluster and Telltales examples. See Testing Safety-Critical Rendering and Events.
- Pre-built Qt Safe Renderer binaries built with Qt 6.5.8. Binaries are provided for the Qt Safe Renderer Runtime component, tools, and plugins.
- Improvements for Qt Safe Layout Tool QML and JavaScript parsing
How to get QSR 2.1
Existing Qt commercial users can now get the QSR 2.1 from the Qt Online Installer with a Device Creation Enterprise license.
Developer Guide and Reporting Bugs
The Qt Safe Renderer developer guide is available online.
If you have any problems with the QSR 2.1, please create bugs to https://bugreports.qt.io for the Qt Safe Renderer project.
