On Thu, Oct 15, 2009 at 09:59:05AM -0700, Eric Anholt wrote:
> Not sure the impact on DRI ABI, but I like the idea.  In the automake
> work, I'd been thinking about conditionally compiling multiple copies of
> Mesa core with/without IN_DRI_DRIVER so that we could actually build
> more than one "driver" target at once.  Avoiding this entirely would be
> much nicer.
I have posted an RFC patch series.  It is (slightly) tested on x86 and
x86-64, with and without GLX_USE_TLS.  X server and unpatched libGL.so
seem to load the DRI drivers just fine.

A libmesa.a with remap table can be linked to by any of the drivers.
But there is an issue with libglapi.a.  When GLX_INDIRECT_RENDERING is
defined, glapitemp.h will eliminate some symbols.  It expects drivers to
provide them.  It is possible to modify gl_apitemp.py to generate the
stubs to help drivers.

-- 
Regards,
olv

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to