Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: document make <package>-dirclean
Date: Fri, 20 Jun 2014 12:11:54 +0200	[thread overview]
Message-ID: <20140620121154.39a88ecb@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LXBfosgS1dBZtx8ZMp_bEsxeyALNSOnMAEt7aS-nXpVMg@mail.gmail.com>

Dear Thomas De Schampheleire,

On Fri, 20 Jun 2014 11:40:10 +0200, Thomas De Schampheleire wrote:

> According to me, foo-dirclean is much more useful to the typical user
> than foo-rebuild or foo-reconfigure.

I agree.

> The latter two actions are
> typically used for OVERRIDE_SRCDIR only, right? While -dirclean can be
> used for any kind of (mis)action you performed.

Well, I also use -rebuild and -reconfigure when I directly hack into
output/build/<pkg>-<version>/ to do a quick test.

> So while I agree that some make targets should be listed to make sure
> the unsuspecting user is aware that they exist, dirclean would
> definitely be a part of this list, while rebuild/reconfigure need not
> necessarily IMO.

True.

> Maybe we should create a list of all the possible targets (here in
> this thread I mean) and then decide case-by-case if it's necessary to
> list them in 'make help' or not?

Another possible solution would be to have a <pkg>-help target that
lists all targets that are possible on a package, and then the main
"make help" only references that.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-06-20 10:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 17:44 [Buildroot] [PATCH] Makefile: document make <package>-dirclean Vivien Didelot
2014-06-19 18:26 ` Yann E. MORIN
2014-06-19 18:48   ` Vivien Didelot
2014-06-19 20:10     ` Yann E. MORIN
2014-06-20  9:28       ` Luca Ceresoli
2014-06-20 20:07         ` Yann E. MORIN
2014-06-20  9:40       ` Thomas De Schampheleire
2014-06-20 10:11         ` Thomas Petazzoni [this message]
2014-06-20 20:12           ` Yann E. MORIN
2014-06-20  8:27   ` Luca Ceresoli

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=20140620121154.39a88ecb@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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