Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Qt 6.3 Known Issues: Difference between revisions
Jump to navigation
Jump to search
(→Windows: Add known issue regarding the use of backslashes in CMAKE_PREFIX_PATH) |
No edit summary |
||
| Line 1: | Line 1: | ||
*Check that your system meets [https://doc | *Check that your system meets [https://doc.qt.io/qt-6/gettingstarted.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] | ||
Revision as of 06:14, 12 April 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
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.