Lines Matching full:rebuild

4 [[full-rebuild]]
5 === Understanding when a full rebuild is necessary
10 tools. In some cases, Buildroot should rebuild the entire system, in
16 rebuild is necessary. As a hint, here are a few rules of thumb that
20    rebuild is needed. Changing the architecture variant, the binary
24  * When the toolchain configuration is changed, a complete rebuild
31    rebuild is not necessarily needed. Buildroot will detect that this
34    have already been built, Buildroot will not automatically rebuild
36    can rebuild them manually, or you should do a full rebuild. For
44    either have to do a full rebuild, or rebuild +ctorrent+ itself.
49    _sysroot_. A full rebuild is needed to get rid of this
63    rebuild is needed. However, when changes to the root filesystem
65    there is no need for a full rebuild: a simple +make+ invocation
72    configuration change would not result in a rebuild of package +foo+
73    automatically. In this scenario, you may need to either rebuild any
75    or perform a full rebuild to ensure any +bar+ dependent packages are
80 made, do a full rebuild. If you get the same build error, then you are
84 progresses, you will progressively learn when a full rebuild is really
87 For reference, a full rebuild is achieved by running:
93 [[rebuild-pkg]]
94 === Understanding how to rebuild packages
97 rebuild a given package or how to remove a package without rebuilding
106 The easiest way to rebuild a single package from scratch is to remove
112 package from its compilation step, you can run +make <package>-rebuild+. It
115 so it will only rebuild files that changed.
121 While +<package>-rebuild+ implies +<package>-reinstall+ and
122 +<package>-reconfigure+ implies +<package>-rebuild+, these targets as well