From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 3/3] Makefile: Improve 'make help'
Date: Mon, 18 Mar 2024 17:06:54 +0100 [thread overview]
Message-ID: <ZfhmntA-tpbieR4J@yuki> (raw)
In-Reply-To: <20240104211935.1438103-4-petr.vorel@gmail.com>
Hi!
> index 49d91f4d5..7c9d1217a 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -216,8 +216,36 @@ test-metadata: metadata-all
> ## Help
> .PHONY: help
> help:
> - @echo "Please read the Configuration section in $(top_srcdir)/INSTALL"
> - @exit 1
> + @echo 'Cleaning:'
> + @echo ' clean - delete all files created by build'
> + @echo ' distclean - delete all non-source files'
> + @echo ' lib-clean - delete all files created by build in lib directory (C API library and tests)'
> + @echo ' libs-clean - delete all files created by build in libs directory (other libraries)'
> + @echo ' testcases-clean - delete all files created by build in testcases directory (tests)'
> + @echo
> + @echo 'Build:'
> + @echo ' all - build everything'
> + @echo ' autotools - preparation for configure'
> + @echo ' lib-all - build lib directory (C API library and tests)'
> + @echo ' libs-all - build libs directory (other libraries)'
> + @echo ' testcases-all - build testcases and their dependencies'
> + @echo
> + @echo 'Install:'
> + @echo ' install - install all files created by build'
> + @echo ' install-lib - install files in lib directory (C API library and tests)'
> + @echo ' install-libs - install files in libs directory (other libraries)'
> + @echo ' install-testcases - install testcases'
I'm not sure if the sub-targets should be described in make help. I
would say to stick to a simple set of clean, distclean, autotools, all,
install, doc, check and be done with it.
> + @echo 'Documentation:'
> + @echo ' doc - create test documentation (HTML and/or PDF, based on configuration)'
> + @echo
> + @echo 'Testing:'
> + @echo ' test - run all tests'
> + @echo ' test-c - run C API tests'
> + @echo ' test-metadata - run documentation tests'
> + @echo ' test-shell - run shell API tests'
This is way to confusing, we shouldn't mention the internal testsuite
here users will confuse that with actually running LTP tests.
We should instead probably mention the make check.
> + @echo 'For more info please read the Configuration section in $(top_srcdir)/INSTALL'
That file should be probably updated too.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-03-18 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 21:19 [LTP] [PATCH 0/3] Improve make Petr Vorel
2024-01-04 21:19 ` [LTP] [PATCH 1/3] Makefile: Add doc target Petr Vorel
2024-03-18 15:56 ` Cyril Hrubis
2024-01-04 21:19 ` [LTP] [PATCH 2/3] make: Delete gitignore.mk Petr Vorel
2024-03-18 15:58 ` Cyril Hrubis
2024-03-18 16:31 ` Petr Vorel
2024-01-04 21:19 ` [LTP] [PATCH 3/3] Makefile: Improve 'make help' Petr Vorel
2024-03-18 16:06 ` Cyril Hrubis [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=ZfhmntA-tpbieR4J@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=petr.vorel@gmail.com \
/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