From: Adrian Perez de Castro <aperez@igalia.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
Romain Naour <romain.naour@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/mesa3d: add EGL_WL_bind_wayland_display support
Date: Mon, 23 Feb 2026 15:12:30 +0200 [thread overview]
Message-ID: <20260223151230.GD2359969@igalia.com> (raw)
In-Reply-To: <20260218063123.546067-1-james.hilliard1@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1766 bytes --]
On Tue, 17 Feb 2026 23:31:22 -0700 James Hilliard <james.hilliard1@gmail.com> wrote:
> This feature was made optional in mesa3d 25.2.0 as it is deprecated,
> however some packages still require it so lets add a new config
> option that those packages can select until they no longer require
> this feature.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Reviewed-by: Adrian Perez de Castro <aperez@igalia.com>
> ---
> package/mesa3d/Config.in | 6 ++++++
> package/mesa3d/mesa3d.mk | 3 +++
> 2 files changed, 9 insertions(+)
>
> diff --git a/package/mesa3d/Config.in b/package/mesa3d/Config.in
> index e1faea95d5..8a7811b6a5 100644
> --- a/package/mesa3d/Config.in
> +++ b/package/mesa3d/Config.in
> @@ -50,6 +50,12 @@ comment "llvm support needs a toolchain not affected by GCC bug 64735"
> depends on BR2_PACKAGE_LLVM_ARCH_SUPPORTS
> depends on BR2_TOOLCHAIN_HAS_GCC_BUG_64735
>
> +config BR2_PACKAGE_MESA3D_LEGACY_BIND_WAYLAND_DISPLAY
> + bool "Legacy Wayland EGL_WL_bind_wayland_display support"
> + depends on BR2_PACKAGE_WAYLAND
> + help
> + Legacy Wayland EGL_WL_bind_wayland_display support.
> +
> menuconfig BR2_PACKAGE_MESA3D_OPENCL
> bool "OpenCL support"
> depends on BR2_PACKAGE_MESA3D_LLVM
> diff --git a/package/mesa3d/mesa3d.mk b/package/mesa3d/mesa3d.mk
> index 42693ce928..9c0e5d7256 100644
> --- a/package/mesa3d/mesa3d.mk
> +++ b/package/mesa3d/mesa3d.mk
> @@ -209,6 +209,9 @@ endif
> ifeq ($(BR2_PACKAGE_WAYLAND),y)
> MESA3D_DEPENDENCIES += wayland wayland-protocols
> MESA3D_PLATFORMS += wayland
> +ifeq ($(BR2_PACKAGE_MESA3D_LEGACY_BIND_WAYLAND_DISPLAY),y)
> +MESA3D_CONF_OPTS += -Dlegacy-wayland=bind-wayland-display
> +endif
> endif
>
> MESA3D_CONF_OPTS += \
> --
> 2.43.0
>
>
Cheers,
—Adrián
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-23 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 6:31 [Buildroot] [PATCH 1/2] package/mesa3d: add EGL_WL_bind_wayland_display support James Hilliard
2026-02-18 6:31 ` [Buildroot] [PATCH 2/2] package/wpebackend-fdo: fix EGL_NOT_INITIALIZED crash James Hilliard
2026-02-23 13:13 ` Adrian Perez de Castro
2026-03-17 22:04 ` Romain Naour via buildroot
2026-03-27 10:03 ` Thomas Perale via buildroot
2026-02-23 13:12 ` Adrian Perez de Castro [this message]
2026-03-27 10:03 ` [Buildroot] [PATCH 1/2] package/mesa3d: add EGL_WL_bind_wayland_display support Thomas Perale via buildroot
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=20260223151230.GD2359969@igalia.com \
--to=aperez@igalia.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=romain.naour@gmail.com \
/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