On 01/11/2012 04:42 PM, Chia-I Wu wrote:
On Thu, Jan 12, 2012 at 7:47 AM, Jakob Bornecrantz<wallbra...@gmail.com> wrote:
On Thu, Jan 12, 2012 at 12:37 AM, Matt Turner<matts...@gmail.com> wrote:
---
No one on IRC knows why an unshared glapi is useful.
Does anyone have a use-case for this?
If not, we can drop it to simplify automake work.
I tried searching on gmail as to why this was added, but I turned up
nothing. Maybe Chia-I Wu knows.
Shared glapi adds libglapi.so. Weird things could happen when
libGL.so and libglapi.so are from different versions of Mesa.
But it is more a problem for distros to deal with. If we all agree on
that, I am happy to see shared glapi always on.
Matt,
I'd update the commit message to mention that that libglapi.so,
libGL.so, libGLESv2.so, libGLESv1_CM.so must all come from the same
version of Mesa or bad things may happen.
Otherwise, I don't see a problem with it. Tightly-coupled versioning
between the libGL* libraries should be fine, and this doesn't affect the
loosely-coupled versioning between libGL* and the DRI drivers.
Also, I believe the shared-glapi option is necessary for apps that use
both GL and GLES. I've been building with it for some time now; I'm
pretty sure I needed it for apitracing GLES apps.
Acked-by: Kenneth Graunke <kenn...@whitecape.org>
--Kenneth
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
