2010/2/8 Kristian Høgsberg <k...@bitplanet.net>: > 2010/2/6 Chia-I Wu <olva...@gmail.com>: >> >> We can then build libGL.so with or without libglx.a depending on the >> configure optins. Later, src/mesa/drivers/x11/ could be changed to >> build libglxsw.a. We will be able to choose between 3 flavors of >> libGL.so, or choose all of them (to catch build failure) > > I wanted to do something similar, but the problem is: where do you > build libGL? And glx is part of libGL so it's consistent to call the > directory src/gl. And I don't think it's worth the effort to make it > possible to plug in different glx implementations, we already have the > dri sw driver as well as server side sw fallback for glx. >
What about the following: when --disable-glx is defined do not visit src/glx at all and build libGL alongside libEGL (from within src/egl/main ?). The above is consistent with the mesa pattern of building glapi and then using it from each window system subdir/driver, and probably causes less churn than the current patch. Multiple libGL's probably requires building from src/mesa/glapi but that's probably predicated on cleaning the code generation stuff. I think the above cuts it for now. And please leave GLX code under src/glx. regards, George. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
