Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/libegl: add option for wayland extensions
Date: Tue, 23 Aug 2016 22:02:45 +0200	[thread overview]
Message-ID: <20160823220245.49e1b6e7@free-electrons.com> (raw)
In-Reply-To: <6d4c564432948310ca9502dc94c2d50a7c97f460.1471968455.git.yann.morin.1998@free.fr>

Hello,

On Tue, 23 Aug 2016 18:26:32 +0200, Yann E. MORIN wrote:
> Wayland requires that an OpenGL/EGL implementation provides a few
> extensions, so that wayland servers and clients can exchange buffers.
> 
> Currently, only one OpenGL/EGL implementation provides those extensions:
> mesa3d.
> 
> However, other implementations are catching up, especially the
> proprietary NVidia driver, which has as of late introduced those
> extensions. Other, non-public implementations may also provide those
> extensions.
> 
> A lot of wayland-related packages require those extensions, and
> currently they have to depend on mesa3d to provide OpenGL/EGL, which
> precludes using those packages when a non-mesa3d provider is enabled,
> even when that providers implements the necessary extensions.
> 
> Add an option to the libegl virtual package, that providers on
> OpenGL/EGL can select to state they provide those extensions.
> 
> Pacakges that need those extensions can additionally depend on this new
> option, instead of the existing libegl package.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
>  package/opengl/libegl/Config.in | 4 ++++
>  1 file changed, 4 insertions(+)

Applied to next, thanks.

One thing that surprises me though is that weston itself doesn't use
this new option, and still has:

config BR2_PACKAGE_WESTON_DRM
        bool "DRM compositor"
        depends on BR2_PACKAGE_MESA3D_OPENGL_EGL
        select BR2_PACKAGE_LIBDRM
        select BR2_PACKAGE_WESTON_HAS_COMPOSITOR

# Uses libgbm from mesa3d
comment "DRM compositor needs an OpenGL EGL backend provided by mesa3d"
        depends on !BR2_PACKAGE_MESA3D_OPENGL_EGL

So it's weird to have a new OpenGL implementation that is said to be
Wayland capable, but doesn't allow to build the reference Wayland
implementation.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-08-23 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 16:26 [Buildroot] [PATCH 0/4] package/libegl: introduce egl-wayland (branch yem/egl-wayland) Yann E. MORIN
2016-08-23 16:26 ` [Buildroot] [PATCH 1/4] package/libegl: add option for wayland extensions Yann E. MORIN
2016-08-23 20:02   ` Thomas Petazzoni [this message]
2016-08-23 21:43     ` Yann E. MORIN
2016-08-23 21:58       ` Thomas Petazzoni
2016-08-23 22:06         ` Yann E. MORIN
2016-08-24 17:11           ` Thomas Petazzoni
2016-08-23 16:26 ` [Buildroot] [PATCH 2/4] package/mesa3d: also implements the EGL " Yann E. MORIN
2016-08-23 20:02   ` Thomas Petazzoni
2016-08-23 16:26 ` [Buildroot] [PATCH 3/4] package/libgtk3: needs OpenGL-EGL/wayland Yann E. MORIN
2016-08-23 20:02   ` Thomas Petazzoni
2016-08-23 16:26 ` [Buildroot] [PATCH 4/4] package/nvidia-driver: update version Yann E. MORIN
2016-09-20 19:17   ` Thomas Petazzoni

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=20160823220245.49e1b6e7@free-electrons.com \
    --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