-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kristian Høgsberg wrote:
> Ok, big disclaimer here: I haven't looked into glucose or even glitz > much, so what I'm suggesting here may not apply. But my take is that > we shouldn't be loading libGL in the X server to begin with. If we > want to use opengl in the X server we should call into the dispatch > table directly (as for example the __glXDRIbindTexImage implementation > in GL/glx/glxdri.c: > > CALL_GetIntegerv(GET_DISPATCH(), (glxPixmap->target == GL_TEXTURE_2D ? > GL_TEXTURE_BINDING_2D : > GL_TEXTURE_BINDING_RECTANGLE_NV, > &texname)); I think that's correct. Alternately (preferably?) we could generate a fake libGL or gl_calls.h or something so that we can do glGetIntegerv(...) and have it be expanded directly to the above for us. We shouldn't link libGL with the X server any more than we'd link Xlib with it. > and we may have to export some of the GLX code for use inside the X > server (creating glx drawables and contexts etc) and separate out the > protocol stuff. Basically if we have to hack around linking issues > and fudge symbol resolution issues we're doing something wrong. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFG+v30X1gOwKyEAw8RAqSkAJ9weVM3XSBzC5bL84xVwJ9D5KtkXgCdEfgm BRH8+WHsAB1oRAwbW7JgTC0= =59EP -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
