From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH/RFC] Makefile: add 'help' target for target summary
Date: Tue, 13 Dec 2011 20:16:04 +0700 [thread overview]
Message-ID: <1323782164-11759-1-git-send-email-pclouds@gmail.com> (raw)
I find this "make help" very helpful (at work, on a different
project). With this I don't have to crawl through Makefile when I need
something but cannot remember what's the target name. It should also
help discover new targets.
We may also have "make vars" (or something like that) that shows list
of user-configurable variables, basically a conversion of the big
comment block near the makefile's top into a printable target.
I don't work with this Makefile much, so this is just an idea. Anyone
up to turn it to something actually useful?
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
Makefile | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/Makefile b/Makefile
index ed82320..abf6cf9 100644
--- a/Makefile
+++ b/Makefile
@@ -2603,3 +2603,17 @@ profile-all: profile-clean
$(MAKE) CFLAGS="$(PROFILE_GEN_CFLAGS)" all
$(MAKE) CFLAGS="$(PROFILE_GEN_CFLAGS)" -j1 test
$(MAKE) CFLAGS="$(PROFILE_USE_CFLAGS)" all
+
+.PHONY: help
+
+help:
+ @echo "test Run the test suite"
+ @echo "coverage Build git with coverage support"
+ @echo "cover_db Generate coverage database from *.gcov"
+ @echo "cover_db_html Generate coverage report"
+ @echo "profile-all Build git with profiling support"
+ @echo "clean Clean intermediate files"
+ @echo "distclean Clean even more for dist packaging"
+ @echo "sparse Run git with sparse"
+ @echo "cscope Generate cscope symbol database"
+ @echo "check-docs Check documentation"
--
1.7.8.36.g69ee2
next reply other threads:[~2011-12-13 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 13:16 Nguyễn Thái Ngọc Duy [this message]
2011-12-13 15:00 ` [PATCH/RFC] Makefile: add 'help' target for target summary Jakub Narebski
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=1323782164-11759-1-git-send-email-pclouds@gmail.com \
--to=pclouds@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).