Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-36256

Using CONFIG += link_pkgconfig gives weird errors when Qt is configured without pkg-config suppoort

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: P3: Somewhat important P3: Somewhat important
    • 5.8.0 Beta
    • 5.2.0
    • Build System
    • None
    • 0239b4f21705af3c47ebfda34fa354ecc865c52d

      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...

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            buddenha Oswald Buddenhagen
            peppe Giuseppe D'Angelo
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes