# ls -la /usr/lib64/chromium-browser/*.so -rw-r--r-- 1 root root 17928 бер 12 19:58 libEGL.so -rw-r--r-- 1 root root 2165120 бер 12 19:58 libGLESv2.so -rw-r--r-- 1 root root 3796976 бер 12 19:58 libosmesa.so Most probably this is side-effect of https://gitweb.gentoo.org/repo/gentoo.git/commit/www-client/chromium?id=e7b214d802b93e71f715298bcaffc1590541bca6 However, I wonder why this libraries are built with chromium at all. Should chromium depends on mesa[osmesa] instead? BTW, libEGL and libGLESv2 comes not from third_party/mesa but from third_party/angle. Can we disable building angle and require mesa[egl,gles] instead?
The TL;DR here is that ANGLE is Google's backend for webgl used in Firefox and Chromium-based browsers. It was initially used to translate GL into D3D but for Linux allows those to be sent to desktop GL _or_ translated to vulkan. I'm hesitant to debundle this. It's pretty deeply linked to Blink, at the very least, and ANGLE is using system GL/Vulkan to do any drawing at the end of the day. If somebody wants to untangle the build system code, debundle the libs, work out how to make Chromium build against system GL and ANGLE(?), and upstream all of than this I'm happy to look at toggling those options, but I don't think I'm going to be touching this for now.
To add to this, my current Chromium chrome://gpu looks like this: GL implementation parts : (gl=egl-angle,angle=opengl) Display type : ANGLE_OPENGL GL_VENDOR : Google Inc. (NVIDIA Corporation) GL_RENDERER : ANGLE (NVIDIA Corporation, NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2, OpenGL ES 3.2 NVIDIA 560.28.03) GL_VERSION : OpenGL ES 2.0.0 (ANGLE 2.1.0 git hash: unknown hash)
