Handle conflicts between epoxy and manually resolved function pointers
Review Request #125883 - Created Oct. 30, 2015 and submitted
For the functions from GL_FOO_robustness we want to resolve it by
ourselves in order to add a custom implementation if it's not available.
Unfortunately once epoxy.h is included this breaks as epoxy defines the
names and so through the preprocessor epoxy always wins.
So we need different names: all functions from robustness get a "kwin"
prefix and the usage is changed everywhere in kwin source code.
This is on top of http://commits.kde.org/clones/kwin/graesslin/kwin/7eaad2e6544e2437a69a27d186af6f6653f4e391
convincing "using KWin::glReadnPixels;" etc. in some relevant header?
epoxy will "win" because the functions are in "::", though that's really weird, since at lease eg. the shader test is in the KWin namespace - so there should be an ambiguity error on compilation?!
Otherwise rather resort to explicit namespace resolution (should also be ABI stable)?
kwinGlReadnPixels -> KWin::glReadnPixels
Status: Closed (submitted)
Submitted with commit ac1dbac8b11f66a10e7871ae878e30a3e5d42100 by Martin Gräßlin to branch master.
Today I investigated another issue together with Rohan and we figured out that all is stupid. We were looking at a completely wrong problem: the driver supports robustness, the problem is that we don't create a robust context.