summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/doc/user-manual/user-manual-execution.xml24
1 files changed, 24 insertions, 0 deletions
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
@@ -751,6 +751,30 @@
751 </para> 751 </para>
752 752
753 <para> 753 <para>
754 It is worth noting that BitBake's "-S" option lets you
755 debug Bitbake's processing of signatures.
756 The options passed to -S allow different debugging modes
757 to be used, either using BitBake's own debug functions
758 or possibly those defined in the metadata/signature handler
759 itself.
760 The simplest parameter to pass is "none", which causes a
761 set of signature information to be written out into
762 <filename>STAMP_DIR</filename>
763 corresponding to the targets specified.
764 The other currently available parameter is "printdiff",
765 which causes BitBake to try to establish the closest
766 signature match it can (e.g. in the sstate cache) and then
767 run <filename>bitbake-diffsigs</filename> over the matches
768 to determine the stamps and delta where these two
769 stamp trees diverge.
770 <note>
771 It is likely that future versions of BitBake with
772 provide other signature handlers triggered through
773 additional "-S" paramters.
774 </note>
775 </para>
776
777 <para>
754 You can find more information on checksum metadata in the 778 You can find more information on checksum metadata in the
755 "<link linkend='task-checksums-and-setscene'>Task Checksums and Setscene</link>" 779 "<link linkend='task-checksums-and-setscene'>Task Checksums and Setscene</link>"
756 section. 780 section.