[meta-freescale] Error 0x300b in Qt5 applications with EGLFS

[Sébastien Taylor]

But do you remember what specific versions and configurations you were using?  Also how exactly are you defining no x11 in distro flags?  Do you mean not adding it or is there a way to specifically block it?

Here’s the exact procedure I can follow today showing that it does not work.  It’s possible I am doing something incorrect here but if that’s the case I would appreciate if someone could point it out. Starting from a fresh checkout of dora and the dora branch of meta-qt5.

repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dora
cd sources
git clone -b dora https://github.com/meta-qt5/meta-qt5.git
cd ..
MACHINE=nitrogen6x . setup-environment build

I then add meta-qt5 to the bblayers.conf as well as adding the following to local.conf 

CORE_IMAGE_EXTRA_INSTALL += " qtbase qtbase-tools qtbase-plugins qtbase-fonts cinematicexperience”

And then continue with.

bitbake core-image-minimal

Now qtbase fails because of eglvivante.h including X.h which in turns #define None 0L which breaks qurl.h.  To work around this I add #define EGL_API_FB at the top of eglvivante.h as a hack and everything now compiles and the image is loaded onto the Nitrogen6X board.

Attempting to run the example results in the following.

root at nitrogen6x:/usr/share/cinematicexperience-1.0# ./Qt5_CinematicExperience
QXcbConnection: Could not connect to display 
Aborted
root at nitrogen6x:/usr/share/cinematicexperience-1.0# ./Qt5_CinematicExperience -p
latform eglfs
Segmentation fault


On Nov 21, 2013, at 1:07 AM, Eric Bénard <eric at eukrea.com> wrote:

> Hi Sébastien,
> 
> Le Wed, 20 Nov 2013 17:34:15 -0700,
> Sébastien Taylor <me at staylor.ca> a écrit :
> 
>> Could anyone comment on that has actually been tested and is expected to work in regards to Qt5 on i.MX6 Yocto?  X11 is said to be untested and causes compilation issues (eglvivante.h includes X.h whose #define None 0L breaks qurl.h).  Framebuffer doesn’t appear supported as this thread demonstrates, same issue on Nitrogen6X as well so not isolated to Wandboard.
>> 
>> Should we be trying DirectFB or Wayland?  Maybe someone who’s gotten this working could specify which version and configuration was used for testing?  
>> 
>> There’s quite a few of these threads and they all seem to die without any solutions.
>> 
> as said before : this was working in september just before dora went
> "stable" with framebuffer (so no x11 in DISTRO flags).
> 
> Eric