From 34f4a9d8b7ba575759956ac99ac4f5509468a530 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 27 Mar 2014 15:35:43 +0000 Subject: [PATCH] bitbake: user-manual-execution.xml: Updated "Checksum (Signatures) section. Fixes [YOCTO #5357] Added a paragraph at the end of this section to address the fact that the user can now debug Bitbake's processing of signatures. This introduces the -S bitbake option and the fact that the user can provide a couple parameters with it: "none" and "printdiff". (Bitbake rev: 4093fa6c96eebe0bbafb93dc27d8a978cca436c4) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../doc/user-manual/user-manual-execution.xml | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/bitbake/doc/user-manual/user-manual-execution.xml b/bitbake/doc/user-manual/user-manual-execution.xml index a67516e858..d5a288c03f 100644 --- a/bitbake/doc/user-manual/user-manual-execution.xml +++ b/bitbake/doc/user-manual/user-manual-execution.xml @@ -750,6 +750,30 @@ + + It is worth noting that BitBake's "-S" option lets you + debug Bitbake's processing of signatures. + The options passed to -S allow different debugging modes + to be used, either using BitBake's own debug functions + or possibly those defined in the metadata/signature handler + itself. + The simplest parameter to pass is "none", which causes a + set of signature information to be written out into + STAMP_DIR + corresponding to the targets specified. + The other currently available parameter is "printdiff", + which causes BitBake to try to establish the closest + signature match it can (e.g. in the sstate cache) and then + run bitbake-diffsigs over the matches + to determine the stamps and delta where these two + stamp trees diverge. + + It is likely that future versions of BitBake with + provide other signature handlers triggered through + additional "-S" paramters. + + + You can find more information on checksum metadata in the "Task Checksums and Setscene"