From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: Paul Cercueil <paul@crapouillou.net>,
Raphael Pavlidis <raphael.pavlidis@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/wlroots: bump to version 0.16.2
Date: Wed, 1 Nov 2023 12:03:24 +0100 [thread overview]
Message-ID: <20231101120324.23133401@windsurf> (raw)
In-Reply-To: <20231030101115.2214402-2-aperez@igalia.com>
Hello,
+Waldemar as there is a uClibc-specific issue below. Also adding Paul
Cercueil who originally wrote the patch.
On Mon, 30 Oct 2023 12:11:05 +0200
Adrian Perez de Castro <aperez@igalia.com> wrote:
> Update to version 0.16.2, which brings in support for a few new Wayland
> protocols, and improved input device and scene graph APIs. Applications
> which use wlroots might need to be adapted, and at least rebuilt. The
> only packages in Buildroot which use wlroots at the moment are the Cage
> and Sway compositors, to be updated in follow-up patches.
>
> Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> ---
> package/wlroots/wlroots.hash | 4 ++--
> package/wlroots/wlroots.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
I have applied to master. However, the patch
package/wlroots/0001-Add-feature-macros-to-more-C-files-.patch is a bit
annoying because it has been rejected upstream.
The patch currently points to
https://github.com/swaywm/wlroots/pull/2493 which in fact has been
migrated to
https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/2493.
And this concludes with "Closing because we don't want these
workarounds upstream.".
So I think we should either find a better solution to this issue, or
drop the patch and make wlroots unavailable with uClibc.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-01 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 10:11 [Buildroot] [PATCH 0/3] Update wlroots to 0.16.x and dependent packages Adrian Perez de Castro
2023-10-30 10:11 ` [Buildroot] [PATCH 1/3] package/wlroots: bump to version 0.16.2 Adrian Perez de Castro
2023-11-01 11:03 ` Thomas Petazzoni via buildroot [this message]
2023-10-30 10:11 ` [Buildroot] [PATCH 2/3] package/cage: bump to version 0.1.5 Adrian Perez de Castro
2023-11-01 11:03 ` Thomas Petazzoni via buildroot
2023-10-30 10:11 ` [Buildroot] [PATCH 3/3] package/sway: bump to version 1.8.1 Adrian Perez de Castro
2023-11-01 11:03 ` Thomas Petazzoni 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=20231101120324.23133401@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=paul@crapouillou.net \
--cc=raphael.pavlidis@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.