If I configure Qt 5.10 for a build on Windows

SGaist

Hi,

Not tried but you should add the -voption to see what is happening with QtWebEngine.

By the way, what compiler are you using ?

VRHans

@SGaist vs 2015 update 3 (QtWebEngine specifies it requires this at a minimum.)

It looks like I'm building QtWebEngine now (previously it looked like dependencies but I believe it was actually just rebuilding part of the regular Qt Framework.) Chromium is building this time.

VRHans

It appears that you must, and I'm guessing here, build Qt without a shadow build BEFORE you attempt to build QtWebEngine.

The build just broke stating:

Reading C:/QTBUILD/qt-everywhere-src-5.10.0/qtwebengine/src/core/core.pro
Reading C:/QTBUILD/qt-everywhere-src-5.10.0/qtwebengine/src/core/core_headers.pro
Reading C:/QTBUILD/qt-everywhere-src-5.10.0/qtwebengine/src/core/core_generator.pro
Project ERROR: Unknown module(s) in QT: qml quick webchannel

I'm going to go ahead, pollute my source directory with the qt build, and try again...

VRHans

Well, interestingly enough - when not using a shadow build directory, configure reports on QtWebEngine:

Qt WebEngine:
Embedded build ......................... no
Pepper Plugins ......................... yes
Printing and PDF ....................... yes
Proprietary Codecs ..................... no
Spellchecker ........................... yes
Native Spellchecker .................... no
WebRTC ................................. yes
Use System Ninja ....................... no
Geolocation ............................ yes

Note: No wayland-egl support detected. Cross-toolkit compatibility disabled.

Qt is now configured for building. Just run 'nmake'.
Once everything is built, you must run 'nmake install'.
Qt will be installed into 'c:\QTBUILD\results'.

Prior to reconfiguration, make sure you remove any leftovers from
the previous build.

SGaist

That's surprising. Did you re-call configure in the same folder without cleanup ? That's a thing to avoid, you might have leftovers from prior trial that might wreak havoc.

VRHans

I did not, I've only previously called configure from my shadow build directory.
BTW, I've tried the various 'clean' methods people mention but none actually clean the configuration - I either have to delete the shadow build directory or - if I'm not building in a shadow directory - blow away and recopy the source directory.

Since it appears you cannot build QtWebEngine with Qt from a shadow directory, I'm not building in the source directory itself.

SGaist

I wonder it is something like QTBUG-44002.

VRHans

I suspect it's due to the complexity of manipulating chromium and its dependencies outside of the the source directory due to either rapidity of change or it being 'build system tech debt' - but I'm just speculating.

It wouldn't be the end of the world except I can't seem to find out the particular steps to build QtWebEngine... Each failure is likely to require me to replace the source and therefore rebuild all of Qt along the way. This takes a long time (as you would know) before you even get to try building QtWebEngine...

SGaist

You could also just build the QtWebEngine module using:

cd qtwebengine
/path/to/qmake -r
nmake
nmake install

You should also consider replacing nmake by jom. It should paralelize the build better.

VRHans

If it doesn't build by default this time, that's what I'm going to do. Thx

VRHans

I believe it succeeded. I'll validate, and then I think I'm going to update the wiki :).