From: Alexandre Demers <alexandre.f.demers@gmail.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Why does libdrm-intel needs libpciaccess?
Date: Wed, 03 Aug 2011 12:31:44 -0400 [thread overview]
Message-ID: <4E3977F0.9090102@gmail.com> (raw)
Here is a simple question I couldn't find an answer for: why does
libdrm-intel needs libpciaccess to be build? It is the only drm driver
requiering it.
>From what I understand, and correct me if I'm wrong, but libpciaccess is
related to X. And drm should be able to live without X. So why would
libdrm-intel rely on libpciaccess/X to be build? I'm sure we could do
without it, since all other drivers do.
As things are right now, would that imply using a X lib to build
libdrm-intel and then use it with Wayland for instance? Isn't Wayland
supposed to be able to run completly without X?
Cheers,
--
Alexandre Demers
next reply other threads:[~2011-08-03 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 16:31 Alexandre Demers [this message]
2011-08-03 16:55 ` Why does libdrm-intel needs libpciaccess? Alan Coopersmith
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=4E3977F0.9090102@gmail.com \
--to=alexandre.f.demers@gmail.com \
--cc=dri-devel@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