From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] meson: add entry for libgcrypt-config in cross file
Date: Wed, 3 Apr 2019 21:33:27 +0200 [thread overview]
Message-ID: <20190403213327.299f23ca@windsurf> (raw)
In-Reply-To: <20190403183202.19682-1-joerg.krause@embedded.rocks>
Hello,
On Wed, 3 Apr 2019 20:32:01 +0200
J?rg Krause <joerg.krause@embedded.rocks> wrote:
> Since version 0.49.0 the Meson build system has native support for
> looking for `libgcrypt-config` if no pkg-config file is found. As the
> latest version 1.8.4 of libgcrypt does not provide a .pc file, using
> `libgcrypt-config` is the only way for detecting the required libraries
> when linking agains libgrypt.
>
> The `libgcrypt-config` entry is necessary for updating package mpd,
> which switched from the Autotools to the Meson build system when bumping
> from version 0.20 to 0.21.
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> package/meson/cross-compilation.conf.in | 1 +
> package/meson/meson.mk | 1 +
> package/pkg-meson.mk | 1 +
> 3 files changed, 3 insertions(+)
>
> diff --git a/package/meson/cross-compilation.conf.in b/package/meson/cross-compilation.conf.in
> index fc8e27f7eb..b68499a6fa 100644
> --- a/package/meson/cross-compilation.conf.in
> +++ b/package/meson/cross-compilation.conf.in
> @@ -9,6 +9,7 @@ cpp = '@TARGET_CROSS at g++'
> ar = '@TARGET_CROSS at ar'
> strip = '@TARGET_CROSS at strip'
> pkgconfig = '@HOST_DIR@/usr/bin/pkg-config'
> +libgcrypt-config = '@STAGING_DIR@/usr/bin/libgcrypt-config'
Hm, this is a bit annoying. We really have no other solution but to
pass this through cross-compilation.conf ? It cannot be passed on the
meson command line, on a per-package basis, like we do for the autotools ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-03 19:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 18:32 [Buildroot] [PATCH 1/2] meson: add entry for libgcrypt-config in cross file Jörg Krause
2019-04-03 18:32 ` [Buildroot] [PATCH 2/2] package/mpd: bump to version 0.21.7 Jörg Krause
2019-04-03 19:33 ` Thomas Petazzoni [this message]
2019-04-05 6:58 ` [Buildroot] [PATCH 1/2] meson: add entry for libgcrypt-config in cross file Jörg Krause
2019-04-13 16:24 ` Thomas Petazzoni
2019-04-23 21:29 ` Peter Seiderer
2019-04-24 11:09 ` Jörg Krause
2019-04-30 8:11 ` Jörg Krause
2019-04-30 8:27 ` Peter Seiderer
2019-04-30 11:04 ` Jörg Krause
2019-05-01 11:13 ` Arnout Vandecappelle
2019-05-01 19:04 ` Peter Seiderer
2019-05-02 12:17 ` Arnout Vandecappelle
2019-05-02 20:02 ` Peter Seiderer
2019-05-03 9:21 ` Arnout Vandecappelle
2019-05-23 22:51 ` Jörg Krause
2019-05-24 8:18 ` Arnout Vandecappelle
2019-05-26 9:17 ` Jörg Krause
2019-05-01 19:23 ` Peter Seiderer
2019-05-01 19:36 ` Thomas Petazzoni
2019-05-02 12:20 ` Arnout Vandecappelle
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=20190403213327.299f23ca@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.