Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
5.2.0
-
None
-
0239b4f21705af3c47ebfda34fa354ecc865c52d
Description
I don't know the reasons why Qt tries to detect at build time if pkgconfig is present. This is usually false on Mac builds, hence no-pkg-config gets added to QT_CONFIG.
If pkgconfig is then installed, the user expects CONFIG += link_pkgconfig and PKGCONFIG = foo to "just work". Instead, Qt says "Package foo not found" (from link_pkgconfig.prf).
At least one should do an explicit test for contains(QT_CONFIG, no-pkg-config) there and not let packagesExist fail... but why do we require that "build time pkgconfig support" in order to use pkgconfig? Let's instead fail if the binary is not in PATH...
Attachments
Issue Links
- is duplicated by
-
QTBUG-56164 Need official way to use pkg-config, regardless of what Qt's setting was
-
- Closed
-
For Gerrit Dashboard: QTBUG-36256 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
175096,2 | decouple packageExists() and PKGCONFIG from qt configuration | 5.8 | qt/qtbase | Status: MERGED | +2 | 0 |