forked from qt/qtbase
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin/5.15' into dev
Conflicts: examples/opengl/doc/src/cube.qdoc src/corelib/global/qlibraryinfo.cpp src/corelib/text/qbytearray_p.h src/corelib/text/qlocale_data_p.h src/corelib/time/qhijricalendar_data_p.h src/corelib/time/qjalalicalendar_data_p.h src/corelib/time/qromancalendar_data_p.h src/network/ssl/qsslcertificate.h src/widgets/doc/src/graphicsview.qdoc src/widgets/widgets/qcombobox.cpp src/widgets/widgets/qcombobox.h tests/auto/corelib/tools/qscopeguard/tst_qscopeguard.cpp tests/auto/widgets/widgets/qcombobox/tst_qcombobox.cpp tests/benchmarks/corelib/io/qdiriterator/qdiriterator.pro tests/manual/diaglib/debugproxystyle.cpp tests/manual/diaglib/qwidgetdump.cpp tests/manual/diaglib/qwindowdump.cpp tests/manual/diaglib/textdump.cpp util/locale_database/cldr2qlocalexml.py util/locale_database/qlocalexml.py util/locale_database/qlocalexml2cpp.py Resolution of util/locale_database/ are based on: https://codereview.qt-project.org/c/qt/qtbase/+/294250 and src/corelib/{text,time}/*_data_p.h were then regenerated by running those scripts. Updated CMakeLists.txt in each of tests/auto/corelib/serialization/qcborstreamreader/ tests/auto/corelib/serialization/qcborvalue/ tests/auto/gui/kernel/ and generated new ones in each of tests/auto/gui/kernel/qaddpostroutine/ tests/auto/gui/kernel/qhighdpiscaling/ tests/libfuzzer/corelib/text/qregularexpression/optimize/ tests/libfuzzer/gui/painting/qcolorspace/fromiccprofile/ tests/libfuzzer/gui/text/qtextdocument/sethtml/ tests/libfuzzer/gui/text/qtextdocument/setmarkdown/ tests/libfuzzer/gui/text/qtextlayout/beginlayout/ by running util/cmake/pro2cmake.py on their changed .pro files. Changed target name in tests/auto/gui/kernel/qaction/qaction.pro tests/auto/gui/kernel/qaction/qactiongroup.pro tests/auto/gui/kernel/qshortcut/qshortcut.pro to ensure unique target names for CMake Changed tst_QComboBox::currentIndex to not test the currentIndexChanged(QString), as that one does not exist in Qt 6 anymore. Change-Id: I9a85705484855ae1dc874a81f49d27a50b0dcff7
- Loading branch information
Showing
399 changed files
with
8,910 additions
and
4,463 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,117 @@ | ||
Qt 5.14.2 is a bug-fix release. It maintains both forward and backward | ||
compatibility (source and binary) with Qt 5.14.0 through 5.14.1. | ||
|
||
For more details, refer to the online documentation included in this | ||
distribution. The documentation is also available online: | ||
|
||
https://doc.qt.io/qt-5/index.html | ||
|
||
The Qt version 5.14 series is binary compatible with the 5.13.x series. | ||
Applications compiled for 5.13 will continue to run with 5.14. | ||
|
||
Some of the changes listed in this file include issue tracking numbers | ||
corresponding to tasks in the Qt Bug Tracker: | ||
|
||
https://bugreports.qt.io/ | ||
|
||
Each of these identifiers can be entered in the bug tracker to obtain more | ||
information about a particular change. | ||
|
||
**************************************************************************** | ||
* QtCore * | ||
**************************************************************************** | ||
|
||
- QCollator: | ||
* QTBUG-81673: Fixed a regression introduced in 5.14.0 that caused | ||
QCollator not to operate with default-constructed QStrings and print a | ||
warning on Windows. | ||
|
||
- QString, codecs: | ||
* QTBUG-62011: ZWNBS is no longer discarded (mistaken for a BOM despite | ||
not being at the start) when converting UCS4 to QString's UCS2. | ||
|
||
- QLocale: | ||
* QTBUG-80459: Skip digit-grouping if the system locale is configured to | ||
use an empty group separator. | ||
* QTBUG-81530: Use "+" if MS reports empty for the system locale's plus | ||
sign, as documented in MS's API for the relevant query. | ||
|
||
- QLockFile: | ||
* Suppressed the warning on QNX that said 'setNativeLocks failed: | ||
"Function not implemented"'. There is no difference in behavior: Qt | ||
will continue not to be able to apply an OS- level file lock, which | ||
means the lock could be accidentally stolen by buggy software. Correct | ||
software using QLockFile should not be affected. | ||
|
||
- QObject: | ||
* For the purposes of QT_NO_NARROWING_CONVERSIONS_IN_CONNECT, pointer | ||
(incl. pointer-to-member) to bool conversions are now considered | ||
narrowing. This matches the resolution of a defect report in C++ | ||
itself. | ||
|
||
- QStorageInfo: | ||
* Improved discovery of device nodes on Linux if the /dev entry was | ||
renamed after the filesystem was mounted and udev is in use. | ||
|
||
**************************************************************************** | ||
* QtGui * | ||
**************************************************************************** | ||
|
||
- QTextMarkdownImporter: | ||
* Text in Markdown format is assumed to be UTF-8. | ||
* The "title" in a Markdown hyperlink is now used as the tooltip, | ||
not the anchor name. | ||
* Fixed vulnerability oss-fuzz-20450 (invalid input resulted in an | ||
attempt to insert items into a list that no longer exists). | ||
|
||
**************************************************************************** | ||
* QtWidgets * | ||
**************************************************************************** | ||
|
||
- QLineEdit: | ||
* the inputMask property has allowed any Letter or Number category | ||
character for the respective mask characters, not just ASCII. The | ||
documentation has been updated accordingly. | ||
|
||
**************************************************************************** | ||
* qmake * | ||
**************************************************************************** | ||
|
||
- To remove the NDEBUG define that is added by default in MSVC mkspecs, | ||
write DEFINES_RELEASE -= NDEBUG in your .pro file. | ||
- Install/uninstall rules are now generated for target.targets on Windows. | ||
This mirrors the behavior on Unix. | ||
|
||
**************************************************************************** | ||
* Third-Party Code * | ||
**************************************************************************** | ||
|
||
- md4c was updated to 0.4.3. This fixes vulnerability oss-fuzz-20580. | ||
|
||
- QtSQL, sqlite: | ||
* Updated to v3.31.1 | ||
* [QTBUG-82533] Fixed CVE-2020-9327 | ||
|
||
**************************************************************************** | ||
* CMake * | ||
**************************************************************************** | ||
|
||
- Windows: | ||
* Fixed linking with Qt static build | ||
|
||
**************************************************************************** | ||
* MSVC * | ||
**************************************************************************** | ||
|
||
- Fixed a compatibility issue found when linking code compiled with | ||
version 16.6 to a Qt compiled with 16.5. | ||
|
||
**************************************************************************** | ||
* MinGW * | ||
**************************************************************************** | ||
|
||
- Fixed build regressions. | ||
- The -debug-and-release configuration has been fixed. In this | ||
configuration, Qt libraries again have a 'd' suffix. | ||
- In the -debug configuration, libraries do not have a 'd' suffix, similar | ||
to Unix platforms. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.