Bug#1038699: marked as done (qt6-declarative-dev: files missing ... somehow)
Your message dated Wed, 21 Jun 2023 01:02:11 +0200
with message-id <3745532.kQq0lBPeGt@treadstone-71>
and subject line
has caused the Debian Bug report #1038699,
regarding qt6-declarative-dev: files missing ... somehow
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1038699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038699
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qt6-declarative-dev
Version: 6.4.2+dfsg-1
Severity: normal
while building qt creator, cmake spits out this message during the
generation phase (that is, after configuration is done):
======
CMake Error in src/plugins/qmldesigner/CMakeLists.txt:
Imported target "Qt::QmlPrivate" includes non-existent path
"/usr/include/x86_64-linux-gnu/qt6/QtQml/6.4.2"
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:
* The path was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and references files it does not
provide.
======
i have no clue where this is coming from, because there are no obvious
hits for QmlPrivate in the cmake directory.
but once i install qt6-declarative-private-dev, the error goes away.
i suppose this might be some dynamic magic in the upstream code that
isn't prepared for actually being split into public and private.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qt6-declarative-dev depends on:
ii libqt6labsanimation6 6.4.2+dfsg-1
ii libqt6labsfolderlistmodel6 6.4.2+dfsg-1
ii libqt6labsqmlmodels6 6.4.2+dfsg-1
ii libqt6labssettings6 6.4.2+dfsg-1
ii libqt6labssharedimage6 6.4.2+dfsg-1
ii libqt6labswavefrontmesh6 6.4.2+dfsg-1
ii libqt6opengl6-dev 6.4.2+dfsg-11
ii libqt6qml6 6.4.2+dfsg-1
ii libqt6qmlcompiler6 6.4.2+dfsg-1
ii libqt6qmlcore6 6.4.2+dfsg-1
ii libqt6qmllocalstorage6 6.4.2+dfsg-1
ii libqt6qmlmodels6 6.4.2+dfsg-1
ii libqt6qmlworkerscript6 6.4.2+dfsg-1
ii libqt6qmlxmllistmodel6 6.4.2+dfsg-1
ii libqt6quick6 6.4.2+dfsg-1
ii libqt6quickcontrols2-6 6.4.2+dfsg-1
ii libqt6quickcontrols2impl6 6.4.2+dfsg-1
ii libqt6quickdialogs2-6 6.4.2+dfsg-1
ii libqt6quickdialogs2quickimpl6 6.4.2+dfsg-1
ii libqt6quickdialogs2utils6 6.4.2+dfsg-1
ii libqt6quicklayouts6 6.4.2+dfsg-1
ii libqt6quickparticles6 6.4.2+dfsg-1
ii libqt6quickshapes6 6.4.2+dfsg-1
ii libqt6quicktemplates2-6 6.4.2+dfsg-1
ii libqt6quicktest6 6.4.2+dfsg-1
ii libqt6quickwidgets6 6.4.2+dfsg-1
ii qt6-base-dev 6.4.2+dfsg-11
ii qt6-declarative-dev-tools 6.4.2+dfsg-1
ii qt6-qmltooling-plugins 6.4.2+dfsg-1
qt6-declarative-dev recommends no packages.
qt6-declarative-dev suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
qtcreator does indeed need the private headers from qtdeclarative to
build, see https://salsa.debian.org/qt-kde-team/qt/qtcreator/-/blob/
master/debian/control. An upstream project cannot know whether the
public and private headers are in the same or in different packages.
When private headers are needed in a project, you normally have to add
the corresponding package to the build dependencies.
Your error is quite typical for that. When cmake looks for a private
target in a directory with the exact Qt version (6.4.2 in this case),
then it's often the private headers that are missing.
I'm closing this as I don't see how this is a bug. It's just the way it
is.
--
Med vänliga hälsningar
Patrick Franz
--- End Message ---
Reply to: