From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: document make <package>-dirclean
Date: Thu, 19 Jun 2014 14:48:58 -0400 (EDT) [thread overview]
Message-ID: <409511316.213968.1403203738913.JavaMail.root@mail> (raw)
In-Reply-To: <20140619182648.GB3534@free.fr>
Hi Yann, All,
> > @@ -849,6 +849,7 @@ help:
> > @echo ' toolchain - build toolchain'
> > @echo ' <package>-rebuild - force recompile <package>'
> > @echo ' <package>-reconfigure - force reconfigure <package>'
> > + @echo ' <package>-dirclean - remove the whole <package>
> > build directory'
>
> I'm not specifically opposed to this, but then we are still missing
> quite a few package-specific actions, of which the full list is
> available in the manual:
> http://buildroot.net/downloads/manual/manual.html#pkg-build-steps
>
> Also, it is explained in details in the manual how (and when) to
> rebuild
> a package:
> http://buildroot.net/downloads/manual/manual.html#rebuild-pkg
>
> Excerpt:
> You can ask buildroot to [remove the package directory] with the
> "make <package>-dirclean" command.
>
> I believe we should only document the _very important_ commands in
> the
> 'make help' text, and direct the user to the manual for the others.
Having only a portion of commands is confusing.
I would say, either put every package commands in `make help` or
no `make <package>-foo` commands at all.
> E.g.
> something like:
>
> $ make help
> [...]
> Build:
> all - make world
> toolchain - build toolchain
> <package>-rebuild - force recompile <package>
> <package>-reconfigure - force reconfigure <package>
> <package>-graph-depends - generate graph of the dependency
> tree for package
> See the manual
> [http://buildroot.net/downloads/manual/manual.html] for
> the complete list of per-package build actions.
I'd remove the <package>-* command from `make help` and point to the
in-tree documentation instead (docs/manual/rebuilding-packages.txt).
That'd look like:
$ make help
[...]
Build:
all (or "world"?) - make world
toolchain - build toolchain
<package> - compile only <package>
<package>-<action> - See the manual [docs/manual/rebuilding-packages.txt]
for the list of per-package build actions.
[...]
What do you think?
Best,
Vivien
next prev parent reply other threads:[~2014-06-19 18:48 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 [this message]
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
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=409511316.213968.1403203738913.JavaMail.root@mail \
--to=vivien.didelot@savoirfairelinux.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