Details
-
Epic
-
Resolution: Out of scope
-
P1: Critical
-
None
-
None
-
None
-
Extend QPA for all aspects of target HW
-
Description
Business justification
In embedded, we need to support several environment and operating systems (Yocto Embedded Linux and several derivates of it, INTEGRITY, QNX, VxWorks, and in MCU also MQX, Zephyr, freeRTOS, RTEMS and possibly few other), sometimes also bare metal (QSR, MCU). The POSIX layer may or may not be available in those operating systems and it alone is inadequate for a HW and OS abstraction layer we there is a lot of work going in to supporting the various target platforms. In order to separate the maintenance work for OS and HW porting we should consider extending the QPA layer (or whatever is the Qt6 extension of it) to cover areas outside of Qt5 QPA.
Implementation details
Extend QPA, OS and HW abstraction layer to cover also
- File system
- POSIX or lack of POSIX
- Networking and connnectivity
- Memory allocation
- Event loops, threads, etc Etc
Attachments
Issue Links
- depends on
-
QTBUG-75638 Qt Network changes in Qt 6
- Closed
-
QTBUG-66135 Improve Qt and Metal interoperability
- Closed
-
QTBUG-74406 Abstract away the graphics APIs in Qt
- Closed
- is duplicated by
-
QTBUG-74514 QPA improvements for Qt Core
- Withdrawn
- is required for
-
QTBUG-73666 Configurable Qt
- Closed
-
QTBUG-74396 Technical enhancements of the Qt framework
- Closed
-
QTBUG-74403 Modernize the Qt graphics stack
- Closed
-
QTBUG-74398 Scaling down on small hardware
- Withdrawn
- relates to
-
QTBUG-70095 QWindowSystemInterface synchronous mode
- Reported
-
QTBUG-70518 Make platform plugins libraries with their own private headers
- Closed