From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] help: add a way to document targets declared in local.mk/external.mk
Date: Wed, 09 Mar 2016 09:27:54 +0100 [thread overview]
Message-ID: <3019698.gqGZGCWVhD@sagittea> (raw)
In-Reply-To: <56DF5DFB.1050309@mind.be>
Hello Yann, Arnout, All,
On Wednesday 09 March 2016 00:19:23 Arnout Vandecappelle wrote:
> On 03/08/16 23:10, Yann E. MORIN wrote:
[...]
> > What we could do, however, would be:
> > - in external.mk:
> > BR2_HAS_EXTRA_HELP = YES # Whatever non empty
> >
> > - in the main Makefile:
> > help:
> > blabla our current help
> > $(if $(BR2_HAS_EXTRA_HELP),echo " - local-help to get
> > local help blabla)>
> > which would be IMHO much much nicer and much much simpler...
>
> I don't see the advantage of that, to be honest... The point is to
> append it to the main help. You expect just a few lines of extra help
> text.
I agree with Arnout.
I add that EXTRA_HELP is generic enough to implement Yann's idea if
necessary. Instead of supporting BR2_HAS_EXTRA_HELP, just add in
external.mk:
EXTRA_HELP = "- local-help to get local help blabla"
local-help:
@echo "..."
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2016-03-09 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 21:48 [Buildroot] [PATCH v2 1/2] help: add a way to document targets declared in local.mk/external.mk Jérôme Pouiller
2016-03-08 21:48 ` [Buildroot] [PATCH v2 2/2] help: relocate help messages specific to one package Jérôme Pouiller
2016-03-08 22:59 ` Yann E. MORIN
2016-03-08 23:16 ` Arnout Vandecappelle
2016-03-09 18:01 ` Yann E. MORIN
2016-03-08 22:10 ` [Buildroot] [PATCH v2 1/2] help: add a way to document targets declared in local.mk/external.mk Yann E. MORIN
2016-03-08 22:13 ` Thomas Petazzoni
2016-03-08 22:31 ` Yann E. MORIN
2016-03-08 23:19 ` Arnout Vandecappelle
2016-03-09 8:27 ` Jérôme Pouiller [this message]
2016-03-09 17:57 ` Yann E. MORIN
2016-03-20 18:28 ` 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=3019698.gqGZGCWVhD@sagittea \
--to=jezz@sysmic.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.