meta_%.bbappend: Avoid contaminating mesa-native PACKAGECONFIG

Adding meta-xilinx-core was contaminating the PACKAGECONFIG hash when
building mesa-native.  Workaround this by only adjusting the value
when class-target is defined.

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

1 files changed, 1 insertions, 1 deletions

diff --git a/meta-xilinx-core/recipes-graphics/mesa/mesa_%.bbappend b/meta-xilinx-core/recipes-graphics/mesa/mesa_%.bbappend
index 1b2230f7..8c0e7898 100644
--- a/meta-xilinx-core/recipes-graphics/mesa/mesa_%.bbappend
+++ b/meta-xilinx-core/recipes-graphics/mesa/mesa_%.bbappend
@@ -6,7 +6,7 @@ CONFLICT_DISTRO_FEATURES:class-target = "${@bb.utils.contains('MACHINE_FEATURES'
 
 # Enable lima if not using libmali
 PACKAGECONFIG_MALI = "${@bb.utils.contains('DISTRO_FEATURES', 'libmali', '', 'lima', d)}"
-PACKAGECONFIG:append = "${@bb.utils.contains('MACHINE_FEATURES', 'mali400', '${PACKAGECONFIG_MALI}', '', d)}"
+PACKAGECONFIG:append:class-target = "${@bb.utils.contains('MACHINE_FEATURES', 'mali400', '${PACKAGECONFIG_MALI}', '', d)}"
 
 PACKAGE_ARCH_DEFAULT := "${PACKAGE_ARCH}"
 PACKAGE_ARCH = "${@bb.utils.contains('MACHINE_FEATURES', 'mali400', '${MACHINE_ARCH}', '${PACKAGE_ARCH_DEFAULT}', d)}"