----- Original Message ----- > On 26.03.2012 14:56, Jose Fonseca wrote: > > This doesn't look like a "winsys" per se, but rather an auxiliary > > library to create winsys and screens, meant to be used by state > > trackers. Is this right? > > > > If so then I believe the right place would be somewhere > > src/gallium/auxiliary . > > > > Jose > The same is true for winsys/g3dvl, and I'm planning to move it under > auxiliary for quite some time, but unfortunately it has a dependency > on > X libs, and well something like this is a bit sensitive to put under > auxiliary. The same might be true for this winsys loader.
I see. We could put this kind of modules in src/gallium/auxiliary/foo , but provide them as separate convenient libraries (i.e., libfoo.a, which are only built/linked as appropriate), as opposed to be bundled into libgallium.a (which should retain only cross-platform portable code). I think it would still be less confusing than having auxiliary libraries that are not winsys in src/gallium/winsys . Jose _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
