From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Denton Liu <liu.denton@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 5/7] Makefile: add 'check-sort' target
Date: Wed, 17 Mar 2021 18:42:11 +0100 [thread overview]
Message-ID: <87r1kdzngs.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <YFI9QzKMKLMXYoyz@coredump.intra.peff.net>
On Wed, Mar 17 2021, Jeff King wrote:
> SCRIPT_SH += git-bisect.sh
> SCRIPT_SH += git-difftool--helper.sh
> SCRIPT_SH += git-filter-branch.sh
> @@ -1037,6 +1047,7 @@ LIB_OBJS += ws.o
> LIB_OBJS += wt-status.o
> LIB_OBJS += xdiff-interface.o
> LIB_OBJS += zlib.o
> +$(call check-sort,LIB_OBJS)
>
> BUILTIN_OBJS += builtin/add.o
> BUILTIN_OBJS += builtin/am.o
>
> And then it's just a single-liner for each block that should be checked.
> We haven't used $(call) or $(eval) yet in our Makefile, but past
> discussions have reached the conclusion that they should be safe
> (they're both in GNU make 3.80, which is the oldest version worth caring
> about).
...also this sort of thing can be guarded by "ifdef DEVELOPER" or
something, which AFAICT (from trying to introduce syntax errors etc.)
will get parsed first, before "make" even tries to parse what's within
the ifdef.
So if we have bells & whistles in that sort of setup it can be less
portable than the Makefile in general..
next prev parent reply other threads:[~2021-03-17 17:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 0:56 [PATCH 0/7] Sort lists and add static-analysis Denton Liu
2021-03-16 0:56 ` [PATCH 1/7] Makefile: mark 'check-builtins' as a .PHONY target Denton Liu
2021-03-16 4:59 ` Eric Sunshine
2021-03-17 17:47 ` Junio C Hamano
2021-03-16 0:56 ` [PATCH 2/7] Makefile: ASCII-sort LIB_OBJS Denton Liu
2021-03-16 0:56 ` [PATCH 3/7] builtin.h: ASCII-sort list of functions Denton Liu
2021-03-17 17:51 ` Junio C Hamano
2021-03-16 0:56 ` [PATCH 4/7] test-tool.h: " Denton Liu
2021-03-17 17:54 ` Junio C Hamano
2021-03-16 0:56 ` [PATCH 5/7] Makefile: add 'check-sort' target Denton Liu
2021-03-16 6:37 ` Eric Sunshine
2021-03-17 9:50 ` Denton Liu
2021-03-17 12:47 ` Ævar Arnfjörð Bjarmason
2021-03-17 17:32 ` Jeff King
2021-03-17 17:42 ` Ævar Arnfjörð Bjarmason [this message]
2021-03-17 21:48 ` Eric Sunshine
2021-03-17 22:01 ` Jeff King
2021-03-17 18:01 ` Junio C Hamano
2021-03-17 18:16 ` Ævar Arnfjörð Bjarmason
2021-03-17 17:59 ` Junio C Hamano
2021-03-16 0:56 ` [PATCH 6/7] ci/run-static-analysis.sh: make check-builtins Denton Liu
2021-03-16 0:56 ` [PATCH 7/7] ci/run-static-analysis.sh: make check-sort Denton Liu
2021-03-17 11:01 ` [PATCH 0/7] Sort lists and add static-analysis Bagas Sanjaya
2021-03-17 18:05 ` Junio C Hamano
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=87r1kdzngs.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=peff@peff.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;
as well as URLs for NNTP newsgroup(s).