Patchwork [git,commit] Add documentation for <pkg>-rebuild and <pkg>-reconfigure

mail settings
Submitter Peter Korsgaard
Date April 7, 2012, 5:38 p.m.
Message ID <>
Download mbox | patch
Permalink /patch/151312/
State Not Applicable
Headers show


Peter Korsgaard - April 7, 2012, 5:38 p.m.

Since these two special make targets are very useful but not yet
mentioned in the documentation I added them to the make help and
the manual.

Signed-off-by: Stephan Hoffmann <>
Signed-off-by: Peter Korsgaard <>
 Makefile                            |    2 ++
 docs/manual/rebuilding-packages.txt |    4 ++++
 2 files changed, 6 insertions(+), 0 deletions(-)


diff --git a/Makefile b/Makefile
index 30099d9..3a09417 100644
--- a/Makefile
+++ b/Makefile
@@ -654,6 +654,8 @@  help:
 	@echo 'Build:'
 	@echo '  all                    - make world'
+	@echo '  <package>-rebuild      - force recompile <package>'
+	@echo '  <package>-reconfigure  - force reconfigure <package>'
 	@echo 'Configuration:'
 	@echo '  menuconfig             - interactive curses-based configurator'
diff --git a/docs/manual/rebuilding-packages.txt b/docs/manual/rebuilding-packages.txt
index 9a41a88..f247dd0 100644
--- a/docs/manual/rebuilding-packages.txt
+++ b/docs/manual/rebuilding-packages.txt
@@ -15,6 +15,10 @@  The easiest way to rebuild a single package from scratch is to remove
 its build directory in +output/build+. Buildroot will then re-extract,
 re-configure, re-compile and re-install this package from scratch.
+For convenience, most packages support the special make targets
+<package>-reconfigure and <package>-rebuild to repeat the configure
+and build steps.
 However, if you don't want to rebuild the package completely from
 scratch, a better understanding of the Buildroot internals is
 needed. Internally, to keep track of which steps have been done and