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. RaspberryPi2EGLFS guide - EGL/GLES libraries fix fail
Forum Updated to NodeBB v4.3 + New Features

RaspberryPi2EGLFS guide - EGL/GLES libraries fix fail

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
8 Posts 2 Posters 1.3k Views 2 Watching
  • 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.
  • R Offline
    R Offline
    rrd0
    wrote on last edited by rrd0
    #1

    I built Qt 5.12.3 for Raspberry Pi following the RaspberryPi2EGLFS guide from Qt Wiki.

    I was able to reproduce almost each one of the steps described in the guide, but on step 14 (EGL/GLES libraries fix), I failed to create some symbolic links.

    I couldn't create the following links

    sudo ln -s /opt/vc/lib/libbrcmEGL.so /opt/vc/lib/libEGL.so
    sudo ln -s /opt/vc/lib/libbrcmGLESv2.so /opt/vc/lib/libGLESv2.so
    

    because the files /opt/vc/lib/libEGL.so and /opt/vc/lib/libGLESv2.so already exist.

    So, I moved those files to /opt/vc/lib/libEGL.so_backup and /opt/vc/lib/libGLESv2.so_backup, then I created the symbolic links and the rest of the steps worked like a charm.

    But I have a problem. Apps that run on another Qt build are crashing on this one. So, I think the problem may be those symbolic links.

    Are the symbolic links correct? Am I missing something? Anybody here had the same problem with EGLFS? If yes, how did you fix?

    Thanks!

    1 Reply Last reply
    0
    • sierdzioS Offline
      sierdzioS Offline
      sierdzio
      Moderators
      wrote on last edited by sierdzio
      #2

      Try bringing back your backup libs and running on them. I think raspbian has fixed this issue already (not sure) so symlinking may not be necessary at all.

      Alternatively, try running raspi-config and forcing the prioprietary graphics driver, then symlinking.

      (Z(:^

      R 1 Reply Last reply
      1
      • sierdzioS sierdzio

        Try bringing back your backup libs and running on them. I think raspbian has fixed this issue already (not sure) so symlinking may not be necessary at all.

        Alternatively, try running raspi-config and forcing the prioprietary graphics driver, then symlinking.

        R Offline
        R Offline
        rrd0
        wrote on last edited by
        #3

        @sierdzio

        I moved the original files back and deleted the links, but that didn't solve the problem. I'm still getting segfaults.

        1 Reply Last reply
        0
        • R Offline
          R Offline
          rrd0
          wrote on last edited by
          #4

          @sierdzio said in RaspberryPi2EGLFS guide - EGL/GLES libraries fix fail:

          Alternatively, try running raspi-config and forcing the prioprietary graphics driver, then symlinking.

          The only GL-related option I found on raspi-config is the one to disable OpenGL (Original non-GL desktop driver). I chose that option, but it didn't work too.

          1 Reply Last reply
          0
          • R Offline
            R Offline
            rrd0
            wrote on last edited by
            #5

            A whole week has past and I'm still struggling with this problem.

            1 Reply Last reply
            0
            • sierdzioS Offline
              sierdzioS Offline
              sierdzio
              Moderators
              wrote on last edited by
              #6

              Sorry but I can't help more. I don't have time right now to try it out again myself. Last time I did was back in Qt 5.10 times, I think, and after enabling the driver in raspi-config it worked.

              However, no matter which driver I used, there was no crash - perhaps you are actually facing a different issue? Are you sure your app works OK?

              (Z(:^

              R 1 Reply Last reply
              0
              • sierdzioS sierdzio

                Sorry but I can't help more. I don't have time right now to try it out again myself. Last time I did was back in Qt 5.10 times, I think, and after enabling the driver in raspi-config it worked.

                However, no matter which driver I used, there was no crash - perhaps you are actually facing a different issue? Are you sure your app works OK?

                R Offline
                R Offline
                rrd0
                wrote on last edited by
                #7

                @sierdzio said in RaspberryPi2EGLFS guide - EGL/GLES libraries fix fail:

                However, no matter which driver I used, there was no crash - perhaps you are actually facing a different issue? Are you sure your app works OK?

                Yes, I'm sure. It works fine on another build of Qt.

                1 Reply Last reply
                0
                • R Offline
                  R Offline
                  rrd0
                  wrote on last edited by
                  #8

                  Update:

                  1. The app crashs only on exit.

                  2. The stack trace shows me that the segfault happens inside QBasicDrag::disableEventFilter().

                  Information #1 is some help, cause it indicates that something is not being cleaned.

                  Info #2 also makes sense, cause drag-n-drop is not 100%. When I drag something, the pixmap that represents the drag is invisible.

                  If you guys have some idea on how to track this error, please let me know.

                  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