54 lines
2.8 KiB
HTML
54 lines
2.8 KiB
HTML
<html>
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||
<title>2.4. Maintaining Build Output Quality</title>
|
||
<link rel="stylesheet" type="text/css" href="../book.css">
|
||
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
|
||
<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
|
||
<link rel="up" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
|
||
<link rel="prev" href="usingpoky-debugging-others.html" title="2.3.8. Other Tips">
|
||
<link rel="next" href="enabling-and-disabling-build-history.html" title="2.4.1. Enabling and Disabling Build History">
|
||
</head>
|
||
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4. Maintaining Build Output Quality">
|
||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||
<a name="maintaining-build-output-quality"></a>2.4. Maintaining Build Output Quality</h2></div></div></div>
|
||
<p>
|
||
A build's quality can be influenced by many things.
|
||
For example, if you upgrade a recipe to use a new version of an upstream software
|
||
package or you experiment with some new configuration options, 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,
|
||
then 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.
|
||
</p>
|
||
<p>
|
||
The <code class="filename">buildhistory</code> 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.
|
||
</p>
|
||
<p>
|
||
The remainder of this section describes the following:
|
||
</p>
|
||
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
|
||
<li class="listitem"><p>How you can enable and disable
|
||
build history</p></li>
|
||
<li class="listitem"><p>How to understand what the build history contains
|
||
</p></li>
|
||
<li class="listitem"><p>How to limit the information used for build history
|
||
</p></li>
|
||
<li class="listitem"><p>How to examine the build history from both a
|
||
command-line and web interface</p></li>
|
||
</ul></div>
|
||
<p>
|
||
</p>
|
||
</div></body>
|
||
</html>
|