All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/5] mesa3d: pull out from x11
Date: Mon, 10 Mar 2014 19:20:32 +0100	[thread overview]
Message-ID: <20140310182030.GB18832@pc-eric> (raw)
In-Reply-To: <20140310173941.GA3282@free.fr>

Yann E., All
On Mon, Mar 10, 2014 at 06:39:41PM +0100, Yann E. MORIN wrote:

> > diff --git a/package/Config.in b/package/Config.in
> > index 70e5a7f..b0da653 100644
> > --- a/package/Config.in
> > +++ b/package/Config.in
> > @@ -188,6 +188,7 @@ source "package/fbv/Config.in"
> >  source "package/imagemagick/Config.in"
> >  source "package/linux-fusion/Config.in"
> >  source "package/lite/Config.in"
> > +source "package/mesa3d/Config.in"
>
> If I understand correctly, mesa3d is an implementation of OpenGL. So,
> *maybe* it would make sense to move it along the other OpenGL packages,
> into package/opengl/.
Some quick thoughts:

1. As Mesa3D is an implementation of OpenGL, it will be a provider for the
   virtual packages libegl, libgles and libopenvg.

2. Mesa3D also provides libgl, but:

  - no package in Buildroot requires full OpenGL.
  - Buildroot is unlikely to include packages for AMD/NVidia/Intel drivers
    (providers for libgl).

  So there is no need for a libgl virtual package.

3. IMHO package/opengl should only contain the definitions of the virtual
   packages, not the providers (otherwise sunxi-mali should be moved to
   package/opengl too!).

Best regards,
ELB

  parent reply	other threads:[~2014-03-10 18:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09 19:01 [Buildroot] [PATCH v4 1/5] mesa3d: pull out from x11 Bernd Kuhls
2014-03-10 16:21 ` Sebastien Bourdelin
2014-03-10 17:39 ` Yann E. MORIN
2014-03-10 17:52   ` Bernd Kuhls
2014-03-10 18:05     ` Yann E. MORIN
2014-03-10 18:20   ` Eric Le Bihan [this message]
2014-03-10 18:41     ` Yann E. MORIN
2014-03-12  6:24       ` Arnout Vandecappelle
2014-03-12 17:31         ` Yann E. MORIN
2014-03-10 18:58     ` 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=20140310182030.GB18832@pc-eric \
    --to=eric.le.bihan.dev@free.fr \
    --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.