From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] prepare build infrastructure to pick up installed meson tool
Date: Wed, 16 Oct 2019 15:48:50 +0200 [thread overview]
Message-ID: <20191016154850.0d093c4d@windsurf> (raw)
In-Reply-To: <20191016111927.14208-3-nolange79@gmail.com>
Hello Norbert
On Wed, 16 Oct 2019 13:19:25 +0200
Norbert Lange <nolange79@gmail.com> wrote:
> Automatically check for an available meson tool,
> and use it as long as the version is fitting.
>
> Using a system provided meson is not an official supported
> option, hence this is currently disabled.
> use of the system provided meson can be enforced with:
>
> make ... BR2_MESON_VERSION_MIN=0
>
> Signed-off-by: Norbert Lange <nolange79@gmail.com>
Thanks for this, however I don't think we will ever merge this until a
system-provided meson can effectively be used.
What about working on merging
0001-Only-fix-RPATH-if-install_rpath-is-not-empty.patch to upstream
Meson, in this form or another form ? This would definitely pave the
way to using the system-provided Meson.
Another (more useful ?) thing to look at: is it possible to use the
system-provided Python for Meson and Ninja, when python3 is provided by
the system ? I think Meson and Ninja by themselves are not long at all
to build, and it would be a much more useful direction for this patch
series.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-16 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 11:19 [Buildroot] allow build infrastructure to pick up installed meson tool Norbert Lange
2019-10-16 11:19 ` [Buildroot] [PATCH 1/4] package/pkg-meson: move crosscompilation support out of package Norbert Lange
2019-10-16 11:19 ` [Buildroot] [PATCH 2/4] prepare build infrastructure to pick up installed meson tool Norbert Lange
2019-10-16 13:48 ` Thomas Petazzoni [this message]
2019-10-16 16:28 ` Norbert Lange
2019-10-16 19:01 ` Thomas Petazzoni
2019-10-16 20:16 ` Yann E. MORIN
2019-10-16 20:31 ` Norbert Lange
2019-10-16 21:08 ` Thomas Petazzoni
2019-10-17 10:58 ` Norbert Lange
2019-10-16 20:22 ` Norbert Lange
2019-10-16 16:47 ` Yann E. MORIN
2019-10-16 17:22 ` Norbert Lange
2019-10-16 11:19 ` [Buildroot] [PATCH 3/4] prepare build infrastructure to pick up installed ninja tool Norbert Lange
2019-10-16 11:19 ` [Buildroot] [PATCH 4/4] support/dependencies: use a helper script for common checks Norbert Lange
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=20191016154850.0d093c4d@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