From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/9 v2] core: add the possibility to provide help for custom rules
Date: Sat, 19 Mar 2016 19:05:00 +0100 [thread overview]
Message-ID: <20160319190500.088f883a@free-electrons.com> (raw)
In-Reply-To: <e9f41039f5e4b50300a78a45a136cd04cf2c6cfe.1457717002.git.yann.morin.1998@free.fr>
Hello,
On Fri, 11 Mar 2016 18:41:09 +0100, Yann E. MORIN wrote:
> diff --git a/Makefile b/Makefile
> index 98c8dc7..7bb5f6d 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -966,6 +966,7 @@ endif
> @echo ' source-check - check selected packages for valid download URLs'
> @echo ' external-deps - list external packages used'
> @echo ' legal-info - generate info about license compliance'
> + @echo ' help-custom - print help about custom actions (if any)'
> @echo
> @echo ' make V=0|1 - 0 => quiet build (default), 1 => verbose build'
> @echo ' make O=dir - Locate all output files in "dir", including .config'
> @@ -974,6 +975,12 @@ endif
> @echo 'it on-line at http://buildroot.org/docs.html'
> @echo
>
> +# This rule does nothing, it is expected to be overloaded by
> +# a br2-external tree or a local.mk . However, it must exist,
> +# as we reference it in the main help, above. Making the rule
> +# .PHONY does not work.
> +help-custom:
> +
There is a pretty important problem with this implementation (which
gets even worse when PATCH 2 is applied), but I am not sure why it
happens: the custom help is not taken into account if you don't have a
configuration file defined. This is weird, because BR2_EXTERNAL_FILE
gets included outside of the BR2_HAVE_DOT_CONFIG condition. But still:
thomas at skate:~/projets/buildroot (master)$ cat /tmp/external/external.mk
help-custom:
@echo TEST
thomas at skate:~/projets/buildroot (master)$ make BR2_EXTERNAL=/tmp/external help-custom
make[1]: Nothing to be done for 'help-custom'.
And then, if I create a .config file:
thomas at skate:~/projets/buildroot (master)$ make defconfig
[...]
thomas at skate:~/projets/buildroot (master)$ make BR2_EXTERNAL=/tmp/external help-custom
TEST
This is not expected, since the help text is supposed to be available
even when no configuration has been defined.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-19 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:41 [Buildroot] [PATCH 0/9 v2] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 1/9 v2] core: add the possibility to provide help for custom rules Yann E. MORIN
2016-03-19 18:05 ` Thomas Petazzoni [this message]
2016-03-19 18:56 ` Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 2/9 v2] core: also display the custom help with our main help Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 3/9 v2] core/pkg-utils: add a macro to pretty-print a help entry Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 4/9 v2] docs/manual: print-help can be used in help-custom Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 5/9 v2] core/pkg-generic: add help about package-specific rules Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 6/9 v2] package/busybox: use the generic help rules Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 7/9 v2] linux: add " Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 8/9 v2] package/uclibc: use " Yann E. MORIN
2016-03-11 17:41 ` [Buildroot] [PATCH 9/9 v2] boot/barebox: " Yann E. MORIN
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=20160319190500.088f883a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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