Qt 6.0.0 Known Issues: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 7: | Line 7: | ||
==All platforms== | ==All platforms== | ||
*When using socks proxy it may read and send data from deallocated memory when sending large amounts of data at once. | *When using socks proxy it may read and send data from deallocated memory when sending large amounts of data at once. | ||
*[https://bugreports.qt.io/browse/QTBUG-89176 QTBUG-89176] | *QCache related crash on DNS lookups ([https://bugreports.qt.io/browse/QTBUG-89176 QTBUG-89176]) | ||
*Any Qt Quick Controls 2 applications that still set the Default style will not start | *Any Qt Quick Controls 2 applications that still set the Default style will not start. The fix will be available with 6.0.1. The workaround is to set a [https://doc.qt.io/qt-6/qtquickcontrols2-styles.html#available-styles valid] style. ([https://bugreports.qt.io/browse/QTBUG-89286 QTBUG-89286]) | ||
* There are known issues with CMake 4.18.2 and multi-config ninja that prevend building Qt with a -debug-and-release build. Please consider updating CMake in such cases. | |||
==Linux== | ==Linux== | ||
| Line 22: | Line 22: | ||
==Windows== | ==Windows== | ||
* | * Static builds with MSVC are not currently possible due to some filenames causing MAX_PATH to be exceeded ([https://bugreports.qt.io/browse/QTBUG-88581 QTBUG-88581]). | ||
==Android== | ==Android== | ||
Latest revision as of 09:34, 8 January 2021
- Check that your system meets Qt's requirements
- All open issues can be found from Jira: https://bugreports.qt.io
- RTA findings here
- Supported development platforms are listed here: https://bugreports.qt.io/browse/QTBUG-85851
All platforms
- When using socks proxy it may read and send data from deallocated memory when sending large amounts of data at once.
- QCache related crash on DNS lookups (QTBUG-89176)
- Any Qt Quick Controls 2 applications that still set the Default style will not start. The fix will be available with 6.0.1. The workaround is to set a valid style. (QTBUG-89286)
- There are known issues with CMake 4.18.2 and multi-config ninja that prevend building Qt with a -debug-and-release build. Please consider updating CMake in such cases.
Linux
- Minimum glibc version for prebuild binaries is 2.28, see https://bugreports.qt.io/browse/QTBUG-88833
- Workaround: compile Qt 6.0.0 by yourself or update glibc to 2.28 or newer
macOS
Windows
- Static builds with MSVC are not currently possible due to some filenames causing MAX_PATH to be exceeded (QTBUG-88581).
Android
- Qt 6.0 for Android doesn't support multi-abi builds, it will be added in the next release (QTBUG-88841).
- When using CMake properties like QT_ANDROID_PACKAGE_SOURCE_DIR, qt_android_generate_deployment_settings(target_name) must be added after setting properties to make sure they are included in the deployment JSON file (QTBUG-88840).
iOS
- Using CMake to build user projects requires manual tweak. Please use qmake for now.
- Qt Creator cannot yet build iOS CMake projects (QTCREATORBUG-25058).
- Starting deployed iOS application from Qt Creator fails, see https://bugreports.qt.io/browse/QTBUG-89058
- If you click the installed icon on the device (located on the last screen) it starts Ok.
Qt for Device Creation
- Qt Creator's wizard generated CMake applications need a workaround to be able to deploy to device. See: https://bugreports.qt.io/browse/QTCREATORBUG-25029