diff options
Diffstat (limited to 'docs/manual/rebuilding-packages.txt')
| -rw-r--r-- | docs/manual/rebuilding-packages.txt | 40 |
1 files changed, 14 insertions, 26 deletions
diff --git a/docs/manual/rebuilding-packages.txt b/docs/manual/rebuilding-packages.txt index e677590b4..d6a77a7fc 100644 --- a/docs/manual/rebuilding-packages.txt +++ b/docs/manual/rebuilding-packages.txt @@ -41,49 +41,37 @@ One of the most common questions asked by Buildroot users is how to rebuild a given package or how to remove a package without rebuilding everything from scratch. -Removing a package is currently unsupported by Buildroot without +Removing a package is unsupported by Buildroot without rebuilding from scratch. This is because Buildroot doesn't keep track of which package installs what files in the +output/staging+ and -+output/target+ directories. However, implementing clean package -removal is on the TODO-list of Buildroot developers. ++output/target+ directories, or which package would be compiled differently +depending on the availability of another package. 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. +re-configure, re-compile and re-install this package from scratch. You +can ask buildroot to do this with the +make <package>-dirclean+ command. -For convenience, most packages support the special make targets -<package>-reconfigure and <package>-rebuild to repeat the configure -and build steps. +For convenience, the special make targets +<package>-reconfigure and <package>-rebuild repeat the configure +resp. 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 which steps remain to be done, Buildroot maintains stamp files (empty -files that just tell whether this or that action has been done). The -problem is that these stamp files are not uniformly named and handled -by the different packages, so some understanding of the particular -package is needed. +files that just tell whether this or that action has been done): -For packages relying on Buildroot packages infrastructures (see -xref:adding-packages[this section] for details), the following stamp -files are relevant: - -* +output/build/packagename-version/.stamp_configured+. If removed, +* +output/build/<package>-<version>/.stamp_configured+. If removed, Buildroot will trigger the recompilation of the package from the configuration step (execution of +./configure+). -* +output/build/packagename-version/.stamp_built+. If removed, +* +output/build/<package>-<version>/.stamp_built+. If removed, Buildroot will trigger the recompilation of the package from the compilation step (execution of +make+). -.Notes -- Since the _Buildroot-2012.11_ release, all packages rely on the -Buildroot infrastructures. -- Only toolchain packages remain using custom makefiles (i.e. do not -use any Buildroot infrastructure). -- Most, if not all, packages and toolchain packages will progressively -be ported over to the generic, autotools or CMake infrastructure, -making it much easier to rebuild individual packages. +Note: toolchain packages use custom makefiles. Their stamp files are named +differently. -Further details about package special make target at the +Further details about package special make targets are explained in xref:pkg-build-steps[]. |