Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/8] core: add the possibility to provide help for local, custom rules
Date: Fri, 11 Mar 2016 01:01:13 +0100	[thread overview]
Message-ID: <56E20AC9.4000506@mind.be> (raw)
In-Reply-To: <20160310202257.GB3424@free.fr>

On 03/10/16 21:22, Yann E. MORIN wrote:
> Arnout, All,
>
> On 2016-03-10 00:35 +0100, Arnout Vandecappelle spake thusly:
>> On 03/09/16 23:22, Yann E. MORIN wrote:
>>> When using a br2-external tree, it is possible (as stated in our manual)
>>> to implement whatever arbitrary extra make rules (such as flashing a
>>> board, or extracting the rootfs in an NFS export...). Some of those
>>> extra rules might be exposed to the user as new entry points that the
>>> user can call by itself.
>>>
>>> However, there is no way for the br2-external to advertise those new
>>> rules in the help text.
>>>
>>> We add the possibility to do so, by adding a new make rule, called
>>> help-local, advertised in our own help info.
>>>
>>> It is up to the br2-external tree to provide whatever help text is
>>> deemed necessary.
>>>
>>> Note that we need to provide an empty, dummy help-local' rule, since it
>>> is always advertised. Since this rule is empty, make gently reports that
>>> there is "Nothing to be done for `help-local'", which is pretty well
>>> fitting when help-local was not provided (either because there's no
>>> br2-external tree, or when the br2-external tree does not provide it.
>>>
>>> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>> Cc: J?r?me Pouiller <jezz@sysmic.org>
>>> Cc: Arnout Vandecappelle <arnout@mind.be>
>>> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>>> ---
>>>   Makefile | 6 ++++++
>>>   1 file changed, 6 insertions(+)
>>>
>>> diff --git a/Makefile b/Makefile
>>> index f2822a2..d24793b 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-local             - print help about local, 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,11 @@ 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.
>>> +help-local:
>>
>>   It's sufficient and better to do
>>
>> .PHONY: help-local
>
> I tried (evenm before I submitted!) and it does not work. It still
> prints that there is nothing to do...
>
> Here's my test case:
>
>      $ cat Makefile
>      .PHONY: help
>      help:
>
>      $ make help
>      make: Nothing to be done for `help'.

  But that's also the case with the empty rule, no?

  My point was: if you just declare it phony, it will have the same effect. In 
addition, you've declared it phony already which is really what we want in the 
end. And finally, when declaring it phony, there's no need to add a comment 
because it's obvious that it's a phony target.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-03-11  0:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 22:22 [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 1/8] core: add the possibility to provide help for local, custom rules Yann E. MORIN
2016-03-09 23:35   ` Arnout Vandecappelle
2016-03-10 20:22     ` Yann E. MORIN
2016-03-11  0:01       ` Arnout Vandecappelle [this message]
2016-03-09 22:22 ` [Buildroot] [PATCH 2/8] core/pkg-utils: add a macro to pretty-print a help entry Yann E. MORIN
2016-03-09 23:37   ` Arnout Vandecappelle
2016-03-10  9:31     ` Jérôme Pouiller
2016-03-10 20:27       ` Yann E. MORIN
2016-03-10 20:24     ` Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 3/8] core/pkg-generic: add help about package-specific rules Yann E. MORIN
2016-03-09 23:38   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 4/8] package/busybox: use the generic help rules Yann E. MORIN
2016-03-09 23:38   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 5/8] linux: add " Yann E. MORIN
2016-03-09 23:47   ` Arnout Vandecappelle
2016-03-10  9:21     ` Jérôme Pouiller
2016-03-10  9:39       ` Thomas Petazzoni
2016-03-10  9:52         ` Arnout Vandecappelle
2016-03-10 10:12           ` Thomas Petazzoni
2016-03-10 20:34         ` Yann E. MORIN
2016-03-10 20:58           ` Thomas Petazzoni
2016-03-10 20:29     ` Yann E. MORIN
2016-03-09 22:22 ` [Buildroot] [PATCH 6/8] package/uclibc: use " Yann E. MORIN
2016-03-09 23:47   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 7/8] boot/barebox: " Yann E. MORIN
2016-03-09 23:47   ` Arnout Vandecappelle
2016-03-09 22:22 ` [Buildroot] [PATCH 8/8] docs/manual: document the br2-external help-local Yann E. MORIN
2016-03-09 23:35 ` [Buildroot] [PATCH 0/8] core: allow for custom, local help; rearrange package-specific help (branch yem/help) Arnout Vandecappelle
2016-03-10  8:31   ` Thomas Petazzoni
2016-03-10 20:20     ` Yann E. MORIN
2016-03-10 21:01   ` Thomas Petazzoni

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=56E20AC9.4000506@mind.be \
    --to=arnout@mind.be \
    --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