All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 30 Nov 2015 23:22:18 +0100	[thread overview]
Message-ID: <565CCC1A.5010209@mind.be> (raw)
In-Reply-To: <1691926.UbH5yYOTKg@sagittea>

On 30-11-15 13:04, J?r?me Pouiller wrote:
> Hello Yann,
> 
> On Sunday 29 November 2015 21:26:50 Yann E. MORIN wrote:
>> J?r?me, All,
>>
>> On 2015-11-18 15:37 +0100, J?r?me Pouiller spake thusly:
[snip]
>> Well, for help from extenal.mk (or local.mk, but I'd arue that would
>> be a bad idea, given that local.mk is supposedly short-lived), there
>> is in my opinion a much better solution.
>>
>> Change the 'help' rule to a double-colon make rule, like so:
>>
>>     help::
>>         echo Current Buildroot help
>>
>> Then you can add as many such rules in as many places you want,
>> especially in external.mk, and the will be appended one after the
>> others.
>
> Nice trick.

 IMHO tricks (nice or not) are no good because they make things more difficult
to understand. Also, we don't currently use the :: construct so I'd prefer to
avoid introducing it.


>> We just have to ensure that our help comes before the external ones,
>> so maybe you'll have to move our help block before inclusion of
>> external.mk...
> 
> I have a slight preference for my proposal since I think it allows a 
> finer control of the way extra help is handled. However, I have no 
> problem to send a new patch using your trick.

 Because of what I wrote above, I also prefer your proposal.


 Regards,
 Arnout

> 
> Regards,
> 


-- 
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:[~2015-11-30 22:22 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 [this message]
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

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=565CCC1A.5010209@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 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.