From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk
Date: Tue, 8 Mar 2016 22:21:49 +0100 [thread overview]
Message-ID: <56DF426D.2000800@mind.be> (raw)
In-Reply-To: <20160308220221.0a5088d0@free-electrons.com>
On 03/08/16 22:02, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 8 Mar 2016 21:54:55 +0100, Arnout Vandecappelle wrote:
>> On 11/18/15 15:37, J?r?me Pouiller wrote:
>>> It is handy to use local.mk or external.mk to add specific targets
>>> for current project. However, until now, it not possible to add help
>>> message these targets.
>>> This patch add LOCAL_HELP variable. This variable is aimed to be assigned
>>> from any .mk files. Its content is displayed with 'make help'.
>>>
>>> For exemple:
>>> LOCAL_HELP += "flash - Flash target"
>>> LOCAL_HELP += "chroot - Chroot into target/"
>>> LOCAL_HELP += "qemu - Run image with qemu"
>>> LOCAL_HELP += "install-nfs - Extract rootfs in \$$NFSROOT (=$(NFSROOT))"
>>> LOCAL_HELP += "`printf '%-22s%s' '$(var)-feature' ' - Call $(var) feature'`"
>>> LOCAL_HELP += "Please contact support at company.com in case of problem."
>>>
>>> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
>>
>> Looks good to me, except that I don't like the name 'LOCAL'. I'd prefer e.g.
>> ADDITIONAL.
>
> Wouldn't EXTERNAL_HELP be even better, suggesting that its main
> use-case is for BR2_EXTERNAL ?
Works for me as well. Additional is a word we're currently not using at all,
so perhaps reusing external is better.
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
prev parent reply other threads:[~2016-03-08 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 14:37 [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk Jérôme Pouiller
2015-11-18 14:37 ` [Buildroot] [PATCH 2/2] help: relocate help messages specific to one package Jérôme Pouiller
2015-11-18 14:49 ` Thomas Petazzoni
2015-11-19 10:44 ` Jérôme Pouiller
2015-11-29 20:39 ` Arnout Vandecappelle
2016-03-08 20:58 ` Arnout Vandecappelle
2015-11-29 20:26 ` [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk Yann E. MORIN
2015-11-30 12:04 ` Jérôme Pouiller
2015-11-30 22:22 ` Arnout Vandecappelle
2016-03-08 20:54 ` Arnout Vandecappelle
2016-03-08 21:02 ` Thomas Petazzoni
2016-03-08 21:19 ` Thomas Petazzoni
2016-03-08 21:21 ` Arnout Vandecappelle [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=56DF426D.2000800@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