path: root/meta/classes
diff options
authorRandy Witt <randy.e.witt@linux.intel.com>2016-05-01 17:13:02 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-05-09 08:03:59 +0100
commit6ba86d847275126bf435f144e7d029d10e7ab17d (patch)
tree2d5df2c6a0ebfea6003a0b12183b6c914cb76803 /meta/classes
parent7fc6e5e816434fb6e35c137d5440b92a1cc4d9c2 (diff)
populate_sdk_ext: Change lockedsigs task mismatch to a warning
It has been determined that it is highly likely that users might get signatures that don't match in an extensible sdk. This doesn't necessarily happen with oe-core, so we can set the mismatch to an error during testing if we like. However, for the case where users are creating their own sdks, we don't need an error halting their progress. locked-sigs will still function as it should. Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/classes')
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass
index 902bd7a885..6d8edca16d 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -221,7 +221,7 @@ python copy_buildsystem () {
# Error if the sigs in the locked-signature file don't match
# the sig computed from the metadata.
- f.write('SIGGEN_LOCKEDSIGS_TASKSIG_CHECK = "error"\n\n')
+ f.write('SIGGEN_LOCKEDSIGS_TASKSIG_CHECK = "warn"\n\n')
# Hide the config information from bitbake output (since it's fixed within the SDK)
f.write('BUILDCFG_HEADER = ""\n')