When passing the wrong value for UBOOT_CONFIG it ought to raise an
error otherwise it is quite difficult for user to notice it didn't
behave as expected.
Reported-by: Lauren Post <lauren.p...@freescale.com>
Signed-off-by: Otavio Salvador <ota...@ossystems.com.br>
---
Changes in v2:
- Use ValueError as exception
meta/classes/uboot-config.bbclass | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/meta/classes/uboot-config.bbclass
b/meta/classes/uboot-config.bbclass
index ba01bff..5068f49 100644
--- a/meta/classes/uboot-config.bbclass
+++ b/meta/classes/uboot-config.bbclass
@@ -51,4 +51,9 @@ python () {
if len(items) > 1 and items[1]:
bb.debug(1, "Appending '%s' to IMAGE_FSTYPES." % items[1])
d.appendVar('IMAGE_FSTYPES', ' ' + items[1])
+
+ # Go out as we found a match!
+ break
+ else:
+ raise ValueError("UBOOT_CONFIG %s is not supported" % ubootconfig)
}
--
1.8.4.rc3
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
