Qt 5.15.4 WebEngine not building on Linux
-
I downloaded Qt 5.15.4 today and attempted to create a Linux build on the same machine on which I had successfully built Qt 5.15.2, including WebEngine.
Following the same steps (specifying only --prefix and --commercial to configure), configure is telling me that the webengine* modules are not going to be built, but it is not clear why. The QT WebEngine Build Tools section of the config.summary is the same as the 5.15.2 build, but there are no Qt WebEngineCore, WebEngineQml or WebEngineWidgets sections in the 5.15.4 config.summary as there were in the 5.15.2 one.
I have compared the config.log output for the two packages and it looks very similar. If I edited the version numbers to be identical, a diff showed only 26 difference sections, which were all insignificant as far as I could tell - things like slightly different ordering of some of the config tests.
Has anything changed? Do I need to explicitly request a WebEngine build now? Or might some dependencies have changed?
Otherwise, how can I debug this?
-
Well it looks like I did miss some differences between the config logs and this warning that was staring me in the face in the config.summary:
"WARNING: Nodejs is required to build QtWebEngine."
This started appearing at 5.15.3 so I guess it is a new dependency.
-
I downloaded Qt 5.15.4 today and attempted to create a Linux build on the same machine on which I had successfully built Qt 5.15.2, including WebEngine.
Following the same steps (specifying only --prefix and --commercial to configure), configure is telling me that the webengine* modules are not going to be built, but it is not clear why. The QT WebEngine Build Tools section of the config.summary is the same as the 5.15.2 build, but there are no Qt WebEngineCore, WebEngineQml or WebEngineWidgets sections in the 5.15.4 config.summary as there were in the 5.15.2 one.
I have compared the config.log output for the two packages and it looks very similar. If I edited the version numbers to be identical, a diff showed only 26 difference sections, which were all insignificant as far as I could tell - things like slightly different ordering of some of the config tests.
Has anything changed? Do I need to explicitly request a WebEngine build now? Or might some dependencies have changed?
Otherwise, how can I debug this?
@Bob64
did you already try to pass-vto configure?
it shows some more output what might fail -
@raven-worx Thank you for the suggestion. I was not using the -v option but have just tried it. The main difference seems to be that more information is output to the console, but it seems similar to the output already written to the config.log file. The main additional output that I see is that more details of the qmake build are output.
As a further data point, I returned to the 5.15.2 package and did a fresh trial configure for that. This shows that the WebEngine packages are configured. This seems to rule out one thought I had, which was that the machine configuration had changed since I last tried to build on it.
-
Well it looks like I did miss some differences between the config logs and this warning that was staring me in the face in the config.summary:
"WARNING: Nodejs is required to build QtWebEngine."
This started appearing at 5.15.3 so I guess it is a new dependency.
-
Well it looks like I did miss some differences between the config logs and this warning that was staring me in the face in the config.summary:
"WARNING: Nodejs is required to build QtWebEngine."
This started appearing at 5.15.3 so I guess it is a new dependency.
-
@Bob64 I am seeing the issue while building Qt5.15.3 (opensource) for arm target. How did you resolve this issue?
In my case, when I add node (v18.17.1) for arm, then cross compile of node has lot more issues.
