Qt 5.9.1 Known Issues: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:Known Issues == All platforms == * Check that your system meets [http://doc-snapshots.qt.io/qt5-5.9/gettingstarted.html#platform-requirements Qt's requirements]...") |
(→Qt for Device Creation: known issues update for 5.9.1) |
||
Line 27: | Line 27: | ||
== Qt for Device Creation == | == Qt for Device Creation == | ||
* | * Apalis iMX6: If you boot the device with USB cable plugged in, the debug connection to the device fails. Workaround is to disconnect and reconnect the USB cable after the device is booted up, see https://bugreports.qt.io/browse/QTBUG-61718 | ||
{{Release Information}} | {{Release Information}} |
Revision as of 08:10, 30 June 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=18750
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.
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.
macOS
Android
iOS
UWP
- 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
- Should be fixed in QtCreator 4.3.1
QNX
- C++ debugging fails on QNX, see https://bugreports.qt.io/browse/QTCREATORBUG-17901
Qt for Device Creation
- Apalis iMX6: If you boot the device with USB cable plugged in, the debug connection to the device fails. Workaround is to disconnect and reconnect the USB cable after the device is booted up, see https://bugreports.qt.io/browse/QTBUG-61718