Qt 5.9.0 Known Issues: Difference between revisions
Jump to navigation
Jump to search
(Add info about MSVC 2017 -static not working) |
Ulf Hermann (talk | contribs) (note about broken QML memory profiler) |
||
(9 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:Known Issues]] | |||
== All platforms == | == All platforms == | ||
Line 7: | Line 7: | ||
* CMake: Qt modules do not define <code>Qt5XXX_VERSION_STRING</code> correctly. Workaround is to use <code>Qt5XXX_VERSION</code> instead: https://bugreports.qt.io/browse/QTBUG-60936 | * CMake: Qt modules do not define <code>Qt5XXX_VERSION_STRING</code> correctly. Workaround is to use <code>Qt5XXX_VERSION</code> instead: https://bugreports.qt.io/browse/QTBUG-60936 | ||
* https://bugreports.qt.io/browse/QTBUG-61017 :Configuring Qt from sources gets stuck if trying<code> ./configure + press 'c'</code> Workaround is to use <code>-confirm-license</code> | * https://bugreports.qt.io/browse/QTBUG-61017 :Configuring Qt from sources gets stuck if trying<code> ./configure + press 'c'</code> Workaround is to use <code>-confirm-license</code> | ||
* The QML profiler will not record memory allocations. See https://bugreports.qt.io/browse/QTBUG-64674 | |||
== Windows == | == Windows == | ||
* Static builds of Qt with Microsoft Visual Studio 2017 (through Update 2) do not work and will likely crash at runtime. This is believed to be a compiler bug and therefore an update from Microsoft is required. See https://bugreports.qt.io/browse/QTBUG-59721. | * Static builds of Qt with Microsoft Visual Studio 2017 (through Update 2) do not work and will likely crash at runtime. This is believed to be a compiler bug and therefore an update from Microsoft is required. See https://bugreports.qt.io/browse/QTBUG-59721. | ||
* windeployqt cannot deploy ANGLE when using -combined-angle-lib https://bugreports.qt.io/browse/QTBUG-60962 | * windeployqt cannot deploy ANGLE when using -combined-angle-lib https://bugreports.qt.io/browse/QTBUG-60962 | ||
* Ctrl C/V shortcuts do not work in Qt Quick applications https://bugreports.qt.io/browse/QTBUG-61086 | |||
== Linux == | == Linux == | ||
Building Qt modules fails with binaries delivered with online installer [https://bugreports.qt.io/browse/QTBUG-53865 see bug QTBUG-53865]. Workaround is to build whole Qt from source or have libicu 56 installed on the system. | |||
Qt Speech: pre-built packages do not contain the speech-dispatcher backend ([https://bugreports.qt.io/browse/QTBUG-58461 QTBUG-58461]). | |||
== macOS == | == macOS == | ||
== Android == | == Android == | ||
[[Qt_for_Android_known_issues|Qt for Android known issues]] | [[Qt_for_Android_known_issues|Qt for Android known issues]] | ||
Line 20: | Line 25: | ||
== iOS == | == iOS == | ||
* QNetworkAccessManager fails to trust CA certs, breaking https, on iOS: https://bugreports.qt.io/browse/QTBUG-61053 | |||
== UWP == | == UWP == | ||
* QtNetworkAuth/TwitterTimeline build fails for UWP: https://bugreports.qt.io/browse/QTBUG-59963 | * QtNetworkAuth/TwitterTimeline build fails for UWP: https://bugreports.qt.io/browse/QTBUG-59963 | ||
* Qt Creator uses the wrong mkspec for UWP projects using Visual Studio 2017. If you encounter errors like 'qt.winrtrunner: "<BUILDDIR>/AppxManifest.xml" does not exist.' please set the Kit's '''Qt mkspec''' to '''winrt-x86-msvc2017''', '''winrt-x64-msvc2017''' or '''winrt-arm-msvc2017''' depending on target architecture. Afterwards rerun qmake, rebuild and run your application. [https://bugreports.qt.io/browse/QTCREATORBUG-18288 https://bugreports.qt.io/browse/QTCREATORBUR-18288] | |||
== QNX == | == QNX == |
Latest revision as of 10:04, 22 November 2017
All platforms
- Check that your system meets Qt's requirements
- All open issues can be found from Jira: https://bugreports.qt.io
- RTA findings here: https://bugreports.qt.io/issues/?filter=18372
- CMake: Qt modules do not define correctly. Workaround is to use
Qt5XXX_VERSION_STRING
instead: https://bugreports.qt.io/browse/QTBUG-60936Qt5XXX_VERSION
- https://bugreports.qt.io/browse/QTBUG-61017 :Configuring Qt from sources gets stuck if tryingWorkaround is to use
./configure + press 'c'
-confirm-license
- The QML profiler will not record memory allocations. See https://bugreports.qt.io/browse/QTBUG-64674
Windows
- Static builds of Qt with Microsoft Visual Studio 2017 (through Update 2) do not work and will likely crash at runtime. This is believed to be a compiler bug and therefore an update from Microsoft is required. See https://bugreports.qt.io/browse/QTBUG-59721.
- windeployqt cannot deploy ANGLE when using -combined-angle-lib https://bugreports.qt.io/browse/QTBUG-60962
- Ctrl C/V shortcuts do not work in Qt Quick applications https://bugreports.qt.io/browse/QTBUG-61086
Linux
Building Qt modules fails with binaries delivered with online installer see bug QTBUG-53865. Workaround is to build whole Qt from source or have libicu 56 installed on the system.
Qt Speech: pre-built packages do not contain the speech-dispatcher backend (QTBUG-58461).
macOS
Android
iOS
- QNetworkAccessManager fails to trust CA certs, breaking https, on iOS: https://bugreports.qt.io/browse/QTBUG-61053
UWP
- QtNetworkAuth/TwitterTimeline build fails for UWP: https://bugreports.qt.io/browse/QTBUG-59963
- Qt Creator uses the wrong mkspec for UWP projects using Visual Studio 2017. If you encounter errors like 'qt.winrtrunner: "<BUILDDIR>/AppxManifest.xml" does not exist.' please set the Kit's Qt mkspec to winrt-x86-msvc2017, winrt-x64-msvc2017 or winrt-arm-msvc2017 depending on target architecture. Afterwards rerun qmake, rebuild and run your application. https://bugreports.qt.io/browse/QTCREATORBUR-18288
QNX
- C++ debugging fails on QNX, see QTCREATORBUG-17901
Qt for Device Creation
- Device Creation requires QtCreator 4.3 to work due new QDB plugin.
- Virtual keyboard does not work in the sample Qt Quick application, see QTCREATORBUG-18247