From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core/help: fix custom help without a .config
Date: Tue, 22 Mar 2016 23:40:17 +0100 [thread overview]
Message-ID: <56F1C9D1.2010104@mind.be> (raw)
In-Reply-To: <1458509069-11960-1-git-send-email-yann.morin.1998@free.fr>
On 03/20/16 22:24, Yann E. MORIN wrote:
> When there is no .config, we do not source $(BR2_EXTERNAL)/external.mk.
> So we can not expose the custom help in that situation.
>
> It is now known whether sourcing $(BR2_EXTERNAL)/external.mk outside the
> HAVE_DOT_CONFIG conditional block is entirely safe. Even if it would
> work today, we would have a hard time not breaking it in the future,
> because we do not have automatic checks for that and would need to rely
> on users reporting issues after the fact.
>
> Instead, we require the custom help to be defined in its own file in the
> br2-external tree. This way, we can safely include it unconditionally.
IMHO that custom help was a bad idea. It's adding complexity, an extra file in
BR2_EXTERNAL, and really not that useful...
>
> Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Makefile | 11 +++++++----
> docs/manual/customize-outside-br.txt | 7 ++++---
> 2 files changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index ea8b1e4..03657d5 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -976,10 +976,13 @@ 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.
> +ifneq ($(wildcard $(BR2_EXTERNAL)/help.mk),)
> +include $(BR2_EXTERNAL)/help.mk
Why not just -include?
Regards,
Arnout
> +endif
> +
> +# This rule does nothing, it is expected to be overloaded by a
> +# br2-external tree. However, it must exist, as we reference it
> +# as a dependency of the main help, above.
> help-custom:
>
> list-defconfigs:
> diff --git a/docs/manual/customize-outside-br.txt b/docs/manual/customize-outside-br.txt
> index be1827e..4f1c752 100644
> --- a/docs/manual/customize-outside-br.txt
> +++ b/docs/manual/customize-outside-br.txt
> @@ -108,9 +108,10 @@ And then in +$(BR2_EXTERNAL)/package/package1+ and
> normal +make <name>_defconfig+ command. They will be visible under the
> +User-provided configs+' label in the 'make list-defconfigs' output.
>
> -Additionally, an +external.mk+ file may define the +help-custom+ make
> -rule, to document custom make targets specific to this +BR2_EXTERNAL+
> -tree. The help is completely free-form.
> +Additionally, a +BR2_EXTERNAL+ tree may provide a file named +help.mk+
> +that defines the +help-custom+ make rule, to document custom make
> +targets specific to this +BR2_EXTERNAL+ tree. The help is completely
> +free-form. See below for a sample +$(BR2_EXTERNAL)/help.mk+ file:
>
> ------
> help-custom:
>
--
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
next prev parent reply other threads:[~2016-03-22 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 21:24 [Buildroot] [PATCH] core/help: fix custom help without a .config Yann E. MORIN
2016-03-22 22:40 ` Arnout Vandecappelle [this message]
2016-03-22 22:52 ` Thomas Petazzoni
2016-04-15 22:16 ` Peter Korsgaard
2016-04-16 7:28 ` Thomas Petazzoni
2016-04-16 21:07 ` Yann E. MORIN
2016-04-17 22:51 ` Arnout Vandecappelle
2016-04-18 20:27 ` 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=56F1C9D1.2010104@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