From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Adrian Perez de Castro <aperez@igalia.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4] package/webkitgtk: bump to 2.44.2
Date: Sat, 13 Jul 2024 00:08:32 +0200 [thread overview]
Message-ID: <20240713000832.79ccfa53@windsurf> (raw)
In-Reply-To: <20240519091604.2195932-1-thomas@devoogdt.com>
On Sun, 19 May 2024 11:16:04 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> A lot has been changed in 2.44.0, please consult the announcement [1], what's new [2],
> and the security advisory [3] for more details.
>
> Specific to this bump:
>
> - Libegl is now mandatory [4] and the USE_OPENGL_OR_ES flag has been dropped.
> While at it, also explicitly add the libepoxy dependency which is now selected
> by libgtk3.
>
> - The WPE renderer has been dropped [2], so drop the wpebackend-fdo dependency.
>
> - JPEG2000 has been dropped [2], so drop the OpenJPEG dependency.
>
> - GTK4 is now the default, so turn it off, since buildroot has no GTK4 support
> yet [2].
>
> - USE_LIBBACKTRACE has been added [5], so select it properly.
>
> - Support for ENABLE_WEB_CODECS has been added, which will now be enabled
> together with audio and video support.
>
> - ENABLE_WEBASSEMBLY is forbidden when ENABLE_C_LOOP [6], so disable it when
> compiling for MIPS r6, ARMv5, and ARMv6.
>
> In the meantime, a follow-up 2.44.1 and 2.44.2 release has been announced [7][8],
> which contains a bunch of patches that were accepted upstream. Including build
> fixes for 32-bit devices, and disabling video.
>
> [1]: https://webkitgtk.org/2024/03/16/webkitgtk2.44.0-released.html
> [2]: https://webkitgtk.org/2024/03/27/webkigit-2.44.html
> [3]: https://webkitgtk.org/security/WSA-2024-0002.html
> [4]: https://commits.webkit.org/271345@main
> [5]: https://commits.webkit.org/268579@main
> [6]: https://commits.webkit.org/271347@main
> [7]: https://webkitgtk.org/2024/04/09/webkitgtk2.44.1-released.html
> [8]: https://webkitgtk.org/2024/05/16/webkitgtk2.44.2-released.html
>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
> ---
> v2: update patches with the upstream reference
> v3: bump to 2.44.1 and drop the upstreamed patches
> v4: bump to 2.44.2 and move xlib_libxshmfence to a separate patch series
> ---
> ...velInterpreter.cpp-339-21-error-t6-w.patch | 39 ---------------
> package/webkitgtk/Config.in | 4 +-
> package/webkitgtk/webkitgtk.hash | 6 +--
> package/webkitgtk/webkitgtk.mk | 50 ++++++++-----------
> 4 files changed, 26 insertions(+), 73 deletions(-)
> delete mode 100644 package/webkitgtk/0001-GTK-2.42.5-LowLevelInterpreter.cpp-339-21-error-t6-w.patch
Applied to master, thanks.
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:[~2024-07-12 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 9:16 [Buildroot] [PATCH v4] package/webkitgtk: bump to 2.44.2 Thomas Devoogdt
2024-05-22 11:11 ` Adrian Perez de Castro
2024-07-12 22:08 ` Thomas Petazzoni via buildroot [this message]
2024-08-08 21:29 ` Peter Korsgaard
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=20240713000832.79ccfa53@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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