浏览代码

Add documentation for <pkg>-rebuild and <pkg>-reconfigure

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 <sho@reLinux.de>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Stephan Hoffmann 13 年之前
父节点
当前提交
040f6a325f
共有 2 个文件被更改,包括 6 次插入0 次删除
  1. 2 0
      Makefile
  2. 4 0
      docs/manual/rebuilding-packages.txt

+ 2 - 0
Makefile

@@ -654,6 +654,8 @@ help:
 	@echo
 	@echo
 	@echo 'Build:'
 	@echo 'Build:'
 	@echo '  all                    - make world'
 	@echo '  all                    - make world'
+	@echo '  <package>-rebuild      - force recompile <package>'
+	@echo '  <package>-reconfigure  - force reconfigure <package>'
 	@echo
 	@echo
 	@echo 'Configuration:'
 	@echo 'Configuration:'
 	@echo '  menuconfig             - interactive curses-based configurator'
 	@echo '  menuconfig             - interactive curses-based configurator'

+ 4 - 0
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,
 its build directory in +output/build+. Buildroot will then re-extract,
 re-configure, re-compile and re-install this package from scratch.
 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
 However, if you don't want to rebuild the package completely from
 scratch, a better understanding of the Buildroot internals is
 scratch, a better understanding of the Buildroot internals is
 needed. Internally, to keep track of which steps have been done and
 needed. Internally, to keep track of which steps have been done and