From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] MAKEALL: add incremental build support
Date: Wed, 21 Jun 2023 09:54:22 +0200 [thread overview]
Message-ID: <20230621075422.GR18491@pengutronix.de> (raw)
In-Reply-To: <20230619094651.4143187-1-a.fatoum@pengutronix.de>
On Mon, Jun 19, 2023 at 11:46:51AM +0200, Ahmad Fatoum wrote:
> MAKEALL always deletes the build directory, before starting. Add a
> command line option to make this configurable.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> MAKEALL | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/MAKEALL b/MAKEALL
> index a4e268d54cf8..f2e774cf88be 100755
> --- a/MAKEALL
> +++ b/MAKEALL
> @@ -53,6 +53,7 @@ usage() {
> echo "LOGDIR -l log dir"
> echo "REGEX -e regex"
> echo "KCONFIG_ADD -k kconfig fragment"
> + echo "INCREMENTAL -i"
> echo ""
> }
>
> @@ -89,7 +90,7 @@ do_build_target() {
> local log_report="${LOGDIR}/${target}/report.log"
> local log_err="${LOGDIR}/${target}/errors.log"
>
> - rm -rf "${BUILDDIR}"
> + [ "$INCREMENTAL" != "1" ] && rm -rf "${BUILDDIR}"
> mkdir -p "${LOGDIR}/${target}"
> printf "Building ${arch} ${target} \n" >&2 | tee -a "${log_report}"
>
> @@ -196,7 +197,7 @@ do_build_all() {
> return $build_target
> }
>
> -while getopts "hc:j:O:l:a:e:k:" Option
> +while getopts "hc:j:O:l:a:e:k:i" Option
> do
> case $Option in
> a )
> @@ -220,6 +221,9 @@ case $Option in
> k )
> KCONFIG_ADD="${KCONFIG_ADD} ${OPTARG}"
> ;;
> + i )
> + INCREMENTAL=1
> + ;;
> h )
> usage
> exit 0
> --
> 2.39.2
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-06-21 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:46 Ahmad Fatoum
2023-06-21 7:54 ` Sascha Hauer [this message]
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=20230621075422.GR18491@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@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