| Summary: | Review Request: gl4es - OpenGL to GL ES translation library | ||
|---|---|---|---|
| Product: | Package Reviews | Reporter: | Nicolas Chauvet <kwizart> |
| Component: | Review Request | Assignee: | RPM Fusion Package Review <rpmfusion-package-review> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | rpmfusion-package-review |
| Priority: | P1 | ||
| Version: | Current | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | rpi | ||
| Bug Depends on: | |||
| Bug Blocks: | 2 | ||
|
Description
Nicolas Chauvet
2020-10-07 14:50:22 CEST
I don't plan to exclude the libGL to avoid dependency computation error given that for the rpi namespace it's already expected to have the rpi gles and egl as an override, so with that library it's possible to fully replace the system libglvnd. (until raspi userspace supports libglvnd which isn't planned so far). See also https://github.com/raspberrypi/userland/issues/556 I've dropped aarch64 for now as I don't expect much use case. Given the CPU ressources there, I expect most case can use the llvmpipe software emulation for libGL. I'm not even sure that In the RPI case, there isn't even a vendor libGLESv2,libEGL as it's expected to rely on vc4 userspace driver from mesa instead. I'm not even sure that an vendor implementation lacking libGL even exists... I've dropped the idea to use this as a system path. It would be picked by the desktop environment over any llvmpipe implementation leading to crash because it would not be fully conformant. Instead I expect this libGL can be used for simple libGL programs with LD_LIBRARY_PATH or more probably, old x86 gl games using box86 on rpi (with downstream graphic drivers)... not relevant anymore even for rpi. |