Download build/tmp/deploy

Using the Yocto Project
subtle changes can occur that you might not detect until later. Consider the case where your recipe
is using a newer version of an upstream package. In this case, a new version of a piece of software
might introduce an optional dependency on another library, which is auto-detected. If that library has
already been built when the software is building, the software will link to the built library and that
library will be pulled into your image along with the new software even if you did not want the library.
The buildhistory class exists to help you maintain the quality of your build output. You can use the
class to highlight unexpected and possibly unwanted changes in the build output. When you enable
build history, it records information about the contents of each package and image and then commits
that information to a local Git repository where you can examine the information.
The remainder of this section describes the following:
• How you can enable and disable build history
• How to understand what the build history contains
• How to limit the information used for build history
• How to examine the build history from both a command-line and web interface
2.4.1. Enabling and Disabling Build History
Build history is disabled by default. To enable it, add the following statements to the end of your conf/
local.conf file found in the Build Directory [http://www.yoctoproject.org/docs/1.4.2/dev-manual/devmanual.html#build-directory]:
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
Enabling build history as previously described causes the build process to collect build output
information and commit it to a local Git [http://www.yoctoproject.org/docs/1.4.2/dev-manual/devmanual.html#git] repository.
Note
Enabling build history increases your build times slightly, particularly for images, and
increases the amount of disk space used during the build.
You can disable build history by removing the previous statements from your conf/local.conf file.
However, you should realize that enabling and disabling build history in this manner can change the
do_package task checksums, which if you are using the OEBasicHash signature generator (the default
for many current distro configurations including DISTRO = "poky" and DISTRO = "") and will result
in the packaging tasks being re-run during the subsequent build.
To disable the build history functionality without causing the packaging tasks to be re-run, add this
statement to your conf/local.conf file:
BUILDHISTORY_FEATURES = ""
10