-
-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow compilation by disabling cmake flag WITH_QTWEBENGINE #2006
Conversation
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files |
Hello @gzotti! Thank you for this enhancement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update BUILDING.md also
This PR fixed issue #1982 partially, because the latest one contains 2 problems: no module on Apple Silicon chips and regress in Qt 5.15.x. |
Do you know how to unset the flag if cmake cannot find the QtWebEngine module? This setting should emit a well-visible warning as well, so that it can be installed if available and the user just had forgotten. What kind of regress has happened in 5.15? Mac only or all platforms? (I have not tried building this on 5.15 yet.) |
First problem: standard cmake cannot check the architecture of target platform (see solution here), the second problem - on some platforms (e.g. linux) you may just not installed it in system, but it exists as package in repository or it just not installed from standard Qt installer. Of course you may change the logic of your cmake script to enable/disable flag WITH_QTWEBENGINE (see FIND_PACKAGE docs + you may add MESSAGE(STATUS ...) to inform the user).
Right now I've tested it on linux and mac and I can reproduce the issue on mac only. It may be related to deprecation brige Qt-OpenGL on the Mac or changes the requirement of OpenGL version (3.2 + enable core profile). |
Important note: the regress on Mac may be not related to the QtWebEngine module! |
Ad (1) The logic may be:
This warning should not rush by but be visible as one of the last messages. Ad (2) please try to compile this on a Mac with 5.15 to see if QtWebEngine changed to the worse. Else, this OpenGL deprecation may hit us. It will do so sooner or later, at least on this platform. |
Building with option WITH_QTWEBENGINE=Off has no issues on Mac with Qt 5.15.2. Maybe this is related to OpenGL context (I didn't check details for implementation of independence the window of OnlineQuery plugin)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Hello @gzotti! Please check the fresh version (development snapshot) of Stellarium: |
Just for note: same problem (missing build dependencies) for architectures s390x and ppc64el |
Yes, I have also received the flood from canonical. The complete solution for CI would be to let cmake detect the presence of qtwebengine-dev, and if not found react with disabling the feature, plus emitting a warning (in case the human compiling on a "good" platform has forgot to install the available package). To be realistic: How many instance of Stellarium are running on s390x and ppc64el? |
Hello @gzotti! Please check the latest stable version of Stellarium: |
Description
On some platforms (ARM based) the QtWebEngine seems to be missing. The CMAKE flag WITH_QTWEBENGINE can now be set to false on those to disable the webbrowser view internal to the OnlineQueries plugin. The websites will instead be queried inside the system's default web browser.
Currently this flag has to be manually set. It may be possible to set the flag as consequence of cmake being unable to find the QtWebEngine modules, and emit a warning to the developer during compilation.
If there is some style guide for cmake, I surely did something wrong! Advice?
Fixes #2004, #1982
Screenshots (if appropriate):
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: