I'm not a pyqt guru; but that looks like you have a remnant of qt5 lying
around. To fix when that happens, I do like dpkg --purge --force-all
{your old package}; then something like an apt --fix-broken {path to
your deb file}
Something you can try while you are waiting for an answer from a
pyqt+package guru here...
On 12/2/24 02:02 AM, Antonio Russo wrote:
On 12/1/24 23:16, Andrey Rakhmatullin wrote:
You only need deps installed if you need to run clean. Nowadays, with
git
and clean working copies you normally can skip running clean, by passing
--no-clean-source to sbuild or with something equivalent.
Andrey: thank you. In retrospect, I suppose this is obvious.
My second question is more specific to my package. I'm getting this
error:
-- No Qt5 qmake executable found. Can't check QT_INSTALL_PREFIX
-- Configuring incomplete, errors occurred!
cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
CMake Error at /usr/share/ECM/modules/ECMQueryQt.cmake:82 (message):
No Qt5 qmake executable found. Can't check QT_INSTALL_PLUGINS as
required
Call Stack (most recent call first):
/usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:256 (ecm_query_qt)
/usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include)
CMakeLists.txt:15 (include)
(I tried to attach the full build log, but I think the mailserver
rejected it;
it was ~250kb). It looks like maybe QT_MAJOR_VERSION is somehow
being set to 5,
and /usr/share/ECM/kde-modules/KDEInstallDirs.cmake line 15 is
pulling in
KDEInstallDirs5.cmake as a consequence? Why would that be happening
in a call to `dh_auto_configure --buildsystem=kf6`? Shouldn't the kf6
build sequence be smart enough to not try to use the qt5 qmake? Is
there some
other place that the qt version might be specified that I'm not aware
of?
On this front: I can reproduce the issue with this cmake invocation:
cmake \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=None \
-DCMAKE_INSTALL_SYSCONFDIR=/etc \
-DCMAKE_INSTALL_LOCALSTATEDIR=/var \
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON \
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF \
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON \
-DFETCHCONTENT_FULLY_DISCONNECTED=ON \
-DCMAKE_INSTALL_RUNSTATEDIR=/run \
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON \
"-GUnix Makefiles" \
-DCMAKE_VERBOSE_MAKEFILE=ON \
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu \
-DCMAKE_BUILD_TYPE=Debian \
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON \
..
(modulo typesetting typos). By omitting the
KDE_INSTALL_USE_QT_SYS_PATHS=ON last
option, I can get it to work (i.e., successfully run cmake).
I still get the error
-- No Qt5 qmake executable found. Can't check QT_INSTALL_PREFIX
but, now it is nonlethal, since it apparently isn't being trying to
"check
QT_INSTALL_PLUGINS", whatever that means. So, it looks not having
that option
only covers up the problem: qt6 builds are looking for qmake5. Why is
the kf6
tooling causing that to happen?
I am also getting warnings like:
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
FETCHCONTENT_FULLY_DISCONNECTED
So, it's reasonable to me that I might not have properly updated
CMakeLists.txt .
I'm open to any suggestions.
Thanks,
Antonio
