Also, while GLESv1 is the fixed-pipeline stuff, libGLESv1_CM.so just provides a set of forwarder functions. Libglvnd forwards those calls to a vendor library based on the current context, so it's up to the vendor library what to do with them. If a vendor doesn't provide a function to forward to, then libglvnd sends the function to an error or no-op stub (the same way it would handle calling a function without a current context at all).
For something like GLESv1, if a vendor library doesnt't support it, then it would just return NULL from its eglCreateConext or glXCreateContextAttribsARB implementation. At that point, the vendor library doesn't need to implement any of the GLESv1 functions -- trying to call a GLESv1 function without a current GLESv1 context is an application error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1782285 Title: Add missing libGLESv1_CM.so to Bionic Status in libglvnd package in Ubuntu: Confirmed Status in libglvnd source package in Bionic: New Bug description: libGLESv1_CM.so is provided by GLVND project. This binary is missing in Bionic. It is also not listed under libglvnd source package in Bionic: https://launchpad.net/ubuntu/bionic/+source/libglvnd This bug is to know if this was unintentional ? in that case can it be generated for Bionic-updates ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
