> On Jun 24, 2017, at 6:59 AM, Lubomir I. Ivanov <neolit...@gmail.com> wrote: > > i've just updated my Qt to 5.9.0 on Windows with the Mingw 5.3.0 toolchain. > > but i'm facing a bug where the WebEngine libaries and cmake files are missing: > https://bugreports.qt.io/browse/QTBUG-61394 > > after reading more into it, it seems it might not be an actual bug...: > https://bugreports.qt.io/browse/QTBUG-42725 > > people in the above thread say that QWebEngine relies on the Chromium > engine as a backend and Chromium cannot be build using Mingw on > Windows - MSVC or clang needs to be used, so to me this means that if > you want to deploy a Qt based app on Windows that uses QWebEngine it > has to be built using MSVC or clang.
Hmm, that's odd. Have you looked at what MXE does about that? Because that's what I use to cross build everything. I haven't upgraded that to Qt 5.9, though (and I always need to compile that from source anyway) > if so, that's a bummer. I would agree. Changing my build environment to clang would not make me happy. > the thread is old, but there are recent comments bellow that suggest > to use a fork of QtWebKit, which is what we are using now - is that > correct? We use the "current" (but unmaintained) QtWebKit that is part of the sources. Once 5.9.1 is out (which should happen within a week) I will build that from source on MXE. > i will investigate further into this, but i'm going to assume that > switching to clang is a possibility (if QtWebEngine supports that - i > don't exactly understand the details here), while MSVC is out of the > question? MSVC is out of the question. clang is possible, but not something I look forward to - unless MXE has a clang branch which I haven't seen (and yes, I did look). /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
