From: Elia Pinto <gitter.spiros@gmail.com>
To: git@vger.kernel.org
Cc: Elia Pinto <gitter.spiros@gmail.com>
Subject: [PATCH] Makefile: add help target
Date: Fri, 8 Apr 2022 07:45:24 +0000 [thread overview]
Message-ID: <20220408074524.156165-1-gitter.spiros@gmail.com> (raw)
Add a help target to the Makefile to be able to run make help, in the same way
does the Makefiles self-generated by some build systems.
The target list has been statically extracted from the git Makefile with a
script and the results have been filtered in an essentially arbitrary way to
leave the ones that i imagines most interesting and frequent for a developer.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
---
The toy script I used is here
https://gist.github.com/devzero2000/cb887a6ba2764f7234191e560b64b7c8#file-list_targets_makefile-sh
Makefile | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 63 insertions(+)
diff --git a/Makefile b/Makefile
index e8aba291d7..f6d6de2eb9 100644
--- a/Makefile
+++ b/Makefile
@@ -3448,3 +3448,66 @@ $(FUZZ_PROGRAMS): all
$(XDIFF_OBJS) $(EXTLIBS) git.o $@.o $(LIB_FUZZING_ENGINE) -o $@
fuzz-all: $(FUZZ_PROGRAMS)
+
+# Help Target
+help:
+ @echo "The following are some of the valid targets for this Makefile:"
+ @echo "... all (the default if no target is provided)"
+ @echo "... build-perl-script"
+ @echo "... build-python-script"
+ @echo "... build-sh-script"
+ @echo "... check"
+ @echo "... check-builtins"
+ @echo "... check-docs"
+ @echo "... check-sha1"
+ @echo "... clean"
+ @echo "... clean-perl-script"
+ @echo "... clean-python-script"
+ @echo "... clean-sh-script"
+ @echo "... coccicheck"
+ @echo "... coccicheck-pending"
+ @echo "... cocciclean"
+ @echo "... configure"
+ @echo "... coverage"
+ @echo "... coverage-clean"
+ @echo "... coverage-clean-results"
+ @echo "... coverage-compile"
+ @echo "... coverage-prove"
+ @echo "... coverage-report"
+ @echo "... coverage-test"
+ @echo "... coverage-untested-functions"
+ @echo "... cover_db"
+ @echo "... cover_db_html"
+ @echo "... cscope"
+ @echo "... dist"
+ @echo "... distclean"
+ @echo "... dist-doc"
+ @echo "... doc"
+ @echo "... fuzz-all"
+ @echo "... fuzz-commit-graph"
+ @echo "... fuzz-objs"
+ @echo "... fuzz-pack-headers"
+ @echo "... fuzz-pack-idx"
+ @echo "... html"
+ @echo "... info"
+ @echo "... install"
+ @echo "... man"
+ @echo "... pdf"
+ @echo "... perf"
+ @echo "... profile"
+ @echo "... profile-clean"
+ @echo "... profile-fast"
+ @echo "... profile-fast-install"
+ @echo "... profile-install"
+ @echo "... quick-install-doc"
+ @echo "... quick-install-html"
+ @echo "... quick-install-man"
+ @echo "... reconfigure"
+ @echo "... rpm"
+ @echo "... sparse"
+ @echo "... strip"
+ @echo "... style"
+ @echo "... tags"
+ @echo "... TAGS"
+ @echo "... test"
+.PHONY : help
--
2.35.1
next reply other threads:[~2022-04-08 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 7:45 Elia Pinto [this message]
2022-04-08 9:32 ` [PATCH] Makefile: add help target Philip Oakley
2022-04-08 15:30 ` Taylor Blau
2022-04-08 15:44 ` Ævar Arnfjörð Bjarmason
2022-04-08 18:58 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 8:13 [PATCH] Makefile: Add " Stephen Boyd
2010-09-28 9:45 ` Junio C Hamano
2010-09-28 11:37 ` Sverre Rabbelier
2010-09-28 12:35 ` Andreas Ericsson
2010-09-29 6:10 ` yj2133011
2010-08-25 9:51 Stephen Boyd
2010-08-25 16:27 ` Sverre Rabbelier
2010-08-25 21:36 ` Stephen Boyd
2010-08-25 21:39 ` Sverre Rabbelier
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=20220408074524.156165-1-gitter.spiros@gmail.com \
--to=gitter.spiros@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).