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/recipe-logging-mechanisms.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/recipe-logging-mechanisms.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html | 41 |
1 files changed, 0 insertions, 41 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html deleted file mode 100644 index add1017473..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html +++ /dev/null | |||
| @@ -1,41 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>2.3.7. Recipe Logging Mechanisms</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-debugging.html" title="2.3. Debugging Build Failures"> | ||
| 9 | <link rel="prev" href="usingpoky-debugging-variables.html" title="2.3.6. Variables"> | ||
| 10 | <link rel="next" href="logging-with-python.html" title="2.3.7.1. Logging With Python"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.7. Recipe Logging Mechanisms"> | ||
| 13 | <div class="titlepage"><div><div><h3 class="title"> | ||
| 14 | <a name="recipe-logging-mechanisms"></a>2.3.7. Recipe Logging Mechanisms</h3></div></div></div> | ||
| 15 | <p> | ||
| 16 | Best practices exist while writing recipes that both log build progress and | ||
| 17 | act on build conditions such as warnings and errors. | ||
| 18 | Both Python and Bash language bindings exist for the logging mechanism: | ||
| 19 | </p> | ||
| 20 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
| 21 | <li class="listitem"><p><span class="emphasis"><em>Python:</em></span> For Python functions, BitBake | ||
| 22 | supports several loglevels: <code class="filename">bb.fatal</code>, | ||
| 23 | <code class="filename">bb.error</code>, <code class="filename">bb.warn</code>, | ||
| 24 | <code class="filename">bb.note</code>, <code class="filename">bb.plain</code>, | ||
| 25 | and <code class="filename">bb.debug</code>.</p></li> | ||
| 26 | <li class="listitem"><p><span class="emphasis"><em>Bash:</em></span> For Bash functions, the same set | ||
| 27 | of loglevels exist and are accessed with a similar syntax: | ||
| 28 | <code class="filename">bbfatal</code>, <code class="filename">bberror</code>, | ||
| 29 | <code class="filename">bbwarn</code>, <code class="filename">bbnote</code>, | ||
| 30 | <code class="filename">bbplain</code>, and <code class="filename">bbdebug</code>.</p></li> | ||
| 31 | </ul></div> | ||
| 32 | <p> | ||
| 33 | </p> | ||
| 34 | <p> | ||
| 35 | For guidance on how logging is handled in both Python and Bash recipes, see the | ||
| 36 | <code class="filename">logging.bbclass</code> file in the | ||
| 37 | <code class="filename">meta/classes</code> folder of the | ||
| 38 | <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>. | ||
| 39 | </p> | ||
| 40 | </div></body> | ||
| 41 | </html> | ||