summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/binutils
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2016-02-12 09:37:15 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-02-15 17:47:08 +0000
commitda13f0bce5d1b3c52f5716ae8d104372a820e5f9 (patch)
treeef08feb4936523ad98b22a27151aeac007a6b3c8 /meta/recipes-devtools/binutils
parenta56da4a0fc792c854d1201b22969dc48fe437a0b (diff)
downloadpoky-da13f0bce5d1b3c52f5716ae8d104372a820e5f9.tar.gz
buildhistory.bbclass: remove out-dated information on request
buildhistory.bbclass by design is incremental: each build adds or updates information. Information is never removed. Sometimes it can be useful to reduce the information only to those recipes that were build during a specific bitbake invocation, for example when the invocation does a full world build. This is now possible by setting BUILDHISTORY_RESET as explained in the modified class. The comment on the variable also mentions the caveats associated with using this mode. In this mode, buildhistory.bbclass first moves all existing information into a temporary directory called "old" inside the build history directory. There the information is used for the "version going backwards" QA check. Then when the build is complete and before (potentially) committing to git, the temporary directory gets deleted. Because information that has not changed during the build will be reconstructed during full world rebuilds, a git log will then only show real updates, additions and removals. (From OE-Core rev: 51f4eb5bfcd25f7160e50314f433cad126aa3e9a) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/binutils')
0 files changed, 0 insertions, 0 deletions