|> I've RTFM'd and FAQ'd, and I still think I'm SOL, so I'm seeking wiser counsel:
|> I am interested in using my Intel-based Windows NT machine as a display for
|> OpenGL programs running on a Silicon Graphics
|> workstation (specifically, an R4400SC-based Indy).
|> No glx extension!
|> Xlib: extension "GLX" missing on display "zuul:0.0".
|> Window type not found!
|> In a nutshell, I have some GL-based programs on the Indy which I'd rather not
|> have to rewrite in X. I was hoping that "OpenGL
|> support" in NT meant that I could use the NT box as an OpenGL server, and
|> that porting the programs from GL to OpenGL would be
|> less onerous than porting them from GL to X. Also, GL has some features
|> (overlay planes, for example) that I would have to
|> implement myself under X, and I was hoping that OpenGL would help me avoid
OpenGL on unix is normally implemented as an extension to X windows, so when
OpenGL program tries to open a window, it queries the X windows server if it has
the necessary extention. Unfortunately, none ( to my knowledge ) of the existing
X servers for Windows (NT) have that extention. That is why you get this
message. The OpenGL support in NT means that _Windows_ API gets the extention,
that is you can compile your OpenGL program under NT if you change the window
managment part of your code from x and glx calls to windows and wgl. If you are
using libaux, it's easy, but unfortunately it is rather limited library.
Otherwise - be happy that at least drawing routines stay the same :).
|> callbacks will not be fun. However, if I open an X window, can I then
|> associate an OpenGL drawing area with that window and use
|> things like overlay planes?
On OpenGL capable X server - yes, in fact you have to associate your drawing
area with an X window if you want to see the things you draw. Again, OpenGL
always draws into the window or pixmap supplied by _some_ windowing system, that
is the key to it's portability.
Hope this helps.