summaryrefslogtreecommitdiffstats
path: root/meta
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-16 10:46:05 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-03-16 10:51:17 +0000
commit4ca7075b0972163d95e3c3f5a40c602bf3bb0245 (patch)
treefb43857313251a7d1829393092c5e07de260abc9 /meta
parent1d52c11bf34855bce450bcb2f8651fdaf2d90196 (diff)
downloadpoky-4ca7075b0972163d95e3c3f5a40c602bf3bb0245.tar.gz
runqueue.py: When checking whether stamps are valid for setscene, recurse
Currently the code checking whether stamps are valid only traverses one step of the dependency graph. This works fine in the normal cases where we've already validated dependencies but for the setscene code, it doesn't work well. A typical problem usecase is something like: bitbake gcc-cross -c unpack -f bitbake gcc-cross which will ignore any sstate files already cached which could be used to speed up the gcc-cross build. This becomes particularly problematic with multiple gcc builds where only one should rebuild yet they all do. This patch teaches the stamp code to be able to recurse within a given fn which gives the behaviour people would expect from the code and allows bitbake to make better use of prebuild sstate objects. (Bitbake rev: e68814cb2e8da523d4ddf05e8ceddfaa19244851) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta')
0 files changed, 0 insertions, 0 deletions