When things go wrong, debugging needs to be straightforward. Because of this, the Yocto Project includes 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 you run BitBake 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 .siginfo
files.
If you specify one of these files, BitBake dumps out the dependency
information in the file.
If you specify two files, BitBake compares the two files and dumps out
the differences between the two.
This more easily helps answer the question of "What
changed between X and Y?"