From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/4] mesa3d: modularize and bump to version 10.0.3
Date: Sun, 9 Mar 2014 16:32:34 +0100 [thread overview]
Message-ID: <20140309163234.275df357@skate> (raw)
In-Reply-To: <gt2suaxvbl.ln2@ID-313208.user.individual.net>
Dear Bernd Kuhls,
On Sat, 08 Mar 2014 19:08:16 +0100, Bernd Kuhls wrote:
> > In your Config.in, you have a dependency from EGL/OpenVG on udev, but
> > it isn't reflected here. Which one is correct?
>
> Hi,
>
> OpenVG depends on EGL (--enable-egl):
> "configure: error: cannot enable OpenVG without EGL"
>
> EGL depends on gallium support (--enable-gallium-egl):
> "configure: error: cannot enable OpenVG without egl_gallium"
>
> The EGL drm module depends on gbm:
> "configure: error: EGL platform drm needs gbm"
>
> gbm depends on udev:
> "error: gbm needs udev"
Ah, ok!
> This dependency chain is present in Config.in, should this also be present
> in the mesa3d.mk-sections mentioned above? Is
>
> ifeq ($(BR2_PACKAGE_MESA3D_GBM),y)
> MESA3D_DEPENDENCIES += udev
>
> not enough?
No, as long as the Config.in "select" ensure that
BR2_PACKAGE_MESA3D_GBM is selected in the appropriate cases, then it's
fine.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-09 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394285816-7111-1-git-send-email-berndkuhls@hotmail.com>
2014-03-08 13:36 ` [Buildroot] [PATCH v3 2/4] mesa3d: modularize and bump to version 10.0.3 Bernd Kuhls
2014-03-08 14:21 ` Thomas Petazzoni
2014-03-08 18:08 ` Bernd Kuhls
2014-03-09 15:32 ` Thomas Petazzoni [this message]
2014-03-08 13:36 ` [Buildroot] [PATCH v3 3/4] xorg: Bump xserver_xorg-server version to 1.15.0 Bernd Kuhls
2014-03-08 13:36 ` [Buildroot] [PATCH v3 4/4] xdriver_xf86-video-intel: Bump version to 2.99.910 Bernd Kuhls
2014-03-08 13:36 ` 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=20140309163234.275df357@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