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

QtWayland build fails with "qwayland-server-wayland.h: No such file or directory" (again)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2: Important
    • Resolution: Done
    • Affects Version/s: 5.11.2
    • Fix Version/s: 5.12.4
    • Component/s: Build System
    • Labels:
      None
    • Platform/s:
      Linux/Wayland
    • Commits:
      c2917243a96d19c9cd49c827e63d40b7c0110d7d

      Description

      The fix for QTBUG-70056 (2aa779e893bd7526c97a1968c6835204e4e985e2) breaks building wayland extension, if the source dir of the module is not on the same "depth" level in the filesystem as the qtbase source dir.

      E.g.:

      Qt build from source in ~/git/qt (standard dev shadow build from git into ~/git/build-qt)

      Building QtWayland together with Qt (so its sources are in ~/git/qt/qtwayland) works ok.

       

      BUT, moving QtWayland out to e.g. ~/foo/qtwayland (and shadow building into ~/foo/build-qtwayland) breaks the build, because the generated forward include header tries to include the generated Wayland extension header using a relative path that has one "../" to much.

       

      The funny thing is now that moving QtWayland to ~/foo/bar/qtwayland works again, because the amount of "../" needed to jump from qtbase's build dir to qtwayland's source dir is the same.

       

      The same problem applies to any module using Wayland extension (e.g. QtApplicationManager), but it is easily reproduced with QtWayland - that's why I chose it as an example here.

       

        Attachments

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

          Activity

            People

            • Assignee:
              jbornema Joerg Bornemann
              Reporter:
              rgriebl Robert Griebl
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes