From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: buildroot@buildroot.org, eric.le.bihan.dev@free.fr,
fontaine.fabrice@gmail.com, guillaume.chaye@zeetim.com
Subject: Re: [Buildroot] [PATCH v6] package/librsvg: bump version to 2.61.1
Date: Thu, 1 Jan 2026 18:00:11 +0100 [thread overview]
Message-ID: <20260101180011.5650067c@windsurf> (raw)
In-Reply-To: <20251019064503.2583945-3-thomas@devoogdt.com>
Hello Thomas,
On Sun, 19 Oct 2025 08:45:03 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> This is a major update, which replaces autotools with meson.
> The package uses cargo in the background, so copy the relevant
> environment from the cargo package to get things working.
>
> Note that the download URL has been changed because cargo
> vendoring needs .tar.gz for it's post_process_unpack.
>
> Announcement (for what it's worth):
> - https://gitlab.gnome.org/GNOME/librsvg/-/releases/2.61.1
>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
Thanks for the patch!
> cat libgtk4.config
> BR2_PACKAGE_MESA3D=y
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SOFTPIPE=y
> BR2_PACKAGE_MESA3D_OPENGL_EGL=y
> BR2_PACKAGE_LIBGTK4=y
It's good to test large configs, but they risk bringing extra
dependencies, making you not aware of dependencies you might be missing
for librsvg.
I realized only later that this patch needs cargo-c, which isn't in
Buildroot yet. Could you make sure to always send patches with their
dependencies?
> -LIBRSVG_VERSION_MAJOR = 2.50
> -LIBRSVG_VERSION = $(LIBRSVG_VERSION_MAJOR).9
> -LIBRSVG_SITE = https://download.gnome.org/sources/librsvg/$(LIBRSVG_VERSION_MAJOR)
> -LIBRSVG_SOURCE = librsvg-$(LIBRSVG_VERSION).tar.xz
> +LIBRSVG_VERSION = 2.61.1
> +LIBRSVG_SITE = https://gitlab.gnome.org/GNOME/librsvg/-/archive/$(LIBRSVG_VERSION)
> LIBRSVG_INSTALL_STAGING = YES
> -LIBRSVG_CONF_ENV = \
> - LIBS=$(TARGET_NLS_LIBS) \
> - RUST_TARGET=$(RUSTC_TARGET_NAME)
> -LIBRSVG_CONF_OPTS = --disable-pixbuf-loader --disable-tools
> -HOST_LIBRSVG_CONF_OPTS = --enable-introspection=no
> -LIBRSVG_DEPENDENCIES = cairo host-gdk-pixbuf gdk-pixbuf host-rustc libglib2 libxml2 pango \
> - $(TARGET_NLS_DEPENDENCIES)
> -HOST_LIBRSVG_DEPENDENCIES = host-cairo host-gdk-pixbuf host-libglib2 host-libxml2 host-pango host-rustc
> LIBRSVG_LICENSE = LGPL-2.1+
> LIBRSVG_LICENSE_FILES = COPYING.LIB
> LIBRSVG_CPE_ID_VENDOR = gnome
> -# We're patching gdk-pixbuf-loader/Makefile.am
> -LIBRSVG_AUTORECONF = YES
> +
> +LIBRSVG_DOWNLOAD_POST_PROCESS = cargo
> +LIBRSVG_DL_ENV = $(PKG_CARGO_ENV)
> +
> +LIBRSVG_CONF_ENV = $(PKG_CARGO_ENV)
> +LIBRSVG_NINJA_ENV = $(PKG_CARGO_ENV)
> +LIBRSVG_CONF_OPTS = \
> + -Dtriplet=$(RUSTC_TARGET_NAME) \
> + -Drsvg-convert=disabled \
> + -Dpixbuf-loader=disabled \
> + -Ddocs=disabled \
> + -Dtests=false
> +LIBRSVG_DEPENDENCIES = \
> + host-cairo \
Are you sure host-cairo is needed?
> + host-cargo-c \
> + host-libxml2 \
And host-libxml2?
> + host-pango \
And host-pango2 ?
> + host-rustc \
> + cairo \
> + gdk-pixbuf \
According to the documentation of librsvg, gdk-pixbuf is an optional
dependency.
However, according to the documentation, freetype is mandatory. You get
it automatically as it is a dependency of cairo, but I think it would
be preferable to express this dependency here.
> + libglib2 \
> + libxml2 \
> + pango \
> + $(TARGET_NLS_DEPENDENCIES)
> +
> +HOST_LIBRSVG_CONF_ENV = $(HOST_PKG_CARGO_ENV)
> +HOST_LIBRSVG_NINJA_ENV = $(HOST_PKG_CARGO_ENV)
> +HOST_LIBRSVG_CONF_OPTS = \
> + -Dintrospection=disabled
> +HOST_LIBRSVG_DEPENDENCIES = \
> + host-cairo \
> + host-cargo-c \
> + host-gdk-pixbuf \
Maybe not needed?
Could you investigate this, and resend as part of the cargo-c series?
Thanks a lot!
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
next prev parent reply other threads:[~2026-01-01 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 8:07 [Buildroot] [PATCH v5 1/3] package/pkg-cargo: add support to bundle a custom Cargo.lock file Thomas Devoogdt
2025-09-30 8:07 ` [Buildroot] [PATCH v5 2/3] package/cargo-c: add new package Thomas Devoogdt
2025-09-30 8:07 ` [Buildroot] [PATCH v5 3/3] package/librsvg: bump version to 2.61.1 Thomas Devoogdt
2025-10-11 8:56 ` [Buildroot] [PATCH v5 1/3] package/pkg-cargo: add support to bundle a custom Cargo.lock file Thomas Devoogdt
2025-10-19 6:45 ` [Buildroot] [PATCH v6 " Thomas Devoogdt
2025-10-19 6:45 ` [Buildroot] [PATCH v6 2/3] package/cargo-c: add new package Thomas Devoogdt
2025-10-19 6:45 ` [Buildroot] [PATCH v6] package/librsvg: bump version to 2.61.1 Thomas Devoogdt
2026-01-01 17:00 ` Thomas Petazzoni via buildroot [this message]
2026-01-03 11:20 ` Thomas Devoogdt
2026-01-01 16:36 ` [Buildroot] [PATCH v6 1/3] package/pkg-cargo: add support to bundle a custom Cargo.lock file Thomas Petazzoni via buildroot
2026-02-04 14:10 ` [Buildroot] [PATCH v7 1/2] package/pkg-cargo: add support for prevendored Cargo.lock Thomas Devoogdt
2026-02-04 14:10 ` [Buildroot] [PATCH v7 2/2] package/cargo-c: add new package Thomas Devoogdt
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=20260101180011.5650067c@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=fontaine.fabrice@gmail.com \
--cc=guillaume.chaye@zeetim.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 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.