From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/91] Update mesa3d & xorg
Date: Sun, 30 Mar 2014 11:13:50 +0200 [thread overview]
Message-ID: <20140330111350.4782647c@skate> (raw)
In-Reply-To: <20140329231259.GO3227@free.fr>
Dear Yann E. MORIN,
On Sun, 30 Mar 2014 00:12:59 +0100, Yann E. MORIN wrote:
> The problem seems related to libevas, where the dependency on openGL is
> poorly handled.
>
> I'm working on it, but you are free to investigate too. ;-)
>
> So far, I managed to get rid of the circular hell, with this:
>
> diff --git a/package/efl/libevas/Config.in b/package/efl/libevas/Config.in
> index 2afa888..8eea23d 100644
> --- a/package/efl/libevas/Config.in
> +++ b/package/efl/libevas/Config.in
> @@ -148,7 +148,7 @@ choice
> config BR2_PACKAGE_LIBEVAS_GL
> bool "generic OpenGL"
> - select BR2_PACKAGE_MESA3D
> + depends on BR2_PACKAGE_MESA3D
> select BR2_PACKAGE_LIBEET
But shouldn't BR2_PACKAGE_LIBEVAS_GL instead depend on a new virtual
package for full OpenGL? We can imagine having in the future other
implementations that Mesa3D for the full OpenGL, no? Like if you
install the NVidia proprietary drivers, I believe they come with their
own implementation of OpenGL, completely independent from Mesa3D, no?
In this case, since we can "select" a virtual package because that
doesn't make sense, the dependency would have to be a "depends on", and
we're good, no?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-30 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 20:56 [Buildroot] [PATCH 00/91] Update mesa3d & xorg Bernd Kuhls
2014-03-29 21:30 ` Bernd Kuhls
2014-03-29 21:53 ` Bernd Kuhls
2014-03-29 22:24 ` Thomas Petazzoni
2014-03-29 22:50 ` Thomas Petazzoni
2014-03-29 23:12 ` Yann E. MORIN
2014-03-30 9:13 ` Thomas Petazzoni [this message]
2014-03-30 10:21 ` Yann E. MORIN
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=20140330111350.4782647c@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox