From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] librsvg: bump to version 2.42.5
Date: Thu, 7 Jun 2018 07:58:42 +0200 [thread overview]
Message-ID: <20180607075842.1c92eba9@windsurf> (raw)
In-Reply-To: <20180606202501.14535-2-fontaine.fabrice@gmail.com>
Hello,
On Wed, 6 Jun 2018 22:25:01 +0200, Fabrice Fontaine wrote:
> - Add a dependency to host-cargo
> - Add a patch to set RUST_TARGET
> - Add a dependency to BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS
> - Forward this dependency to efl svg and enlightment
> - Add hash for license file
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
As I was surprised by the new rust dependency, I looked at
https://github.com/GNOME/librsvg/blob/master/COMPILING.md. Indeed, Rust
appears to be necessary.
But the other thing that came up from this reading is:
Mandatory dependencies
[...]
GObject-Introspection 0.10.8
But we don't have gobject-introspection in Buildroot, the package for
that is pending review, and it's a complicated one. How is it possible
that you built librsvg without it ? Is the documentation incorrect and
in fact it's an optional dependency ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-07 5:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 20:25 [Buildroot] [PATCH 1/2] host-cargo: select host-rustc Fabrice Fontaine
2018-06-06 20:25 ` [Buildroot] [PATCH 2/2] librsvg: bump to version 2.42.5 Fabrice Fontaine
2018-06-07 2:39 ` Baruch Siach
2018-06-07 5:58 ` Thomas Petazzoni [this message]
2018-06-07 17:26 ` Fabrice Fontaine
2018-06-07 16:02 ` [Buildroot] [PATCH 1/2] host-cargo: select host-rustc Thomas Petazzoni
2018-06-07 17:25 ` Fabrice Fontaine
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=20180607075842.1c92eba9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.