RaspberryPi2EGLFS guide - EGL/GLES libraries fix fail
-
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!
-
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. -
@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. -
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?
-
@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.
-
Update:
-
The app crashs only on exit.
-
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.
-