From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexander Bau <dev@abau.org>
Cc: Michael Fischer <mf@go-sys.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/sdl2: support building for Wayland
Date: Sat, 29 Jul 2023 22:50:08 +0200 [thread overview]
Message-ID: <20230729225008.131ad59a@windsurf> (raw)
In-Reply-To: <20230522101438.1026434-1-dev@abau.org>
Hello Alexander,
Thanks for your patch, and sorry for the long delay in providing this
review. See below some comments.
On Mon, 22 May 2023 12:14:37 +0200
Alexander Bau <dev@abau.org> wrote:
Your commit log needs to have a Signed-off-by line with your name and
e-mail. And if needed some extra explanation about the change.
> ---
> package/sdl2/Config.in | 7 +++++++
> package/sdl2/sdl2.mk | 7 ++++++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/package/sdl2/Config.in b/package/sdl2/Config.in
> index 7c8258fe73..85d7c09385 100644
> --- a/package/sdl2/Config.in
> +++ b/package/sdl2/Config.in
> @@ -29,6 +29,13 @@ comment "X11 video driver needs X.org"
> depends on !BR2_PACKAGE_XORG7
> depends on BR2_USE_MMU
>
> +config BR2_PACKAGE_SDL2_WAYLAND
> + bool "Wayland video driver"
> + depends on BR2_PACKAGE_WAYLAND
> + depends on BR2_PACKAGE_HAS_LIBEGL
> + depends on BR2_PACKAGE_SDL2_OPENGLES
> + depends on BR2_PACKAGE_LIBXKBCOMMON
I don't think we want to use "depends on" for all those dependencies. I
think we probably want something like this:
depends on BR2_PACKAGE_WAYLAND
depends on BR2_PACKAGE_HAS_LIBEGL
depends on BR2_PACKAGE_HAS_LIBGLES
select BR2_PACKAGE_SDL2_OPENGLES
select BR2_PACKAGE_LIBXKBCOMMON
with also:
comment "wayland video driver needs Wayland, OpenGLES+EGL"
depends on !BR2_PACKAGE_WAYLAND || !BR2_PACKAGE_HAS_LIBEGL || !BR2_PACKAGE_HAS_LIBGLES
> +ifeq ($(BR2_PACKAGE_SDL2_WAYLAND),y)
> +SDL2_CONF_OPTS += --enable-video-wayland
No build dependencies? This looks odd. I'm pretty you need to depend on
host-pkgconf (for pkg-config), on wayland, and libxkbcommon.
Could you have a look at those comments and if possible, send an
updated version that takes them into account?
See
https://buildroot.org/downloads/manual/manual.html#submitting-patches
for some guidelines on submitting patches if needed.
Thanks a lot for your contribution!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-29 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 10:14 [Buildroot] [PATCH] package/sdl2: support building for Wayland Alexander Bau
2023-07-29 20:50 ` Thomas Petazzoni via buildroot [this message]
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=20230729225008.131ad59a@windsurf \
--to=buildroot@buildroot.org \
--cc=dev@abau.org \
--cc=mf@go-sys.de \
--cc=thomas.petazzoni@bootlin.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