On 19/06/15 22:00, Eric Anholt wrote: > Emil Velikov <emil.l.veli...@gmail.com> writes: >> Signed-off-by: Emil Velikov <emil.l.veli...@gmail.com> > > s/confiigure/configure/ in the subject. > Will fix.
> After that, and some cleanup of the commit message in 4, patches 1-8 > will be: > > Reviewed-by: Eric Anholt <e...@anholt.net> > Thanks. > I find 9/10 weird -- if the DRI drivers need libglapi, why aren't they > just linking libglapi? > Short version - currently they don't because of hysterical raisins, once we move to shared-glapi only libGL we'll add the link. Long version - the dri modules require glapi provider. Which could be either one of: 1) the xserver glapi (no longer there since ~1.14) 2) libGL with static glapi 3) the shared glapi Thanks to some interesting overlinking of libgbm, which itself has propagated to libEGL, people won't notice the issue if they're not using 1) or 2). So people working directly with EGL/gbm (wayland/weston folk, everyone writing their wayland compositor, Google with their gbm work) has noticed those and had the same workaround for a while. While most of us working with X and/or GLX did not see it. This of course is prominent, (only?) when using dlopen(libgbm/libEGL), rather than linking against them. When 1) and 2) are gone (second is on it's way out), we can add the link to the dri modules. Although neither helps in the case of "using old dri module with new loader", thus the need for the explicit dlopen(). Thanks Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
