xilinx-standalone.inc: Sync with poky distro settings

Certain settings appear to have an overall affect on recipe hashes. Use
petalinux (poky) distro as an example for base settings to ensure native
items built in one config SHOULD also be re-usable in the bareemetal config.

This has a side effect of NOT disabling static binaries in baremetal, but
this seems like a reasonable default, since there really isn't a concept
of dynamically loaded libraries.  If necessary, the user can still override
this, but will need to specifically select class-target to do so.

Similarly SECURITY_CFLAGS and SECURITY_LDFLAGS are available by empty by
default.  The default cflags/ldflags for baremetal usage are likely
different from a Linux system, so can be used in the future if requried.

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

1 files changed, 18 insertions, 0 deletions

diff --git a/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc b/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc
index 57fbf956..ec490d26 100644
--- a/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc
+++ b/meta-xilinx-standalone/conf/distro/xilinx-standalone.inc
@@ -45,3 +45,21 @@ TOOLCHAIN_NEED_CONFIGSITE_CACHE = ""
 
 # Workaround for pulling in nativesdk-mingw-w64-winpthreads
 TOOLCHAIN_HOST_TASK:append:sdkmingw32 = " nativesdk-mingw-w64-winpthreads"
+
+# Disable static for all classes, except for target.  This will ensure we can
+# share more recipe hashes with other distros, while still building
+# static binaries for baremetal targets (by default).  The user can of course
+# still override this, but will need to specifically select class-target to
+# do so.
+DISABLE_STATIC:class-target ?= ""
+
+SECURITY_CFLAGS:class-target ?= ""
+SECURITY_LDFLAGS:class-target ?= ""
+
+require conf/distro/include/no-static-libs.inc
+require conf/distro/include/yocto-uninative.inc
+require conf/distro/include/security_flags.inc
+INHERIT += "uninative"
+
+BB_SIGNATURE_HANDLER ?= "OEEquivHash"
+BB_HASHSERVE ??= "auto"