[Mesa3d-dev] Re: ARB program rev 6

[Brian P. <bri...@tu...>]

Micha=B3 Kr=F3l wrote:
> Od: Brian Paul <bri...@tu...>
> Do: Micha=B3 Kr=F3l <iun...@tl...>
> Kopia do: rk...@tu..., Keith Whitwell <keith@tungstengra=
phics.com>
> Data: Thu, 12 Feb 2004 15:08:59 -0700
> Temat: Re: ARB program rev 6
>=20
> [...]
>=20
>>>Mesa doesnt support 3 or 4 extensions and they are disabled in the
>>>arbprogram.syn. I realize that they can be implemented in future
>>>revisions thats why I ask You, Brian: if the extensions mechanizm
>>>has a dynamic character or maybe static? I mean: do we know at
>>>compile-time which extension will be supported or do we know it
>>>after context initialization?
>>
>>It's dynamic.  When a device driver creates a rendering context it can=20
>>call _mesa_enable_extension() to enable the extensions that it can=20
>>implement.  Otherwise, most extensions are off by default.
>>
>=20
>=20
> Ok, so I understand that in a first call to BindProgram we can safely c=
heck which extensions are on and enable particular registers inside gramm=
ar object?
> Is there a simpler mechanism to check extension presence other than par=
sing GetString(EXTENSIONS)?

 From outside of the OpenGL API, no, that's the only mechanism.

 From inside Mesa, the ctx->Extensions.EXT_foo_bar flags indicate=20
which extensions are enabled.

-Brian