From: Eric Anholt <eric@anholt.net>
To: Keith Packard <keithp@keithp.com>, mesa-dev@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Mesa-dev] [PATCH] Don't use libudev for glx/dri3
Date: Tue, 19 Nov 2013 12:19:16 -0800 [thread overview]
Message-ID: <8738msf8l7.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <86siusnpqn.fsf@miki.keithp.com>
[-- Attachment #1.1: Type: text/plain, Size: 593 bytes --]
Keith Packard <keithp@keithp.com> writes:
> Eric Anholt <eric@anholt.net> writes:
>
>> Keith Packard <keithp@keithp.com> writes:
>>
>>> libudev doesn't have a stable API/ABI, and if the application wants to use one
>>> version, we'd best not load another into libGL.
>>>
>>> Signed-off-by: Keith Packard <keithp@keithp.com>
>>
>> This looks so simple it's definitely worth dropping udev, but I'd like
>> to see the udev code actually dropped instead of #if 0ed.
>
> It's either that or make it a config option, in case libudev is useful
> on some other system someday?
I hate build options.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2013-11-19 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 0:55 [PATCH] Don't use libudev for glx/dri3 Keith Packard
2013-11-18 1:08 ` Keith Packard
2013-11-18 1:31 ` Emil Velikov
2013-11-18 2:43 ` Keith Packard
2013-11-18 4:08 ` Kenneth Graunke
2013-11-18 6:03 ` Keith Packard
2013-11-18 21:59 ` Ian Romanick
2013-11-18 20:58 ` Emil Velikov
2013-11-19 6:46 ` Keith Packard
2013-12-14 2:33 ` Kenneth Graunke
2013-12-14 10:37 ` [Mesa-dev] " Daniel Vetter
2013-12-16 19:19 ` Eric Anholt
2013-12-16 19:57 ` [Mesa-dev] " Daniel Vetter
2013-11-19 18:41 ` Eric Anholt
2013-11-19 19:41 ` Keith Packard
2013-11-19 20:19 ` Eric Anholt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738msf8l7.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=mesa-dev@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox