That's the way OpenGL versioning works, you could only expose some GL base level if you support *all* of the needed extensions for this base level. However every driver is free to expose additional extensions it supports.
It is the applications job to enumerate the available extensions in order to check which functionality it can use. If GLEW doesn't let you use glGenBuffers although it is supported by the driver this is a bug in GLEW, not mesa. -- Lucas Am Montag, den 20.06.2011, 11:22 -0600 schrieb tom fogal: > I am trying to get some regression tests to run in Xvfb. On my > workstation, the GL_VERSION string from this is: > > 1.4 (2.1 Mesa 7.7.1) > > according to glxinfo. The extensions fairly clearly show 2.x features. > Is it perhaps the case that 2.1 features were available in 7.7.1, but > not /all/ 2.1 features, and thus this was labelled incorrectly? The > version string seems "fixed" in more modern versions. > > In any case, the above version string breaks projects like GLEW > -- one application I have breaks because GLEW doesn't try to load > glGenBuffers, thinking it will not be there. A string like the above > suggests that GLEW should just try to load whatever it can, and just > ignore the version string from the library. > > Thoughts? > > -tom > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
