2. Needs information:
"The specific problem that we are trying to solve is that with Qt client applications on the desktop, EGL fails to recognize native MirConnections as valid EGLNativeDisplayType objects, falling back to X11 and crashing. The reason is that the symbols needed for the MirConnection validation and which are exported by libmirclient, are not available to libEGL for dynamic runtime resolution."
How is failing to find a symbol not a fatal error? If we need validation functions and presently can't find them then what function is being called?
Experience with many global/local symbol resolution problems in plugin systems tells me there's possibly a nicer solution but I still don't fully understand the problem being solved.
1. Needs Fixing: Text conflict in debian/rules
2. Needs information: yType objects, falling back to X11 and crashing. The reason is that the symbols needed for the MirConnection validation and which are exported by libmirclient, are not available to libEGL for dynamic runtime resolution."
"The specific problem that we are trying to solve is that with Qt client applications on the desktop, EGL fails to recognize native MirConnections as valid EGLNativeDispla
How is failing to find a symbol not a fatal error? If we need validation functions and presently can't find them then what function is being called?
Experience with many global/local symbol resolution problems in plugin systems tells me there's possibly a nicer solution but I still don't fully understand the problem being solved.