#13575 closed enhancement (fixed)
qt-everywhere-src-5.15.0 and qtwebengine
Reported by: | Bruce Dubbs | Owned by: | Douglas R. Reno |
---|---|---|---|
Priority: | high | Milestone: | 10.0 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New point version.
Change History (7)
comment:1 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 4 years ago
Priority: | normal → high |
---|---|
Summary: | qt-everywhere-src-5.15.0 → qt-everywhere-src-5.15.0 and qtwebengine |
comment:3 by , 4 years ago
The GCC patch isn't needed for Qt5.
On the other hand, qtwebengine needs the ICU patch (as Thomas mentioned in IRC). All but one of the GCC-10 fixes were implemented into the chromium build shipped with QtWebEngine-5.15.0. I've implented that one, the ICU fix, and another gcc-10 fix needed in "src/3rdparty/chromium/base/trace_event/trace_event_memory_overhead.h" (#include <string> *below* #include <unordered_map>). These will all be present in a new consolidated_fixes patch that I'll submit with the update
comment:4 by , 4 years ago
The patch for qtwebengine has been added to the patches repo at r4131.
The Qt developers have decided to develop their own PDF Reader implementation for Falkon, which is called QtPdf. It's built with QtWebEngine
A link to all of the changelogs can be found here: https://wiki.qt.io/Qt_5.15.0_Change_Files
Some things that stand out with regards to deprecations and behavior changes:
QtBase (https://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.15.0/?h=v5.15.0) Contains binary incompatible changes and many deprecations.
QtDeclarative (which handles QML) https://code.qt.io/cgit/qt/qtdeclarative.git/tree/dist/changes-5.15.0/?h=v5.15.0 has several deprecations and may cause problems.
QtMultimedia (https://code.qt.io/cgit/qt/qtmultimedia.git/tree/dist/changes-5.15.0/?h=v5.15.0) has some deprecations as well.
In QtQuickControls2 (https://code.qt.io/cgit/qt/qtquickcontrols2.git/tree/dist/changes-5.15.0/?h=v5.15.0):
QtWebEngine has the normal host of security fixes (https://code.qt.io/cgit/qt/qtwebengine.git/tree/dist/changes-5.15.0/?h=v5.15.0):
We'll need to test to see whether the GCC-10 patch is needed there or not (same with Qt itself).