Skip to content

Conversation

@a17r
Copy link
Contributor

@a17r a17r commented Oct 23, 2025

Depends on #58

Make WebEngine the default impl

In Qt6, there is no WebKit, which means setting APP_QT_VERSION=6 so far
lead to a default CMake Error unless -DUSE_WEBENGINE was specifically set.
If not cleaned up, it should be the default=off minority config.

Rename USE_WEBENGINE -> USE_WEBKIT
Properly invert logic where used
Update docs

Simplify and make explicit Qt5 vs. Qt6 choice

Guard USE_KF5 and USE_WEBKIT options behind USE_QT5.
Cleanup superfluous APP_QT_VERSION cmake variable
Drop automagic find_package(QT NAMES) mechanism
qt-aliases.cmake: Drop QT_VERSION_MAJOR, simply bail out with >=Qt-5.15

Please note that I can not test this with Qt5 (WebEngine|Webkit) myself any longer. I did however check that the qt-aliases.cmake bailout logic works.

a17r added 4 commits October 23, 2025 21:35
CMake 3.31 warns about compat. for <3.10 being removed in the future. Qt6
CMake modules already require 3.16 though, so it is a good base line.

CMake 3.16 was released in 2019.

Signed-off-by: Andreas Sturmlechner <[email protected]>
Signed-off-by: Andreas Sturmlechner <[email protected]>
In Qt6, there is no WebKit, which means setting APP_QT_VERSION=6 so far
lead to a default CMake Error unless -DUSE_WEBENGINE was specifically set.
If not cleaned up, it should be the default=off minority config.

Rename USE_WEBENGINE -> USE_WEBKIT
Properly invert logic where used
Update docs

Signed-off-by: Andreas Sturmlechner <[email protected]>
@a17r a17r force-pushed the cmake-qt-improv branch 5 times, most recently from 99f7f6b to ba4182b Compare October 23, 2025 20:42
Guard USE_KF5 and USE_WEBKIT options behind USE_QT5.
Cleanup superfluous APP_QT_VERSION cmake variable
Drop automagic find_package(QT NAMES) mechanism
qt-aliases.cmake: Drop QT_VERSION_MAJOR, simply bail out with >=Qt-5.15

Signed-off-by: Andreas Sturmlechner <[email protected]>
@u-235
Copy link
Member

u-235 commented Oct 24, 2025

I'm leaning toward removing KDE support. While in KDE4 the application used many specific widgets, in KDE5 it only uses the about dialog and file dialog. In the next major version, I plan to integrate the browser engine via separate plugins, which will allow the use of different engines without rebuilding the application.

This way, the inconveniences you mentioned will disappear by themselves.

@u-235 u-235 closed this Oct 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants