From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 00/10] MAKEALL updates
Date: Tue, 2 May 2023 09:39:15 +0200 [thread overview]
Message-ID: <20230502073925.266116-1-s.hauer@pengutronix.de> (raw)
This series puts some love into the existing MAKEALL script. Some bugs
are fixes, pick the correct 32/64 ARM toolchain based on the config
file, support applying Kconfig fragments before compilation and some
output beautification.
Sascha
Sascha Hauer (10):
MAKEALL: Configure before setting up CROSS_COMPILE
MAKEALL: Select arm64 toolchain for 64bit ARM configs
MAKEALL: order configs alphabetically
MAKEALL: Do not print sizes
MAKEALL: Do not trap
MAKEALL: fix printing number of compiled configs
MAKEALL: support Kconfig fragments
MAKEALL: rename variables
MAKEALL: separate errors and warnings
MAKEALL: allow multiple defconfigs as arguments
MAKEALL | 88 +++++++++++++++++++++++++++++++++++----------------------
1 file changed, 54 insertions(+), 34 deletions(-)
--
2.39.2
next reply other threads:[~2023-05-02 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 7:39 Sascha Hauer [this message]
2023-05-02 7:39 ` [PATCH 01/10] MAKEALL: Configure before setting up CROSS_COMPILE Sascha Hauer
2023-05-02 7:39 ` [PATCH 02/10] MAKEALL: Select arm64 toolchain for 64bit ARM configs Sascha Hauer
2023-05-02 7:39 ` [PATCH 03/10] MAKEALL: order configs alphabetically Sascha Hauer
2023-05-02 7:39 ` [PATCH 04/10] MAKEALL: Do not print sizes Sascha Hauer
2023-05-02 7:39 ` [PATCH 05/10] MAKEALL: Do not trap Sascha Hauer
2023-05-02 7:39 ` [PATCH 06/10] MAKEALL: fix printing number of compiled configs Sascha Hauer
2023-05-02 7:39 ` [PATCH 07/10] MAKEALL: support Kconfig fragments Sascha Hauer
2023-05-02 7:39 ` [PATCH 08/10] MAKEALL: rename variables Sascha Hauer
2023-05-02 7:39 ` [PATCH 09/10] MAKEALL: separate errors and warnings Sascha Hauer
2023-05-02 7:39 ` [PATCH 10/10] MAKEALL: allow multiple defconfigs as arguments Sascha Hauer
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=20230502073925.266116-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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