Qt 6.3 Known Issues: Difference between revisions
m (→WebAssembly: Add Qt for Wasm known issue) |
No edit summary |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
*Check that your system meets [https://doc | *Check that your system meets [https://doc.qt.io/qt-6/supported-platforms.html Qt's requirements] | ||
*All open issues can be found from [https://bugreports.qt.io/issues/?filter=23977 Jira] | *All open issues can be found from [https://bugreports.qt.io/issues/?filter=23977 Jira] | ||
**RTA findings [https://bugreports.qt.io/issues/?filter=23976 here] | **RTA findings [https://bugreports.qt.io/issues/?filter=23976 here] | ||
==All platforms== | ==All platforms== | ||
====Qt Quick 3D==== | |||
v6.3.1 - 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 12: | Line 15: | ||
==macOS== | ==macOS== | ||
==Windows== | ==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== | ==Android== | ||
[[Qt for Android known issues]] | [[Qt for Android known issues]] | ||
==iOS== | ==iOS== | ||
v6.3.1 - Building qmake projects will fail trying to link to hardcoded CI paths ([https://bugreports.qt.io/browse/QTBUG-104396 QTBUG-104396]) | |||
==WebAssembly== | ==WebAssembly== | ||
v6.3.1 - Building qmake projects will fail trying to link to hardcoded CI paths ([https://bugreports.qt.io/browse/QTBUG-104396 QTBUG-104396]) | |||
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. | 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. | ||
==Static Qt== | |||
v6.3.1 - Building qmake projects will fail trying to link to hardcoded CI paths ([https://bugreports.qt.io/browse/QTBUG-104396 QTBUG-104396]) | |||
==Qt for Device Creation== | ==Qt for Device Creation== | ||
{{Release Information}} | {{Release Information}} | ||
Latest revision as of 04:27, 9 September 2022
- Check that your system meets Qt's requirements
- All open issues can be found from Jira
- RTA findings here
All platforms
Qt Quick 3D
v6.3.1 - 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
v6.3.1 - Building qmake projects will fail trying to link to hardcoded CI paths (QTBUG-104396)
WebAssembly
v6.3.1 - Building qmake projects will fail trying to link to hardcoded CI paths (QTBUG-104396)
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.
Static Qt
v6.3.1 - Building qmake projects will fail trying to link to hardcoded CI paths (QTBUG-104396)