diff options
author | Chris Larson <chris_larson@mentor.com> | 2010-07-26 08:57:57 -0700 |
---|---|---|
committer | Chris Larson <chris_larson@mentor.com> | 2010-07-26 08:57:57 -0700 |
commit | bbc3d4827417d047094b4faafdda9dd2f50422ff (patch) | |
tree | 8e73b01a2f0f7b179405618a9fb9d3cc04f83bf3 | |
parent | 181244a3a629b6dacd5f221f9e9380ba9a078bb0 (diff) |
sanity.bbclass: Run our checking at BuildStarted, not ConfigParsed
ConfigParsed is often utilized to do programmatic changes to the configuration
metadata. If these other event handlers set any variables which
sanity.bbclass needs to check, there's a problem, since we can't ensure those
handlers run before this one. So, we move the sanity checking to when the
build is about to start, this ensures that the configuration metadata is
entirely ready to go.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
-rw-r--r-- | classes/sanity.bbclass | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/classes/sanity.bbclass b/classes/sanity.bbclass index cff415a812..1fd5fbb216 100644 --- a/classes/sanity.bbclass +++ b/classes/sanity.bbclass @@ -188,8 +188,8 @@ def check_sanity(e): if messages != "": raise_sanity_error(messages) -addhandler check_sanity_eventhandler python check_sanity_eventhandler() { - if bb.event.getName(e) == "ConfigParsed": + if isinstance(e, bb.event.BuildStarted): check_sanity(e) } +addhandler check_sanity_eventhandler |