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 --- .../eclipse/html/poky-ref-manual/debugging.html | 43 ---------------------- 1 file changed, 43 deletions(-) delete mode 100644 documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html') diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html deleted file mode 100644 index 80a19f98a4..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html +++ /dev/null @@ -1,43 +0,0 @@ - - - -3.2.4.1. Debugging - - - - - - - -
-

-3.2.4.1. Debugging

-

- When things go wrong, debugging needs to be straightforward. - Because of this, the Yocto Project team included strong debugging - tools: -

-
    -

  • Whenever a shared state package is written out, so is a - corresponding .siginfo file. - This practice results in a pickled python database of all - the metadata that went into creating the hash for a given shared state - package.

    • -

  • If BitBake is run with the --dump-signatures - (or -S) option, BitBake dumps out - .siginfo files in - the stamp directory for every task it would have executed instead of - building the specified target package.

    • -

  • There is a bitbake-diffsigs command that - can process these .siginfo files. - If one file is specified, it will dump out the dependency - information in the file. - If two files are specified, it will compare the two files and dump out - the differences between the two. - This allows the question of "What changed between X and Y?" to be - answered easily.

    • -
-

-

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