With the release of 32bit and 64 bit EGL from nvidia we now need a mechanism that allows wayland to use nvidia EGL. for now i think it requires mesa egl. I am not sure what gles is used for but it is required for KDE with wayland. I geuss a virtual ebuild and eselect module is required like there is for opengl and perhaps for gles as well.
What is the problem here? libEGL and libGLES* should be interchangeable in any implementation. x11-drivers/nvidia-drivers does not provide the headers, though, so setting a DEPEND on a virtual which RDEPENDS on both media-libs/mesa and x11-drivers/nvidia-drivers will not fix your issue, whatever it is. Also, eselect-opengl works just fine.
what also what? Of course eselect-opengl works fine, that is the point. Wayland needs way of knowing whether to use nvidia EGL or mesa EGL
(In reply to C.J. Wijtmans from comment #2) > what also what? What problem are you trying to report? All I see is a solution. > Of course eselect-opengl works fine, that is the point. > Wayland needs way of knowing whether to use nvidia EGL or mesa EGL How does introducing a virtual and an eselect module tell wayland anything? It should compile against mesa, not nvidia EGL.
No it shouldnt, whats the point of nvidia supporting EGL for wayland if we build it against a mesa software renderer? Does mesa EGL compile against nvidia opengl? I dont think so but i dont know.
This is what i am talking about: # ls -lah /usr/lib64/libEGL.so lrwxrwxrwx 1 root root 34 Mar 27 02:15 /usr/lib64/libEGL.so -> opengl/nvidia/lib/libEGL.so.334.21 There is no reason for me to have a mesa EGL module built for my system. Yet packages depend on mesa EGL. I geuss EGL can be handled by eselect opengl.
obsolete?
