Re: [gut-users] Help with GL setup API?
Status: Alpha
Brought to you by:
jason379
|
From: J. P. <ja...@37...> - 2000-08-09 12:02:17
|
Pierre Phaneuf wrote: > I tried it, but it is linked statically with libMesaGL.so.3 and > libMesaGLU.so.3, which is Wrong. I have libGL.so.1 and libGLU.1. If it > pretends to be able to select an OpenGL driver at run type, I would have > expected it *not* to be linked against *any* OpenGL driver, loading them > with dlopen() instead, no? Ah, thanks for letting me know about this Pierre. I was in a rush to get that demo online so I built it on my laptop, which at the time was still running Mesa 3.0 -- before they changed to the new library name standards. I usually build on my desktop machine, which is up to date. Right now, only the Win32 client links OpenGL dynamically. I don't do it on the X client for two reasons: a) there's really no point that I can see, since "libGL.so" has become a standard, b) I couldn't make it work. Here's what would happen: 1) at startup I load libGL.so and libGLU.so 2) I make a bunch of gl...() calls, everything works fine 3) I try to call a glu...() function, say gluPerspective() 4) gluPerspective() tries to call glFrustum() and then 5) segfault...core dump... It appeared that the linker was not properly putting gl() and glu() together. I posted some messages around USENET with no response, and then I figured I'd yank it because of (a), above. Anyway, that's the long answer. I promise never to build against an old version of Mesa again. If you build from the sources you should be okay. Jason 379 |