docs/manual/rebuilding-packages.txt

30  * When an additional package is added to the configuration, a full
32    package has never been built, and will build it. However, if this
33    package is a library that can optionally be used by packages that
38    package, but without +openssl+. Your system works, but you realize
40    +openssl+ package in Buildroot configuration and restart the
46  * When a package is removed from the configuration, Buildroot does
48    this package from the target root filesystem or from the toolchain
50    package. However, generally you don't necessarily need this package
54  * When the sub-options of a package are changed, the package is not
56    this package is often sufficient, unless enabling the package
57    sub-option adds some features to the package that are useful for
58    another package which has already been built. Again, Buildroot does
59    not track when a package should be rebuilt: once a package has been
68  * When a package listed in +FOO_DEPENDENCIES+ is rebuilt or removed,
69    the package +foo+ is not automatically rebuilt. For example, if a
70    package +bar+ is listed in +FOO_DEPENDENCIES+ with +FOO_DEPENDENCIES
71    = bar+ and the configuration of the +bar+ package is changed, the
72    configuration change would not result in a rebuild of package +foo+
97 rebuild a given package or how to remove a package without rebuilding
100 Removing a package is unsupported by Buildroot without
102 of which package installs what files in the +output/staging+ and
103 +output/target+ directories, or which package would be compiled differently
104 depending on the availability of another package.
106 The easiest way to rebuild a single package from scratch is to remove
108 re-configure, re-compile and re-install this package from scratch. You
109 can ask buildroot to do this with the +make <package>-dirclean+ command.
112 package from its compilation step, you can run +make <package>-rebuild+. It
113 will restart the compilation and installation of the package, but not from
114 scratch: it basically re-executes +make+ and +make install+ inside the package,
117 If you want to restart the build process of a package from its configuration
118 step, you can run +make <package>-reconfigure+. It will restart the
119 configuration, compilation and installation of the package.
121 While +<package>-rebuild+ implies +<package>-reinstall+ and
122 +<package>-reconfigure+ implies +<package>-rebuild+, these targets as well
123 as +<package>+ only act on the said package, and do not trigger re-creating
128 which build steps have been completed for each package. They are
129 stored in the package build directory,
130 +output/build/<package>-<version>/+ and are named
133 steps of a package build process.
135 Further details about package special make targets are explained in