[Xquartz-dev] GLX updates on 2.3.2_rc2

ryan woodsmall rwoodsmall at mac.com
Sun Nov 30 12:35:21 PST 2008


Jeremy, George, et al:

Thanks so much for your work on X11 under Leopard!  I do a lot of SSH- 
tunneled X forwarding from Linux servers to my MacBook at my job, and  
your work has made X not only more stable, but a treat to use.  Kudos.

As far as "play" goes, I'm attempting to make open source Wine work  
with straight X11, including OpenGL/Direct3D support.  Wine itself  
works great for running the few Windows apps I need that have no Mac/ 
Linux counterparts, but I'm still running into some problems - likely  
known - with Wine running games.  This issue was marked fixed with the  
recent 2.3.2_rc2 release:

   http://xquartz.macosforge.org/trac/ticket/122

I can indeed see the GLX_SGIX_fbconfig extension, but it fails to  
initialize automatically in Wine.  When forcing Wine to use the  
GLX_SGIX_fbconfig path by #ifdef'ing a section of source in the X11  
OpenGL driver, there's still a crash when initializing a Wine client  
like, say, Steam to run a Direct3D game.  I'd bet this is related to  
the following open issues, but I could be completely wrong:

   http://xquartz.macosforge.org/trac/ticket/135
   http://xquartz.macosforge.org/trac/ticket/140
   http://xquartz.macosforge.org/trac/ticket/196

Using a Wine-ified version of the realtech Windows OpenGL Extensions  
viewer doesn't cause a full crash of the process, but the program warn  
of attempting to read from an unknown part of memory address. This  
looks to be an attempt to use a function pointer to a GL/GLX function  
that's not present.

As always, debugging Wine is something of a nightmare - there are so  
many jumps to different areas that it's hard to even track exactly  
where in the code the crash is occurring.  I have some experience with  
C and OpenGL, but little with direct X or GLX coding, so I'm grasping  
a bit to understand everything here.  Before digging too deep for my  
own good in Wine, should I expect most GLX stuff to "just work" at  
this point, or is this an exercise in futility until the  
OpenGL.framework DRI work is done?  As this is mostly for games, and  
nothing in my day-to-day work requires any OpenGL/Direct3D Windows  
apps, even a recommendation of just wait for the DRI framework would  
suffice, though any advice would be greatly appreciated.

Thanks again!

   ryan woodsmall
     rwoodsmall at mac.com


"Be well, do good work, and keep in touch." - Garrison Keillor






More information about the Xquartz-dev mailing list