Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.12.0 Beta 1
-
None
-
Linux 16.04, Yocto: meta-boot2qt (sumo), meta-qt5 (5.12) + https://codereview.qt-project.org/#/c/241746/
-
-
8b811ee0797f0378a0ef49a5ca04302959e08c65 (qt/qtwebengine/5.12)
Description
QtWebEngine builds got flaky recently in yocto when updating Qt modules from early 5.12 snapshot to proposed beta1 content fail build often with missing mojom header:
| In file included from ../../../../git/src/3rdparty/chromium/chrome/browser/profiles/profile.h:11:0, | from ../../../../git/src/3rdparty/chromium/chrome/browser/custom_handlers/protocol_handler_registry.h:17, | from ../../../../git/src/3rdparty/chromium/chrome/browser/custom_handlers/protocol_handler_registry.cc:5: | ../../../../git/src/3rdparty/chromium/content/public/browser/browser_context.h:24:10: fatal error: third_party/blink/public/mojom/blob/blob.mojom.h: No such file or directory | #include "third_party/blink/public/mojom/blob/blob.mojom.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | compilation terminated.
There seems to be dependency problem or race condition as the mojom headers sometimes get built and building goes through fine. This exact issue was already present in earlier meta-qt5 update attempt where updating webengine to a revision matched by Qt 5.12.0 snapshot build. Updating webengine further to then-latest revision in 5.12 branch solved the build issue momentarily and a Qt 5.12 snapshot update was succesful in meta-qt5 ( https://codereview.qt-project.org/#/c/241374/7 ). Now, trying to build the latest 5.12.0 beta1 content fails seemingly every time.