> Make the enable/disable configurable by an environment variable, like
> so:
>
> if ( getenv( "LIBGL_DISABLE_MULTITEXTURE" ) ) {
> gl_extensions_disable( ctx, "GL_ARB_multitexture" );
> }
> if ( getenv( "LIBGL_ENABLE_TEXTURE_ENV_ADD" ) ) {
> gl_extensions_enable( ctx, "GL_EXT_texture_env_add" );
> gl_extensions_enable( ctx, "GL_ARB_texture_env_add" );
> }
>
> Then, a user/app can just do something equivalent to:
>
> export LIBGL_DISABLE_MULTITEXTURE=1
> ./my_app
>
> And you're done. Variable naming left as an exercise for the user.
>
> -- Gareth
Extensions do get detected by browsing a lengthy string.
Entry point adresses are retrived via a single GL API call.
Extensions constants and alikes simply get used and
will possibly get hounoured by the misc GL calls.
Therefore i would call this "hide" and "reveal" in the first row
when some intermediate layer does remove or add
the repsective strings or bases addresses.
Regards, Alex.
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
