summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html
diff options
context:
space:
mode:
authorTimo Mueller <timo.mueller@bmw-carit.de>2013-02-08 09:16:33 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:25:35 +0000
commita41a805500cab281fba15bd8e5d3e60b88d0d4be (patch)
tree9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html
parent768152340898cbb9faed6e8865a4e35c69833230 (diff)
downloadpoky-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/examining-build-history-information.html')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html70
1 files changed, 0 insertions, 70 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html
deleted file mode 100644
index 0fa3f74545..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html
+++ /dev/null
@@ -1,70 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.2.4. Examining Build History Information</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="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
9<link rel="prev" href="using-build-history-to-gather-image-information-only.html" title="2.4.2.3. Using Build History to Gather Image Information Only">
10<link rel="next" href="technical-details.html" title="Chapter 3. Technical Details">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.2.4. Examining Build History Information">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="examining-build-history-information"></a>2.4.2.4. Examining Build History Information</h4></div></div></div>
15<p>
16 You can examine build history output from the command line or
17 from a web interface.
18 </p>
19<p>
20 To see any changes that have occurred (assuming you have
21 <code class="filename">BUILDHISTORY_COMMIT = "1"</code>), you can simply
22 use any Git command that allows you to view the history of
23 a repository.
24 Here is one method:
25 </p>
26<pre class="literallayout">
27 $ git log -p
28 </pre>
29<p>
30 You need to realize, however, that this method does show
31 changes that are not significant (e.g. a package's size
32 changing by a few bytes).
33 </p>
34<p>
35 A command-line tool called <code class="filename">buildhistory-diff</code>
36 does exist though that queries the Git repository and prints just
37 the differences that might be significant in human-readable form.
38 Here is an example:
39 </p>
40<pre class="literallayout">
41 $ ~/poky/poky/scripts/buildhistory-diff . HEAD^
42 Changes to images/qemux86_64/eglibc/core-image-minimal (files-in-image.txt):
43 /etc/anotherpkg.conf was added
44 /sbin/anotherpkg was added
45 * (installed-package-names.txt):
46 * anotherpkg was added
47 Changes to images/qemux86_64/eglibc/core-image-minimal (installed-package-names.txt):
48 anotherpkg was added
49 packages/qemux86_64-poky-linux/v86d: PACKAGES: added "v86d-extras"
50 * PR changed from "r0" to "r1"
51 * PV changed from "0.1.10" to "0.1.12"
52 packages/qemux86_64-poky-linux/v86d/v86d: PKGSIZE changed from 110579 to 144381 (+30%)
53 * PR changed from "r0" to "r1"
54 * PV changed from "0.1.10" to "0.1.12"
55 </pre>
56<p>
57 </p>
58<p>
59 To see changes to the build history using a web interface, follow
60 the instruction in the <code class="filename">README</code> file here.
61 <a class="ulink" href="http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/" target="_self">http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/</a>.
62 </p>
63<p>
64 Here is a sample screenshot of the interface:
65 </p>
66<table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="130%"><tr><td align="center"><img src="figures/buildhistory-web.png" align="middle" height="468"></td></tr></table>
67<p>
68 </p>
69</div></body>
70</html>