summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.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/usingpoky-debugging.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/usingpoky-debugging.html')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html26
1 files changed, 0 insertions, 26 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html
deleted file mode 100644
index 9a8b72dc96..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html
+++ /dev/null
@@ -1,26 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3. Debugging Build Failures</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-install.html" title="2.2. Installing and Using the Result">
10<link rel="next" href="usingpoky-debugging-taskfailures.html" title="2.3.1. Task Failures">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3. Debugging Build Failures">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="usingpoky-debugging"></a>2.3. Debugging Build Failures</h2></div></div></div>
15<p>
16 The exact method for debugging build failures depends on the nature of the
17 problem and on the system's area from which the bug originates.
18 Standard debugging practices such as comparison against the last
19 known working version with examination of the changes and the re-application of steps
20 to identify the one causing the problem are
21 valid for the Yocto Project just as they are for any other system.
22 Even though it is impossible to detail every possible potential failure,
23 this section provides some general tips to aid in debugging.
24 </p>
25</div></body>
26</html>