From: Norbert Lange <nolange79@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] allow build infrastructure to pick up installed meson tool
Date: Wed, 16 Oct 2019 13:19:23 +0200 [thread overview]
Message-ID: <20191016111927.14208-1-nolange79@gmail.com> (raw)
This is v3 of the patchset, only patch 1 got modifications.
Patch 1 will install a cross-compilation.conf as part of the toolchain
target, removing this logic from the meson package.
Patch 2 + Patch 3 allow picking up meson + ninja from the system,
this functionality is currently disabled.
Patch 4 moves some common functionality of the support tool
handling into a helper script.
[v2->v3]
- rebase
- support overriding [C,CXX,LD]FLAGS in package
- place most logic into a HOST_MESON_CROSSCONFIG_SED variable
- further refactoring and simplification
next reply other threads:[~2019-10-16 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 11:19 Norbert Lange [this message]
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
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=20191016111927.14208-1-nolange79@gmail.com \
--to=nolange79@gmail.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