From ed0a240e1632682ec4c33341f3e24ad71773cdfc Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 11 Dec 2012 12:07:58 -0600 Subject: documentation: Rename of poky-ref-manual folder to ref-manual. Changing the folder that holds the YP Reference Manual to be "ref-manual". This will help with confustion over the manual's intended purpose. (From yocto-docs rev: 1106442964b5080cb0b6b3bd3af32e9407c0f7c1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../maintaining-build-output-quality.html | 53 ++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html') diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html new file mode 100644 index 0000000000..f0896e6c89 --- /dev/null +++ b/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html @@ -0,0 +1,53 @@ + + + +2.4. Maintaining Build Output Quality + + + + + + + +
+

+2.4. Maintaining Build Output Quality

+

+ 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. +

+

+ 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

    • +
+

+

+
+ -- cgit v1.2.3-54-g00ecf