From fe5f742865c6578b99396ddda282c71c0a4dc557 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 25 May 2011 23:19:41 +0100 Subject: build/siggen: Ensure a task signature file is generated for each task that is executed Tracing down signature changes and dependencies is hard unless the complete task chain can be evaultated. Since we have the data available at task exeuction time, writing it to disk makes sense. This change is suboptimal internal knowledge stamp_internal() has leaks into make_stamp() and the concepts used by this code need revisiting but the change brings enough usability benefit to warrant its inclusion despite that. Addresses issue [YOCTO #1074] (Bitbake rev: 139b8a625818225c358a1b8363518d7ed6913188) Signed-off-by: Richard Purdie --- bitbake/lib/bb/siggen.py | 3 +++ 1 file changed, 3 insertions(+) (limited to 'bitbake/lib/bb/siggen.py') diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py index 494282b247..550280339c 100644 --- a/bitbake/lib/bb/siggen.py +++ b/bitbake/lib/bb/siggen.py @@ -47,6 +47,9 @@ class SignatureGenerator(object): def stampfile(self, stampbase, file_name, taskname, extrainfo): return ("%s.%s.%s" % (stampbase, taskname, extrainfo)).rstrip('.') + def dump_sigtask(self, fn, task, stampbase, runtime): + return + class SignatureGeneratorBasic(SignatureGenerator): """ """ -- cgit v1.2.3-54-g00ecf