jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 14:16:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/manual: rephrase part about rebuilding packages

Browse Source 
There is no need to tell people that they should remove stamp files: they
should use the make <pkg>-reconfigure and make <pkg>-rebuild make targets
instead.  We still keep an explanation about stamp files, just to give the
user an insight on how Buildroot works internally.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Thomas Petazzoni 2014-02-23 16:04:28 +01:00 committed by Peter Korsgaard
parent 0b100de2cf
commit 9cab58b69e
1 changed files with 17 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/manual/rebuilding-packages.txt
View File

@ -51,23 +51,25 @@ its build directory in +output/build+. Buildroot will then re-extract,
re-configure, re-compile and re-install this package from scratch. You re-configure, re-compile and re-install this package from scratch. You
can ask buildroot to do this with the +make <package>-dirclean+ command. can ask buildroot to do this with the +make <package>-dirclean+ command.
For convenience, the special make targets On the other hand, if you only want to restart the build process of a
<package>-reconfigure and <package>-rebuild repeat the configure package from its compilation step, you can run +make
resp. build steps. <package>-rebuild+, followed by +make+ or +make <package>+. It will
restart the compilation and installation of the package, but not from
scratch: it basically simply re-executes +make+ and +make install+
inside the package, so it will only rebuild files that changed.
However, if you don't want to rebuild the package completely from If you want to restart the build process of a package from its
scratch, a better understanding of the Buildroot internals is configuration step, you can run +make <package>-reconfigure+, followed
needed. Internally, to keep track of which steps have been done and by +make+ or +make <package>+. It will restart the configuration,
which steps remain to be done, Buildroot maintains stamp files (empty compilation and installation of the package.
files that just tell whether this or that action has been done):
* +output/build/<package>-<version>/.stamp_configured+. If removed, Internally, Buildroot creates so-called _stamp files_ to keep track of
Buildroot will trigger the recompilation of the package from the which build steps have been completed for each package. They are
configuration step (execution of +./configure+). stored in the package build directory,
+output/build/<package>-<version>/+ and are named
* +output/build/<package>-<version>/.stamp_built+. If removed, +.stamp_<step-name>+. The commands detailed above simply manipulate
Buildroot will trigger the recompilation of the package from the these stamp files to force Buildroot to restart a specific set of
compilation step (execution of +make+). steps of a package build process.
Further details about package special make targets are explained in Further details about package special make targets are explained in
xref:pkg-build-steps[]. xref:pkg-build-steps[].