Qt 5.13.1 Known Issues: Difference between revisions
(Created page with "Category:Known Issues *Check that your system meets [http://doc-snapshots.qt.io/qt5-5.9/gettingstarted.html#platform-requirements Qt's requirements] *All open issues can b...") |
(→QNX) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 15: | Line 15: | ||
==Windows== | ==Windows== | ||
* WebEngine 32 bit debug builds show crashes on some web pages. 32 bit release or 64 bit builds are not affected. | * WebEngine 32 bit debug builds show crashes on some web pages. 32 bit release or 64 bit builds are not affected. | ||
* In the binary Windows packages, building with CMake and Qt5::ActiveQt is broken. See [https://bugreports.qt.io/browse/QTBUG-78119 QTBUG-78119]. | |||
==Linux== | ==Linux== | ||
| Line 30: | Line 31: | ||
==QNX== | ==QNX== | ||
* QtCreator 4.9.x, Windows: Creator unable to deploy QNX project, see [https://bugreports.qt.io/browse/QTCREATORBUG-22592 QTCREATORBUG-22592] | |||
* QtCreator 4.9.x, Windows: Unable to deploy public key to qnx device with Creator, see [https://bugreports.qt.io/browse/QTCREATORBUG-22591 QTCREATORBUG-22591] | |||
==Qt for Device Creation== | ==Qt for Device Creation== | ||
CMake projects do not deploy anything to a Boot2Qt device, see [https://bugreports.qt.io/browse/QTCREATORBUG-22822 QTCREATORBUG-22822]. | |||
==Qt for Automation 5.13 == | ==Qt for Automation 5.13 == | ||
{{Release Information}} | {{Release Information}} | ||
Latest revision as of 09:54, 17 September 2019
- Check that your system meets Qt's requirements
- All open issues can be found from Jira: https://bugreports.qt.io
- RTA findings here
OpenSSL
Qt 5.13 requires OpenSSL 1.1.1 version on Linux and Windows. Qt online installer provides as convenience both OpenSSL source code and pre-built binaries of the OpenSSL libraries used by Qt Network. However, the installer doesn't set up OpenSSL environment. User needs to define the library path and possible environment variables. OpenSSL libraries are not automatically deployed with applications that are built with Qt. If provided OpenSSL binaries are not suitable for your use case source code installation includes instructions on how to configure and build your own OpenSSL libraries.
Import and export restrictions apply for some types of software, and for some parts of the world. Developers wishing to use SSL communication in their deployed applications should either ensure that their users have the appropriate libraries installed, or they should consult a suitably qualified legal professional to ensure that applications using the code from the OpenSSL project are correctly certified for import and export in relevant regions of the world.
See more instructions from QTCREATORBUG-22587
All platforms
Windows
- WebEngine 32 bit debug builds show crashes on some web pages. 32 bit release or 64 bit builds are not affected.
- In the binary Windows packages, building with CMake and Qt5::ActiveQt is broken. See QTBUG-78119.
Linux
- PDF viewing in Qt WebEngine using the Chromium extensions is disabled in the official packages, but works in self-compiled version as long as they are using clang or GCC 6 or higher. For details, see QTBUG-76329.
macOS
Android
iOS
UWP
QTBUG-75620: WinRT: Fix crash in native socket engine during close
QNX
- QtCreator 4.9.x, Windows: Creator unable to deploy QNX project, see QTCREATORBUG-22592
- QtCreator 4.9.x, Windows: Unable to deploy public key to qnx device with Creator, see QTCREATORBUG-22591
Qt for Device Creation
CMake projects do not deploy anything to a Boot2Qt device, see QTCREATORBUG-22822.