Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
6.6.3, 6.7.0
-
None
-
Linux/X11
-
337cadbcb (dev), ac4920b5c (dev), 062f701a1 (6.7), 5ee9da89a (6.7)
Description
To keep it short, Qt6.6.2 gave:
$ pkgconf --modversion --cflags Qt6Widgets 6.6.2 $ pkgconf --cflags Qt6Widgets -I/usr/include/qt6/QtWidgets -I/usr/include/qt6 -DQT_WIDGETS_LIB -I/usr/include/qt6/QtGui -DQT_GUI_LIB -I/usr/include/qt6/QtCore -DQT_CORE_LIB -I/usr/lib64/qt6/mkspecs/linux-g++
And then with Qt6.6.3 (or 6.7.0):
$ pkgconf --modversion Qt6Widgets 6.6.3 $ pkgconf --cflags Qt6Widgets -I/usr/include/qt6/QtWidgets -I/usr/include/qt6 -DQT_WIDGETS_LIB
I assume this is not intentional? Same happens for others e.g. --cflags Qt6Gui does not show QtCore include path either.
Was noticed after a bug report to Gentoo about a chromium build failure with the qt6 shim. chromium combines pkgconf's Qt6Core and Qt6Widgets but omits Qt6Gui, which led to an include failure for <QImage> after the include path went missing.
Attachments
| For Gerrit Dashboard: QTBUG-124135 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 566192,1 | Prefer the versioned targets over the namespaceless one when collecting deps | tqtc/lts-6.5 | qt/tqtc-qtbase | Status: NEW | +2 | 0 |
| 566193,1 | Consider '^Qt6' deps when generating pkg-config files | tqtc/lts-6.5 | qt/tqtc-qtbase | Status: NEW | +2 | 0 |
| 553260,6 | Consider '^Qt6' deps when generating pkg-config files | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 553372,4 | Prefer the versioned targets over the namespaceless one when collecting deps | dev | qt/qtbase | Status: MERGED | +2 | +1 |
| 560058,2 | Consider '^Qt6' deps when generating pkg-config files | 6.7 | qt/qtbase | Status: MERGED | +2 | 0 |
| 560060,2 | Prefer the versioned targets over the namespaceless one when collecting deps | 6.7 | qt/qtbase | Status: MERGED | +2 | 0 |