From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH] isar-events: Hook into BuildStarted for task-once cleanup
Date: Tue, 5 Nov 2019 18:23:34 +0100 [thread overview]
Message-ID: <a4fbd504-90d7-b6d4-8b46-74f8d71ec587@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
The Parse* events are unfortunately only fired when there is no cache.
Hooking into the BuildStarted does not have this shortcoming, just
implies multiple events (one per multiconfig), but that is harmless.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/classes/isar-events.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/classes/isar-events.bbclass b/meta/classes/isar-events.bbclass
index cad1d57..4c49635 100644
--- a/meta/classes/isar-events.bbclass
+++ b/meta/classes/isar-events.bbclass
@@ -4,12 +4,12 @@
# Copyright (C) 2015-2017 ilbers GmbH
# Copyright (c) Siemens AG, 2018
-addhandler parse_completed
+addhandler build_started
-python parse_completed() {
+python build_started() {
bb.utils.remove(d.getVar('TMPDIR') + "/work/*/*/*/temp/once.*")
}
-parse_completed[eventmask] = "bb.event.ParseCompleted"
+build_started[eventmask] = "bb.event.BuildStarted"
def task_once_stamp(d):
return "{temp}/once.{task}".format(temp=d.getVar('T'),
--
2.16.4
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next reply other threads:[~2019-11-05 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 17:23 Jan Kiszka [this message]
2019-11-08 13:56 ` Jan Kiszka
2019-11-13 12:29 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4fbd504-90d7-b6d4-8b46-74f8d71ec587@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox