[Mesa-dev] [PATCH 0/3] Only require libdrm if direct rendering is actually enabled

Dan Nicholson dbn.lists at gmail.com
Tue Mar 15 08:30:47 PDT 2011

On Mon, Mar 14, 2011 at 5:23 PM, Brian Paul <brian.e.paul at gmail.com> wrote:
> On Mon, Mar 14, 2011 at 4:03 PM, Jon TURNEY <jon.turney at dronecode.org.uk> wrote:
>> On 16/02/2011 15:44, Julien Cristau wrote:
>>> On Wed, Feb 16, 2011 at 15:11:34 +0000, Jon TURNEY wrote:
>>>> At the moment, libGL cannot be built --with-driver=dri --disable-driglx-direct
>>>> on platforms which don't have libdrm.
>>>> --with-driver=dri is the only way to build a libGL which supports indirect
>>>> rendering.
>>>> This patch set makes libdrm only required if --enable-driglx-direct is used,
>>>> and makes --disable-driglx-direct the default on cygwin and hurd.
>>>> (this patch set combines patches from fd.o bugs #27840 and #29460, updated for
>>>> the current git master)
>>>> Jon TURNEY (1):
>>>>   Disable direct rendering on Cygwin
>>>> Samuel Thibault (1):
>>>>   Only require libdrm if direct rendering is actually enabled.
>>>> nobled (1):
>>>>   Disable direct rendering on GNU/Hurd
>>> For the series:
>>> Reviewed-by: Julien Cristau <jcristau at debian.org>
>> Thanks, updated patches with tag added to follow.
>> Can I apply for mesa commit access, since no-one seems to be particularly
>> interested in picking up my patches?
> Sure, there's instructions on the website.
> I'll commit these tomorrow if there's no objection.  They look OK to
> me but I'm not an autoconf expert.

Yeah, sorry to Jon. I always mean to review these patches, but too
much life always gets in the way. Jon has done a ton of fixes from
building X on cygwin and definitely gets my backing for committing


More information about the mesa-dev mailing list