Define COMPATIBLE_HOST to prevent mix of Linux and Baremetal recipes

The key is using COMPATIBLE_HOST to declare, for each recipe, which
OS they are compatible with.  This is a regex, so we need to
carefully specify the arch/vendor wild cardscomponents so that we match
only the OS parts.

In the distro configuration, default to the standard Linux HOST_SYS
setting.

In the various baremetal recipes (or esw class) set the specific
compatibility to allow baremetal recipes to build.

Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>

1 files changed, 7 insertions, 0 deletions

diff --git a/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc b/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc
index 18ce4da6..5c8ae67a 100644
--- a/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc
+++ b/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc
@@ -24,6 +24,13 @@ INHERIT += "buildhistory"
 # Cortex R5 requires an additional cflag to be passed for compatibility with the embeddedsw
 TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexr5', ' -DARMR5', '', d)}"
 
+# Make sure all regular recipes are excluded from compatibility
+# Avoid using this for native, nativesdk or cross recipes
+COMPATOS = ""
+# Set the regex for target recipes only, follow TARGET_OS default
+COMPATOS_class-target = ".*-linux${LIBCEXTENSION}${ABIEXTENSION}"
+COMPATIBLE_HOST ?= "${COMPATOS}"
+
 # Clear defaults
 DISTRO_FEATURES_BACKFILL_xilinx-standalone = ""
 VIRTUAL-RUNTIME_init_manager_xilinx-standalone = ""