All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/6] libdrm: Remove xorg dependency for intel driver
Date: Wed, 12 Mar 2014 03:14:53 -0400	[thread overview]
Message-ID: <5320096D.1020900@savoirfairelinux.com> (raw)
In-Reply-To: <lo95vax104.ln2@ID-313208.user.individual.net>

Hi bernd,

On 03/12/2014 02:00 AM, Bernd Kuhls wrote:
> Bernd Kuhls <berndkuhls@hotmail.com> wrote in
> news:3p65vaxf8m.ln2 at ID-313208.user.individual.net: 
>
>> xlib_pciaccess itself does not depend on xorg stuff, I was able to
>> compile the libdrm intel driver with patch v5 without activating xorg7.
As far as i understand, the package XORG7 is a kind of a container which
doesn't compile anything, it only adds global toolchain dependencies for
all the xorg stuff.
Did you try to build the xlib_libpciaccess with a toolchain without this
options ?

> PS: Should we also move libpciaccess out of the xorg section?
I dont think so, even if the libpciaccess is a generic PCI access
library, it come as a part of the Xorg project and perhaps there is
other xlib that doesn't require the toolchain options above so should we
move them too ?
An other option could be to don't set dependencies on the XORG7 package
and move the dependencies inside each sub-packages.

  reply	other threads:[~2014-03-12  7:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 18:53 [Buildroot] [PATCH v5 1/6] libdrm: Remove xorg dependency for intel driver Bernd Kuhls
2014-03-11 21:50 ` Sebastien Bourdelin
2014-03-12  5:09   ` Bernd Kuhls
2014-03-12  6:00     ` Bernd Kuhls
2014-03-12  7:14       ` Sebastien Bourdelin [this message]
2014-03-12 19:24         ` Bernd Kuhls

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=5320096D.1020900@savoirfairelinux.com \
    --to=sebastien.bourdelin@savoirfairelinux.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.