meta-xilinx-standalone: Prevent user error, when meta-microblaze is required

When the user chooses to build a microblaze target, the compiler can fail
to patch properly as a symptom.  Users may think it's a simple patch failure,
but really they forgot to include the meta-microblaze layer itself.

Declare the meta-microblaze layer as a recommended layer, and verify in the
gcc-source bbappend that it has been included, if a microblaze target is being
built.

Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>

1 files changed, 8 insertions, 0 deletions

diff --git a/meta-xilinx-standalone/recipes-devtools/gcc/gcc-source_10.%.bbappend b/meta-xilinx-standalone/recipes-devtools/gcc/gcc-source_10.%.bbappend
index e1876700..d3abc611 100644
--- a/meta-xilinx-standalone/recipes-devtools/gcc/gcc-source_10.%.bbappend
+++ b/meta-xilinx-standalone/recipes-devtools/gcc/gcc-source_10.%.bbappend
@@ -5,3 +5,11 @@ FILESEXTRAPATHS_append_microblaze_xilinx-standalone := ":${THISDIR}/gcc-10"
 SRC_URI_append_microblaze_xilinx-standalone = " \
         file://additional-microblaze-multilibs.patch \
 "
+
+CHECK_FOR_MICROBLAZE_microblaze = "1"
+
+python() {
+    if d.getVar('CHECK_FOR_MICROBLAZE') == '1':
+        if 'xilinx-microblaze' not in d.getVar('BBFILE_COLLECTIONS').split():
+            bb.fatal('You must include the meta-microblaze layer to build for this configuration.')
+}