Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Qt 5.12.2 Raspberry Pi X11
QtWS25 Last Chance

Qt 5.12.2 Raspberry Pi X11

Scheduled Pinned Locked Moved Solved Mobile and Embedded
19 Posts 8 Posters 7.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    SGaist
    Lifetime Qt Champion
    wrote on 22 Mar 2019, 20:43 last edited by
    #9

    Hi,

    Since Qt 5.12.1, xkbcommon is not provided anymore as all older platforms supported now provides that dependency.

    Interested in AI ? www.idiap.ch
    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

    L 1 Reply Last reply 23 Mar 2019, 23:11
    1
    • S SGaist
      22 Mar 2019, 20:43

      Hi,

      Since Qt 5.12.1, xkbcommon is not provided anymore as all older platforms supported now provides that dependency.

      L Offline
      L Offline
      Lashc
      wrote on 23 Mar 2019, 23:11 last edited by
      #10

      @SGaist I checked to see if I have any xkbcommon packages installed on my Raspberry Pi, and I discovered the following ones:

      libxkbcommon-dev, libxkbcommon-x11-0, libxkbcommon-x11-dev, and libxkbcommon0
      

      I tried to compile Qt 5.12.2 again, but I still received errors about xkbcommon and xcb.

      1 Reply Last reply
      0
      • S Offline
        S Offline
        SGaist
        Lifetime Qt Champion
        wrote on 24 Mar 2019, 20:55 last edited by
        #11

        Which version are they ?

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        L 1 Reply Last reply 27 Mar 2019, 03:54
        0
        • N Offline
          N Offline
          Nikhilesh N
          wrote on 25 Mar 2019, 04:39 last edited by
          #12

          This topic has garnered my interest, and I'll follow it from now. Getting to know very interesting revelations by the way, Samuel.

          1 Reply Last reply
          0
          • S SGaist
            24 Mar 2019, 20:55

            Which version are they ?

            L Offline
            L Offline
            Lashc
            wrote on 27 Mar 2019, 03:54 last edited by
            #13

            @SGaist Here's a list of the packages and their respective versions:
            libxkbcommon-dev: 0.7.1-2~deb9u1
            libxkbcommon-x11-0: 0.7.1-2~deb9u1
            libxkbcommon-x11-dev: 0.7.1-2~deb9u1
            libxkbcommon0: 0.7.1-2~deb9u1

            1 Reply Last reply
            0
            • H Offline
              H Offline
              hlmjr
              wrote on 30 Mar 2019, 16:01 last edited by
              #14

              This is due to changes in Qt's configure system in 5.12+. Namely, commits like this one: https://github.com/qt/qtbase/commit/e80bf655e922e9864f8843b5e7bbb47019a6d95a

              Anywhere there once was "include": "suchandsuch" inside a test that was changed to "headers": "suchandsuch" outside the test fails now when cross-compiling for Raspbian.

              I'm in the process of trying to find and revert them all but have gotten stuck on the somewhat more complicated Xlib detection:

              "xlib": {
              	"label": "XLib",
              	"test": {
              		"main": [
              			"Display *d = XOpenDisplay(NULL);",
              			"XCloseDisplay(d);"
              		]
              	},
              	"headers": "X11/Xlib.h",
              	"sources": [
              		{ "type": "makeSpec", "spec": "X11" }
              	]
              },
              

              It's that { "type": "makeSpec", "spec": "X11" } line that is failing. I'm not yet sure how to modify that one. Once I figure this out I'll open a bug and see if we can boil it down to a root cause. I'm sure the way I'm adjusting the configure.json isn't quite correct.

              /ranton How changes that can break this on this level made their debut in an LTS is beyond me. /rantoff

              1 Reply Last reply
              3
              • H Offline
                H Offline
                hlmjr
                wrote on 31 Mar 2019, 03:01 last edited by
                #15

                As I suspected, I was going down the wrong path. The issue is QTBUG-74326, and resolved in this patch which is scheduled for Qt 5.12.3.

                It doesn't seem to be a perfect fix as it corrects the system library detection for me but breaks linking QtWebEngine.

                A 1 Reply Last reply 1 Apr 2019, 15:28
                2
                • H hlmjr
                  31 Mar 2019, 03:01

                  As I suspected, I was going down the wrong path. The issue is QTBUG-74326, and resolved in this patch which is scheduled for Qt 5.12.3.

                  It doesn't seem to be a perfect fix as it corrects the system library detection for me but breaks linking QtWebEngine.

                  A Offline
                  A Offline
                  Antiheld
                  wrote on 1 Apr 2019, 15:28 last edited by
                  #16

                  @hlmjr said in Qt 5.12.2 Raspberry Pi X11:

                  As I suspected, I was going down the wrong path. The issue is QTBUG-74326, and resolved in this patch which is scheduled for Qt 5.12.3.

                  It doesn't seem to be a perfect fix as it corrects the system library detection for me but breaks linking QtWebEngine.

                  I tried to apply the patch, however it changed nothing. Can you explain how you did it? There's no explanation online on how to apply such patches manually, only via git when having previously cloned the git repo. I wanted to apply it to the current source release (qt-everywhere-src-5.12.2), though.

                  I myself am currently trying to cross-compile Qt 5.12.2 for Raspberry Pi 3 B+.
                  Weirdly enough I have to configure with -device linux-rasp-pi-g++ to get EGLFS to work, might that be the problem?

                  H 1 Reply Last reply 2 Apr 2019, 13:27
                  0
                  • A Antiheld
                    1 Apr 2019, 15:28

                    @hlmjr said in Qt 5.12.2 Raspberry Pi X11:

                    As I suspected, I was going down the wrong path. The issue is QTBUG-74326, and resolved in this patch which is scheduled for Qt 5.12.3.

                    It doesn't seem to be a perfect fix as it corrects the system library detection for me but breaks linking QtWebEngine.

                    I tried to apply the patch, however it changed nothing. Can you explain how you did it? There's no explanation online on how to apply such patches manually, only via git when having previously cloned the git repo. I wanted to apply it to the current source release (qt-everywhere-src-5.12.2), though.

                    I myself am currently trying to cross-compile Qt 5.12.2 for Raspberry Pi 3 B+.
                    Weirdly enough I have to configure with -device linux-rasp-pi-g++ to get EGLFS to work, might that be the problem?

                    H Offline
                    H Offline
                    hlmjr
                    wrote on 2 Apr 2019, 13:27 last edited by
                    #17

                    @Antiheld True, it is difficult to get a patch from those changesets they way they're displayed in gerrit. I created one myself you can obtain from https://www.sky-meyg.com/downloads/rpi-qt5.12-configure.patch. Apply it with patch -p0 < rpi-qt5.12-configure.patch in your Qt source directory.

                    A 1 Reply Last reply 2 Apr 2019, 17:21
                    0
                    • H hlmjr
                      2 Apr 2019, 13:27

                      @Antiheld True, it is difficult to get a patch from those changesets they way they're displayed in gerrit. I created one myself you can obtain from https://www.sky-meyg.com/downloads/rpi-qt5.12-configure.patch. Apply it with patch -p0 < rpi-qt5.12-configure.patch in your Qt source directory.

                      A Offline
                      A Offline
                      Antiheld
                      wrote on 2 Apr 2019, 17:21 last edited by
                      #18

                      @hlmjr Thank you for your quick answer!
                      Weirdly enough it doesn't change anything for me. Maybe I'm doing something wrong.
                      For now EGLFS will have to suffice, I guess.
                      Thank you anyway!

                      1 Reply Last reply
                      0
                      • S Offline
                        S Offline
                        silicon
                        wrote on 18 Feb 2020, 13:57 last edited by
                        #19

                        @Lashc said in Qt 5.12.2 Raspberry Pi X11:

                        12.2 to my Raspberry Pi 3 B+ f

                        Hello,
                        I'm also using same setup RPi 3B+ with Qt5.12.2
                        facing the same issue with xcb.
                        i've tried all above mentioned solutions nothing works for me.
                        Could you solve the issue?

                        Thanks in advance.

                        1 Reply Last reply
                        0

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved