[Mesa-dev] multiple versions in version string

Ian Romanick idr at freedesktop.org
Mon Jun 20 13:48:33 PDT 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/20/2011 10:22 AM, tom fogal wrote:
> 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.

This happens when you're running an indirect context.  The underlying
driver can support 2.1 (and says so), but the protocol layers cannot.
Since there's no way to send protocol for glGenBuffers, you can't use it
indirect.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk3/siEACgkQX1gOwKyEAw/o+ACfb2jGZ3I34mjBrikjRv+8uURp
2JwAmgLiyUV/OIuorIu1gNmDHFWgAD9z
=Ve25
-----END PGP SIGNATURE-----


More information about the mesa-dev mailing list