Yes, I do have directfb in DISTRO_FEATURES. The following is in my local.conf:
http://pastebin.com/8vmN0r7Z Furthermore, to even get this to build I had to alter the libva recipe because it caused conflicts. Even though I was excluding x11 it would still try to build libva-x11 due to the following RDEPENDS for egl in libva_1.5.0_bb: RDEPENDS_${PN}-egl =+ "${PN}-x11" I changed this to RDEPENDS_${PN}-egl =+ "${PN}" in order for it to build. I know I probably should definitely not be doing this, but it is for the purpose of testing. All of this gets pulled in due to my images inclusion of hardware codecs for hardware acceleration: IMAGE_FEATURES += "splash package-management ssh-server-openssh hwcodecs" where hwcodecs is defined by the Intel BSP as the following: MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0" So in the end, I can get the app to run without error by including x11 which allows me to fully include the Intel hardware acceleration, but I do not want x11. I feel like there is the aforementioned dependency that should not exist, but I am not in the position to know how to work around this. As I said, if I alter the dependency of libva-egl on libva-x11 it will build, but I get the EGL surface error. Any insight is greatly appreciated. On Fri, Apr 22, 2016 at 9:22 PM, Khem Raj <[email protected]> wrote: > > > On Apr 22, 2016, at 6:07 PM, Ryan Elkholy, PhD, PE < > [email protected]> wrote: > > > > Hello, > > > > I am am trying to make a build that includes meta-qt5 without x11 or > > wayland on the Minnowboard Turbot (x86-64). I was successful in building > my > > image but the problem occurred when testing my basic qt app on the image. > > When trying to run the app I get the following error: > > > > EGL Error : Could not create the egl surface: error = 0x300 > > > Do you have ‘directfb’ in DISTRO_FEATURES > > > > I have been trying to find a solution for this for weeks with no luck. I > am > > able tu run my application when including x11, but I am trying to avoid > it. > > Does anyone know any solution for this? Any insight will be helpful > because > > I have been stumped for weeks. If nobody knows of a solution is it > possible > > to dig deeper into this error and see what is causing it? If so, how? > > > > Thanks > > -- > > _______________________________________________ > > Openembedded-devel mailing list > > [email protected] > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > > > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > >
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
