Qt 5.9 error eglfs with raspberry pi 3

jsulm

@requinham Try to start your app with QT_DEBUG_PLUGINS variable set to get a more verbose output.

requinham

@jsulm no change I have the same input. I also set QT_LOGGING_RULES="qt.qpa.*=true" but same output !

jsulm

@requinham Is it a debug build?

QT_DEBUG_PLUGINS=1 && ./my_app

requinham

@jsulm It is a release build like specified in configure command (-release)

jsulm

@requinham I mean: did you build your app in debug mode?

requinham

@jsulm No I compile it on release mode with the same parameter as I compile qt additional libraries (qtdeclarative, qtquickcontrols, etc.)

jsulm

@requinham Well, if you want to debug a problem you should build in debug mode.

moldovan.catalin

How did you managed to compile with Raspbian Stretch? I have Raspbian Stretch Lite and I don't manage to compile. It seems it doesn't find EGLFS support. I was trying to build native on the board (RPI3) with this config:

/../qt5/configure -release -opengl es2 -eglfs -no-gtk -tslib -force-pkg-config -opensource -confirm-license -make libs -device linux-rasp-pi3-g++ -optimized-qmake -reduce-exports -no-use-gold-linker -nomake examples -no-compile-examples -skip qtwebengine -qt-pcre -ssl -evdev -system-freetype -fontconfig -glib -prefix /opt/qt5pi -v

Taking a closer look at /opt/vc/lib folder on the board where the legacy VideoCore drivers are located I noticed that their names are changed. Instead of standard libEGL, libGLESv2 names I saw libbrcmEGL, libbrcmGLESv2 etc.

requinham

@moldovan.catalin For compiling I use raspbian stretch full version and I boot with it to install some libraries (libgles2, libgl-mesa-dri, libglew-dev, libpng, libjpeg, etc.) after this I remount my sdcard filesystem on my Ubuntu machine and I run the configure like mentioned in the first post.
I also compiled Qt 5.9.2 natively on Raspberry Pi 3 successfully and I succeeded running programs. I confirm that instead of eglfs there is brcm-eglfs and instead of libEGL and libGLESv2 there is libbrcm{EGL,GLESv2}.
I think it is a patched version for RPI.

requinham

@jsulm Thank you for your help but no more result ! I guess the problem is when compiling in host machine because my program can't see anything in the RPI...
I succeded to compile and run latest Qt natively in RPI3. Obviously, this take more time but make something works. It must important for the rest to found the problem with this may be in fixQualifiedLibraryPaths script !

jsulm

@moldovan.catalin You can create symbolic link in /opt/vc/lib pointing to these libraries but having old names.