Bug #2063
closedFails to build with Qt5
100%
Description
This line QT5_USE_MODULES (leechcraft-util-qml Declarative Network) contains Declarative. Declarative has been discontinues in Qt5.
Updated by yurivict about 6 years ago
Additionally, with USE_QT5=ON, it still looks for qmake-qt4:
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/local/bin/qmake-qt4 (found version "4.8.7")
CMake Error at plugins/summary/CMakeLists.txt:15 (find_package):
By not providing "FindLeechCraft.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"LeechCraft", but CMake did not find one.
Could not find a package configuration file provided by "LeechCraft" with
any of the following names:
LeechCraftConfig.cmake
leechcraft-config.cmake
Add the installation prefix of "LeechCraft" to CMAKE_PREFIX_PATH or set
"LeechCraft_DIR" to a directory containing one of the above files. If
"LeechCraft" provides a separate development package or SDK, be sure it has
been installed.
Updated by 0xd34df00d about 6 years ago
Which version is that?
HEAD only supports Qt5 for quite some time now. I believe the dependency on QtDeclarative has also been dropped, but I'll double-check.
Updated by yurivict about 6 years ago
0.6.70
I am trying to update the FreeBSD port. I can't use the head, it has to be in a tarball.
Updated by 0xd34df00d about 6 years ago
That's >4 years old now, IIRC it doesn't support Qt5 at all.
Would a weekly snapshot work? Say, https://dist.leechcraft.org/LeechCraft/0.6.75/leechcraft-0.6.70-12062-gcc93e7b776.tar.xz
Updated by 0xd34df00d about 6 years ago
BTW the FreeBSD port might be really outdated. In any event, the Gentoo ebuilds might help to figure out the correct dependencies and their versions: https://github.com/gentoo/gentoo/tree/master/app-leechcraft
Updated by yurivict about 6 years ago
It's not really outdated, it is at the latest release. The release hasn't been made in a while.
Anyway, I'm trying to update it.
Updated by yurivict about 6 years ago
It requires a specific version of Qt:
CMake Warning at /usr/local/share/cmake/Modules/CMakeFindDependencyMacro.cmake:48 (find_package): Could not find a configuration file for package "Qt5Network" that exactly matches requested version "5.11.1". The following configuration files were considered but not accepted: /usr/local/lib/cmake/Qt5Network/Qt5NetworkConfig.cmake, version: 5.11.2 Call Stack (most recent call first): /usr/local/lib/cmake/Qt5WebKitWidgets/Qt5WebKitWidgetsConfig.cmake:73 (find_dependency) /usr/local/lib/cmake/Qt5/Qt5Config.cmake:28 (find_package) CMakeLists.txt:141 (find_package) util/models/CMakeLists.txt:22 (FindQtLibs)
How do I make it to accept any version?
Updated by 0xd34df00d about 6 years ago
Try rebuilding qtwebkit. Looks like it was built with Qt 5.11.1, while Qt has later been upgraded to 5.11.2.
Updated by yurivict about 6 years ago
There is a quirk in FreeBSD ports: QtWebkit has some other version because of some issues. It normally works fine when used with Qt-5.11.2.
How to make leechcraft tolerant to the QtWebkit version? It is normally the REQUIRED keyword, but in this case I don't see it.
Updated by 0xd34df00d about 6 years ago
There is a quirk in FreeBSD ports: QtWebkit has some other version because of some issues.
That's just the same situation as in Gentoo (and some other distros) - looks like it's the new normal as QtWebkit has been long dropped by upstream Qt.
How to make leechcraft tolerant to the QtWebkit version?
Not sure how it works with other cmake projects, but in this particular case it's the qtwebkit itself that's complaining. Indeed, the cmake call stack ends up in /usr/local/lib/cmake/Qt5WebKitWidgets/Qt5WebKitWidgetsConfig.cmake:73
. I just double-checked mine, and indeed looks like it only depends on the major-minor pair, not on the major-minor-patch triple (in my particular case, that's just 5.11
). Can you paste your /usr/local/lib/cmake/Qt5WebKitWidgets/Qt5WebKitWidgetsConfig.cmake
and, perhaps, something like /usr/local/lib/cmake/Qt5WebKit/Qt5WebKitConfig.cmake
?
Updated by 0xd34df00d almost 6 years ago
Do you think anything else could be done here, or shall I close this ticket?
Updated by 0xd34df00d over 5 years ago
- Category set to Overall
- Status changed from New to Closed
- Assignee set to 0xd34df00d
- Target version set to 0.6.75
- % Done changed from 0 to 100
- Estimated time set to 0:00 h
I'm gonna be releasing 0.6.75 hopefully this month (writing the release notes and the changelog is the biggest blocker, lol), so closing.