All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/5] mesa3d: pull out from x11
Date: Wed, 12 Mar 2014 07:24:14 +0100	[thread overview]
Message-ID: <531FFD8E.8010209@mind.be> (raw)
In-Reply-To: <20140310184119.GC3282@free.fr>

On 03/10/14 19:41, Yann E. MORIN wrote:
>> > 1. As Mesa3D is an implementation of OpenGL, it will be a provider for the
>> >    virtual packages libegl, libgles and libopenvg.
> I've looked on my distro, and mesa3d does not provide any file named
> libegl*.so or ligles*.so or libopenvg*.so. So I don't think it should
> be, *as is*, a provider for libegl, libgles or libopenvg.

 Have you looked at libegl1-mesa, libgles2-mesa, libopenvg1-mesa?

> 
>> > 2. Mesa3D also provides libgl, but:
> libgl or libglx ?
> 
> On my distro (Ubuntu 13.10), there's no libgl.so, only libglx.so which
> is provided by a bumch of different packages, of which the nvidia blobs.

 That one is in libgl1-mesa-glx.

 All that stuff is only installed if you need it - which you usually
don't because glx is enough for desktop use.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-03-12  6:24 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
2014-03-10 18:41     ` Yann E. MORIN
2014-03-12  6:24       ` Arnout Vandecappelle [this message]
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=531FFD8E.8010209@mind.be \
    --to=arnout@mind.be \
    --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.