diff options
| author | Timo Mueller <timo.mueller@bmw-carit.de> | 2013-02-08 09:16:33 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-02-14 17:25:35 +0000 |
| commit | a41a805500cab281fba15bd8e5d3e60b88d0d4be (patch) | |
| tree | 9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html | |
| parent | 768152340898cbb9faed6e8865a4e35c69833230 (diff) | |
| download | poky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz | |
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi,
the generation of eclipse help files has been merged from the timo
branch to the master. Since the creation of the timo branch there have
been some changes to the master branch (e.g. new documentation,
renamed documentation).
This patch set does some cleanup for the renamed documentation and
adds eclipse help generation support to the new documentation.
01: Removes the 'the' from the document titles
02..04: Cleanup obsolete artifacts resulting from the merge
05..08: Add eclipse help generation for ref-manual
09..13: Add eclipse help generation for kernel-dev
14..18: Add eclipse help generation for profile-manual
Best regards,
Timo
This patch set originally contained 18 patches. I (Scott Rifenbark)
had to push these changes as two parts. This is the first part.
It does not include creation of the three cusomization files.
(From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html | 53 |
1 files changed, 0 insertions, 53 deletions
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 deleted file mode 100644 index f0896e6c89..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html +++ /dev/null | |||
| @@ -1,53 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>2.4. Maintaining Build Output Quality</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="The Yocto Project Reference Manual"> | ||
| 8 | <link rel="up" href="usingpoky.html" title="Chapter 2. Using the Yocto Project"> | ||
| 9 | <link rel="prev" href="usingpoky-debugging-others.html" title="2.3.8. Other Tips"> | ||
| 10 | <link rel="next" href="enabling-and-disabling-build-history.html" title="2.4.1. Enabling and Disabling Build History"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4. Maintaining Build Output Quality"> | ||
| 13 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | ||
| 14 | <a name="maintaining-build-output-quality"></a>2.4. Maintaining Build Output Quality</h2></div></div></div> | ||
| 15 | <p> | ||
| 16 | A build's quality can be influenced by many things. | ||
| 17 | For example, if you upgrade a recipe to use a new version of an upstream software | ||
| 18 | package or you experiment with some new configuration options, subtle changes | ||
| 19 | can occur that you might not detect until later. | ||
| 20 | Consider the case where your recipe is using a newer version of an upstream package. | ||
| 21 | In this case, a new version of a piece of software might introduce an optional | ||
| 22 | dependency on another library, which is auto-detected. | ||
| 23 | If that library has already been built when the software is building, | ||
| 24 | then the software will link to the built library and that library will be pulled | ||
| 25 | into your image along with the new software even if you did not want the | ||
| 26 | library. | ||
| 27 | </p> | ||
| 28 | <p> | ||
| 29 | The <code class="filename">buildhistory</code> class exists to help you maintain | ||
| 30 | the quality of your build output. | ||
| 31 | You can use the class to highlight unexpected and possibly unwanted | ||
| 32 | changes in the build output. | ||
| 33 | When you enable build history it records information about the contents of | ||
| 34 | each package and image and then commits that information to a local Git | ||
| 35 | repository where you can examine the information. | ||
| 36 | </p> | ||
| 37 | <p> | ||
| 38 | The remainder of this section describes the following: | ||
| 39 | </p> | ||
| 40 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
| 41 | <li class="listitem"><p>How you can enable and disable | ||
| 42 | build history</p></li> | ||
| 43 | <li class="listitem"><p>How to understand what the build history contains | ||
| 44 | </p></li> | ||
| 45 | <li class="listitem"><p>How to limit the information used for build history | ||
| 46 | </p></li> | ||
| 47 | <li class="listitem"><p>How to examine the build history from both a | ||
| 48 | command-line and web interface</p></li> | ||
| 49 | </ul></div> | ||
| 50 | <p> | ||
| 51 | </p> | ||
| 52 | </div></body> | ||
| 53 | </html> | ||