From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] core/pkg-meson: allow packages to add extra [binaries]
Date: Sat, 5 Oct 2019 22:33:03 +0200 [thread overview]
Message-ID: <20191005223303.0c35239a@windsurf> (raw)
In-Reply-To: <be7aee4db475150e52b2c7a36979c89537d79a86.1569701061.git.yann.morin.1998@free.fr>
On Sat, 28 Sep 2019 22:04:30 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> meson does not allow passing path to helper programs (e.g. pkgconfig)
> using variables in the environment. Instead, it insists that those paths
> be defined in the cross-compilation.conf file, in the [binaries]
> section [0]
>
> As such, allow packages to declare such a list of arbitrary entries to
> add in the [binaries] section.
>
> [0] https://github.com/mesonbuild/meson/issues/3327 for the LLVM_CONFIG
> example, which we'll address in a follow=up patch.
>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> Cc: Peter Seiderer <ps.report@gmx.net>
> Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
> docs/manual/adding-packages-meson.txt | 7 +++++++
> package/pkg-meson.mk | 3 +++
> 2 files changed, 10 insertions(+)
Both applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-05 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 20:04 [Buildroot] [PATCH 0/2] mesa: fix build with llvm (branch yem/meson-extra-progs) Yann E. MORIN
2019-09-28 20:04 ` [Buildroot] [PATCH 1/2] core/pkg-meson: allow packages to add extra [binaries] Yann E. MORIN
2019-10-05 9:14 ` Romain Naour
2019-10-05 20:33 ` Thomas Petazzoni [this message]
2019-09-28 20:04 ` [Buildroot] [PATCH 2/2] package/mesa3d: add llvm-config to meson [binaries] Yann E. MORIN
2019-10-05 9:15 ` Romain Naour
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=20191005223303.0c35239a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox