Xgl page - http://www.freedesktop.org/Software/Xgl

[Michel Dänzer]

On Thu, 2005-03-10 at 05:07 -0800, Ian Romanick wrote:
> Michel Dänzer wrote:
> 
> > Ah, I was wondering why it wasn't using pbuffers... I'll look into why
> > it doesn't advertise these extensions (maybe glitz could still try to
> > use an extension if GetProcAddress succeeds for all needed functions?),
> > but I think there might be another problem in glitz as well: For direct
> > rendered contexts, shouldn't it use glXGetClientString(...,
> > GLX_EXTENSIONS) instead of glXQueryExtensionsString() (and analogously
> > for the GLX version)?
> 
> No!  glXGetClientString will list all the extensions that libGL *can* 
> support.  For direct-rendering there is still handshaking between libGL 
> and the DRI driver to determine the set of extensions to actually 
> advertise.  Using glXGetClientString for this purpose is a mistake.  For 
> most GLX extensions, like fbconfigs and pbuffers, the extension 
> functionality is used *before* you have a context (direct or otherwise), 
> so how could you even make this distinction?

So how are GLX_SGIX_fbconfig and GLX_SGIX_pbuffer supposed to be
advertised and picked up by glitz if they're only supported on the
client side?


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer