QtWebKit is unmaintained
Details
- Reviewers
mwolff kfunk - Group Reviewers
KDevelop - Commits
- R33:2486228ccee2: Port away from QtWebKit to QtWebEngine
R32:2486228ccee2: Port away from QtWebKit to QtWebEngine
manual testing
Diff Detail
- Repository
- R33 KDevPlatform
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Hi, Aleix. This patch seems to be incorrect - on my kubuntu 16.04 with kde-backports (qt 5.6.1) it's unable to find Qt5WebEngineWidgetsConfig.cmake
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1579265
QtWebKit is actually more alive nowadays than in a long time, so I still think the best way forward would be to wrap it in a thin KF5-material wrapper and use that here
@mwolff I think it's fine like this, I wouldn't want people compiling against qtwebkit because they forgot to pull a dependency, it should be a conscious decision.
documentation/CMakeLists.txt | ||
---|---|---|
31 | PREFER_WEBKIT -> USE_WEBKIT. This is not about preference. There's actually no other choice :) |
I agree with Milian here. There's still several systems where QtWebKit is the default. Let's not make it more difficult to build KDevelop on these. We don't care about whether we use WebKit or WebEngine. It's up to the packagers.
You could add a note to the package properties text of WebKit telling that WebEngine is preferred, though.
We'll probably need to tweak the CMake code a bit more.
IIUC, right now if neither WK nor WE are installed, CMake will just tell you to get WK. It should give you both options.
documentation/CMakeLists.txt | ||
---|---|---|
5 | FYI: That basically renders TYPE REQUIRED redundant. As Qt5WebEngineWidgets is already found here. |