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/usingpoky-debugging-taskrunning.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/usingpoky-debugging-taskrunning.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html | 68 |
1 files changed, 0 insertions, 68 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html deleted file mode 100644 index 998d9d03c7..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html +++ /dev/null | |||
| @@ -1,68 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>2.3.2. Running Specific Tasks</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-taskfailures.html" title="2.3.1. Task Failures"> | ||
| 10 | <link rel="next" href="usingpoky-debugging-dependencies.html" title="2.3.3. Dependency Graphs"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.2. Running Specific Tasks"> | ||
| 13 | <div class="titlepage"><div><div><h3 class="title"> | ||
| 14 | <a name="usingpoky-debugging-taskrunning"></a>2.3.2. Running Specific Tasks</h3></div></div></div> | ||
| 15 | <p> | ||
| 16 | Any given package consists of a set of tasks. | ||
| 17 | The standard BitBake behavior in most cases is: <code class="filename">fetch</code>, | ||
| 18 | <code class="filename">unpack</code>, | ||
| 19 | <code class="filename">patch</code>, <code class="filename">configure</code>, | ||
| 20 | <code class="filename">compile</code>, <code class="filename">install</code>, <code class="filename">package</code>, | ||
| 21 | <code class="filename">package_write</code>, and <code class="filename">build</code>. | ||
| 22 | The default task is <code class="filename">build</code> and any tasks on which it depends | ||
| 23 | build first. | ||
| 24 | Some tasks exist, such as <code class="filename">devshell</code>, that are not part of the | ||
| 25 | default build chain. | ||
| 26 | If you wish to run a task that is not part of the default build chain, you can use the | ||
| 27 | <code class="filename">-c</code> option in BitBake as follows: | ||
| 28 | </p> | ||
| 29 | <pre class="literallayout"> | ||
| 30 | $ bitbake matchbox-desktop -c devshell | ||
| 31 | </pre> | ||
| 32 | <p> | ||
| 33 | </p> | ||
| 34 | <p> | ||
| 35 | If you wish to rerun a task, use the <code class="filename">-f</code> force option. | ||
| 36 | For example, the following sequence forces recompilation after changing files in the | ||
| 37 | working directory. | ||
| 38 | </p> | ||
| 39 | <pre class="literallayout"> | ||
| 40 | $ bitbake matchbox-desktop | ||
| 41 | . | ||
| 42 | . | ||
| 43 | [make some changes to the source code in the working directory] | ||
| 44 | . | ||
| 45 | . | ||
| 46 | $ bitbake matchbox-desktop -c compile -f | ||
| 47 | $ bitbake matchbox-desktop | ||
| 48 | </pre> | ||
| 49 | <p> | ||
| 50 | </p> | ||
| 51 | <p> | ||
| 52 | This sequence first builds <code class="filename">matchbox-desktop</code> and then recompiles it. | ||
| 53 | The last command reruns all tasks (basically the packaging tasks) after the compile. | ||
| 54 | BitBake recognizes that the <code class="filename">compile</code> task was rerun and therefore | ||
| 55 | understands that the other tasks also need to be run again. | ||
| 56 | </p> | ||
| 57 | <p> | ||
| 58 | You can view a list of tasks in a given package by running the | ||
| 59 | <code class="filename">listtasks</code> task as follows: | ||
| 60 | </p> | ||
| 61 | <pre class="literallayout"> | ||
| 62 | $ bitbake matchbox-desktop -c listtasks | ||
| 63 | </pre> | ||
| 64 | <p> | ||
| 65 | The results are in the file <code class="filename">${WORKDIR}/temp/log.do_listtasks</code>. | ||
| 66 | </p> | ||
| 67 | </div></body> | ||
| 68 | </html> | ||