summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/binutils/binutils-cross.inc
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2011-11-30 16:48:47 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-12-01 16:53:04 +0000
commit508ff624fea705eb93cf2cc1e0c9c42cb817acf8 (patch)
tree92f4901c7375ffb16776649ec9b8e1080dd3e295 /meta/recipes-devtools/binutils/binutils-cross.inc
parentc1bca5d95051362320008f16d8f5acd87faa34ac (diff)
downloadopenembedded-core-508ff624fea705eb93cf2cc1e0c9c42cb817acf8.tar.gz
openembedded-core-508ff624fea705eb93cf2cc1e0c9c42cb817acf8.tar.bz2
openembedded-core-508ff624fea705eb93cf2cc1e0c9c42cb817acf8.tar.xz
openembedded-core-508ff624fea705eb93cf2cc1e0c9c42cb817acf8.zip
classes/buildhistory: add new output history collection class
Create a new build output history reporting class, using testlab.bbclass from meta-oe and packagehistory.bbclass as a base. This records information from packages and images output from the build process in text files structured suitably for tracking within a git repository, thus enabling monitoring of changes over time. Build history collection can be enabled simply by adding the following to your local.conf: INHERIT += "buildhistory" The output after a build can then be found in BUILDHISTORY_DIR (defaults to TMPDIR/buildhistory). If you set up this directory as a git repository and set BUILDHISTORY_COMMIT to "1" in local.conf, the build history data will be committed on every build. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'meta/recipes-devtools/binutils/binutils-cross.inc')
0 files changed, 0 insertions, 0 deletions