From a41a805500cab281fba15bd8e5d3e60b88d0d4be Mon Sep 17 00:00:00 2001 From: Timo Mueller Date: Fri, 8 Feb 2013 09:16:33 -0600 Subject: 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 Signed-off-by: Richard Purdie --- .../usingpoky-debugging-taskrunning.html | 68 ---------------------- 1 file changed, 68 deletions(-) delete mode 100644 documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html') 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 @@ - - - -2.3.2. Running Specific Tasks - - - - - - - -
-

-2.3.2. Running Specific Tasks

-

- Any given package consists of a set of tasks. - The standard BitBake behavior in most cases is: fetch, - unpack, - patch, configure, - compile, install, package, - package_write, and build. - The default task is build and any tasks on which it depends - build first. - Some tasks exist, such as devshell, that are not part of the - default build chain. - If you wish to run a task that is not part of the default build chain, you can use the - -c option in BitBake as follows: -

-
-     $ bitbake matchbox-desktop -c devshell
-
-

-

-

- If you wish to rerun a task, use the -f force option. - For example, the following sequence forces recompilation after changing files in the - working directory. -

-
-     $ bitbake matchbox-desktop
-               .
-               .
-        [make some changes to the source code in the working directory]
-               .
-               .
-     $ bitbake matchbox-desktop -c compile -f
-     $ bitbake matchbox-desktop
-
-

-

-

- This sequence first builds matchbox-desktop and then recompiles it. - The last command reruns all tasks (basically the packaging tasks) after the compile. - BitBake recognizes that the compile task was rerun and therefore - understands that the other tasks also need to be run again. -

-

- You can view a list of tasks in a given package by running the - listtasks task as follows: -

-
-     $ bitbake matchbox-desktop -c listtasks
-
-

- The results are in the file ${WORKDIR}/temp/log.do_listtasks. -

-
- -- cgit v1.2.3-54-g00ecf