https://bugzilla.redhat.com/show_bug.cgi?id=1415143
--- Comment #27 from Nicolas Chauvet (kwizart) <[email protected]> --- I'm not sure if we aren't going too fast here. As I understand egl-wayland, it's "aimed" to be generic implementation on top of (generic) EGL. Unfortuntately, this doesn't seem to be completely generic yet as the produced shared object name suggest. (nvidia-egl-wayland.so.1). Looking at the code: 1/ it seems to rely on a special magic number for a fifo dedicated to nvidia client (driver) side communication. https://github.com/NVIDIA/egl-wayland/blob/master/wayland-egl/wayland-egl-ext.h#L33 2/ It seems to use on #ifdef EGL_NV_stream_remote available https://www.khronos.org/registry/EGL/extensions/NV/EGL_NV_stream_remote.txt Right now this eglext.h header update is available in mesa master (not in 17.0 or 13.0 branches) a98b3a0872f9c542e6db75d17b7875a3f0374a14 So right now we cannot build a full featured (nvidia-)egl-wayland replacing the pre-build version. (we would need to backport at least the header update in our mesa version). Then I agree we don't know if this project will handle others (mesa?, amdgpu-pro ?) egl-wayland implementation or if it will only be the nvidia dedicated implementation. My bet is that it will became generic as soon as there are others adopters. Hence I don't think moving the directories into libglvnd-gl is relevant for the long run. But I agree this is a possible way forward. (don't forget arched requires: libglvnd-egl%{?_isa} ) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected]
