So i will write it out short and simply. I have a problem with egl wich prints out libEGL warning: DRI2: failed to authenticate.
I created an simple XWindow and tryed to attach an egl context to it but it fails on eglInitialize. And yes searched all ready for a solution but can not find one. Tryed some Librarys but im not very satisfied. I'm using the actual raspbian stretch with libgles2-mesa-dev, libegl1-mesa-dri,mesa-utils. And i link to EGL;GLESv2;X11;

Did you enable the new experimental GPU driver ? The old , stable one does not cooperate with X and is accessed completely orthogonal to X.

ghans

• Don't like the board ? Missing features ? Change to the prosilver theme ! You can find it in your settings.
• Don't like to search the forum BEFORE posting 'cos it's useless ? Try googling : yoursearchtermshere site:raspberrypi.org

What i also not understand is why are there no libGLESv2.so files in the armhf folder even i use full kms how can the use it when there is no egl library or GLES library where the link to? Another thing is with a manual installation of vc4 it works like a charm in jessie but i this is not possible on stretch.

Very interssting is that i found out this could be actually
taht i link to the wrong lib even if i get an right
egldisplay wich makes for me no sense but it is so.
This opens the Question how to link to the vc4 lib in a way were we can use X?

The foundation renamed some libraries in August 2017 to clear up some confusion.

libGLESv2.so became libbrcmGLESv2.so
libEGL.so became libbrcmEGL.so

and so on. Why ? It turns out Mesa ships libraries with exactly the same name and people were gettting confused which libraries were from Mesa and which from Broadcom. This is especially fatal since the libraries Mesa provides are better integrated with X , but less stable and a bit slower (speed has increased dramatically since hardware rendering was added).

ghans

• Don't like the board ? Missing features ? Change to the prosilver theme ! You can find it in your settings.
• Don't like to search the forum BEFORE posting 'cos it's useless ? Try googling : yoursearchtermshere site:raspberrypi.org

The foundation renamed some libraries in August 2017 to clear up some confusion.

libGLESv2.so became libbrcmGLESv2.so
libEGL.so became libbrcmEGL.so

and so on. Why ? It turns out Mesa ships libraries with exactly the same name and people were gettting confused which libraries were from Mesa and which from Broadcom. This is especially fatal since the libraries Mesa provides are better integrated with X , but less stable and a bit slower (speed has increased dramatically since hardware rendering was added).

ghans

.. and this has turned compiling some packages against these libraries into a real nightmare.

Minimal Kiosk Browser (kweb)
Slim, fast webkit browser with support for audio+video+playlists+youtube+pdf+download
Optional fullscreen kiosk mode and command interface for embedded applications
Includes omxplayerGUI, an X front end for omxplayer

Or to say it in other words wich argument do i need to pass to gcc to accept my XWindow.
Today i use: gcc main.cpp -lX11 -lEGL -lGLESv2 wich compiles but throws the DRI2 warning wich then doesn't let me draw anything to the screen.
I can use: