In embedded world, GPU support egl, gles1, gles2 and openvg, not opengl. So package like x11-libs/cairo can depends on the virtual packages.
Agreed. CC'ing lu_zero@gentoo.org since he was doing some eselect-opengl work sort of related to this.
1. mesa installs all libraries into /usr/lib/opengl, includes egs, opengles and openvg, maybe it misleading? 2. eselect-opengl currently dose not support switch to no-opengl implementation. 3. Switch implementation must whole or nothing, eg, we can't mix xorg-x11 (egl, opengl, opengl es 1&2, openvg) with nvidia (opengl only) up, and for my case, imx53 (egl, opengl es 1&2, openvg), because usage of HW resources. 4. Switch implementation maybe break binary linkage, eg. switch from a implementation with opengl support to opengl es only one 5, opencl support?
Seems latest stable nvidia drivers now support EGL, may be it is time to add virtual/egl?
virtual/egl sounds like a good idea. I noticed that gtk-3.16 now pulls in libepoxy which currently has a dep on mesa. If I have understood things correctly, mesa will only be used for headers and pkgconfig for nvidia users, which makes it feel a bit unnecessary to pull in for this. So for me the preferred solution would be to have a virtual/egl that provides both libEgl.so and the egl headers/pkgconfig... given that I have understood everything correctly. Graphics acceleration standards are terribly confusing :)
I guess what I'm looking for is something similar to debian's libegl1-mesa-dev, granted that it also works for nvidia drivers (slightly unrelated to the virtual/egl topic)