Message ID | cover-0.5-00000000000-20220901T130817Z-avarab@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Makefile: split up $(test_bindir_programs) | expand |
On 9/1/2022 9:17 AM, Ævar Arnfjörð Bjarmason wrote: > Ævar Arnfjörð Bjarmason (5): > Makefile: factor sed-powered '#!/bin/sh' munging into a variable > Makefile: define "TEST_{PROGRAM,OBJS}" variables earlier > Makefile: simplify $(test_bindir_programs) rule by splitting it up > Makefile: define bin-wrappers/% rules with a template > Makefile: fix "make clean && make bin-wrappers/$NAME" dependencies > > Makefile | 58 +++++++++++++++++++++++++++++++++++++------------------- > 1 file changed, 39 insertions(+), 19 deletions(-) I find it very distracting when you send a full patch series in the middle of someone else's patch series. Viewing the thread now involves two distinct conversations, assuming that your series gets review and requires multiple versions. I would rather that you started a new thread with your proposed series and then sent a reply in this thread pointing to that one. Thanks, -Stolee
Hi Ævar, On Thu, 1 Sep 2022, Ævar Arnfjörð Bjarmason wrote: > On Thu, Sep 01 2022, Johannes Schindelin wrote: > > > [...] > > On Wed, 31 Aug 2022, Victoria Dye via GitGitGadget wrote: > > [...] > >> @@ -3062,7 +3067,7 @@ bin-wrappers/%: wrap-for-bin.sh > >> $(call mkdir_p_parent_template) > >> $(QUIET_GEN)sed -e '1s|#!.*/sh|#!$(SHELL_PATH_SQ)|' \ > >> -e 's|@@BUILD_DIR@@|$(shell pwd)|' \ > >> - -e 's|@@PROG@@|$(patsubst test-%,t/helper/test-%$(X),$(@F))$(patsubst git%,$(X),$(filter $(@F),$(BINDIR_PROGRAMS_NEED_X)))|' < $< > $@ && \ > >> + -e 's|@@PROG@@|$(patsubst test-%,t/helper/test-%,$(@F))$(if $(filter-out $(BINDIR_PROGRAMS_NO_X),$(@F)),$(X),)|' < $< > $@ && \ > > > > It took me a good while to wrap my head around this (and let me be clear: > > I consider none of this your fault, it's the fault of the design of the > > Makefile syntax). > > > > Let me untangle this, for posterity's benefit. We substitute the > > placeholder `@@PROG@@` with a concatenation of two strings that are both > > derived from `@F`, i.e. the basename of the to-be-wrapped command. > > We could do this later, [... something about touching the same code ...] Yes, and we should. It would be better if we kept the focus on Scalar in this mail thread, to get it done first. It is the stated preference in this project anyway to avoid working on the code that is already being worked on in other in-flight patch series, to reduce unnecessary friction. Ciao, Johannes