[Interest] QWE hacking: "backporting" src/3rdparty/chromium?

[Kai Koehne]

> -----Original Message-----
> From: Interest <interest-bounces+kai.koehne=qt.io at qt-project.org> On Behalf
> Of René J.V. Bertin
> Sent: Wednesday, November 7, 2018 3:10 PM
> To: interest at qt-project.org
> Subject: [Interest] QWE hacking: "backporting" src/3rdparty/chromium?
> 
> Hi,
> 
> Out of curiosity, how feasible would it be to deploy a more up-to-date
> QtWebEngine on a system that's stuck on an older Qt version. I understood
> from a previous exchange that QWE is much more a "thin wrapper" around the
> actual web engine than QtWebKit is, with the intention of making it easier to
> upgrade that component. If so, it might be possible to replace the
> src/3rdparty/chromium directory from, say, 5.8.0 with the one from 5.9.7 and
> get things to build with only minimal patching.
> 
> Thoughts?

That won't fly, because Chromium API is unstable and changes very often.

What we're trying to support though is building a newer qtwebengine.git against older Qt versions (usually last LTS).

For your example with Qt 5.8 I'm not sure, because there were some configuration system changes that probably require some fixes.

But you can build qtwebengine 5.11 branch against Qt 5.9.

Kai