Qt 6.3 Known Issues: Difference between revisions
Jump to navigation
Jump to search
m (Jani Heikkinen moved page Qt 6.3.0 Known Issues to Qt 6.3 Known Issues) |
mNo edit summary |
||
Line 5: | Line 5: | ||
==All platforms== | ==All platforms== | ||
==== Qt Quick 3D ==== | |||
Global scaling is not applied on asset import ([https://bugreports.qt.io/browse/QTBUG-104118 QTBUG-104118]). | |||
==Linux== | ==Linux== | ||
Qt applications using QProcess crash when run in qemu ([https://bugreports.qt.io/browse/QTBUG-98951 QTBUG-98951]) or under valgrind ([https://bugreports.qt.io/browse/QTBUG-87230 QTBUG-87230]). | Qt applications using QProcess crash when run in qemu ([https://bugreports.qt.io/browse/QTBUG-98951 QTBUG-98951]) or under valgrind ([https://bugreports.qt.io/browse/QTBUG-87230 QTBUG-87230]). | ||
Line 14: | Line 18: | ||
It's impossible to run Qt tests when building Qt from sources with a custom CMAKE_PREFIX_PATH containing Windows format paths with backslashes. | It's impossible to run Qt tests when building Qt from sources with a custom CMAKE_PREFIX_PATH containing Windows format paths with backslashes. | ||
* Workaround: Use paths in CMake format to specify CMAKE_PREFIX_PATH when building Qt. | *Workaround: Use paths in CMake format to specify CMAKE_PREFIX_PATH when building Qt. | ||
==Android== | ==Android== |
Revision as of 07:38, 13 June 2022
- Check that your system meets Qt's requirements
- All open issues can be found from Jira
- RTA findings here
- Supported development platforms are listed here
All platforms
Qt Quick 3D
Global scaling is not applied on asset import (QTBUG-104118).
Linux
Qt applications using QProcess crash when run in qemu (QTBUG-98951) or under valgrind (QTBUG-87230).
- Workaround: configure Qt with
-no-feature-forkfd_pidfd
macOS
Windows
It's impossible to run Qt tests when building Qt from sources with a custom CMAKE_PREFIX_PATH containing Windows format paths with backslashes.
- Workaround: Use paths in CMake format to specify CMAKE_PREFIX_PATH when building Qt.
Android
iOS
WebAssembly
Qt applications which use time zone or calendar functionality may fail to link, with errors like "error: undefined symbol: _get_daylight" (QTBUG-101267). Workaround: build Qt from source using a more recent emsdk version, for example 3.1.6.