Skip to contentSkip to conversation

glib: support target/os/libc-specific Meson cross files

PATCH In review Ross Burton 2 participants 2 messages Jan 8, 2020 – Jan 10, 2020 Arm/Amlogic Meson SoC support

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 glib: support target/os/libc-specific Meson cross files

Build systems have a common problem that some tests can only be done by executing a piece of test code (compared to just compiling or linking test code). In a cross-compilation the execution of this code isn't possible and the Meson solution to this is to allow 'cross properties' to be specified in the cross files.

GLib has a number of these, for example determining the direction the stack grows, whether /proc/self/cmdline exists, or the behaviour of snprintf(). Previously we'd passed values for these to the Glib build for target builds, but this misses out nativesdk builds (which are also cross-compiled) and the fact that some of these values are specific to the platform, some are specific to the host OS, and some are specific to the libc implementation.

This problem has already been solved for autotools with the siteinfo class, which turns the target platform/OS/libc variables into filenames (such as common common-linux common-glibc). We can look for these in FILESDIR and use them as cross files.

Assuming that there are no problems with this appoach it can be moved into meson.bbclass so that all Meson recipes can use it for their cross files.

---
 .../glib-2.0/glib-2.0/meson.cross.d/common    |  3 +++
 .../common-glibc}                             |  5 ----
 .../glib-2.0/meson.cross.d/common-linux       |  5 ++++
 .../glib-2.0/meson.cross.d/common-mingw       |  6 +++++
 .../glib-2.0/meson.cross.d/common-musl        |  6 +++++
 meta/recipes-core/glib-2.0/glib-2.0_2.62.4.bb | 26 ++++++++++++++++++-
 meta/recipes-core/glib-2.0/glib.inc           |  1 -
 7 files changed, 45 insertions(+), 7 deletions(-)
 create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common
 rename meta/recipes-core/glib-2.0/glib-2.0/{glib-meson.cross => meson.cross.d/common-glibc} (56%)
 create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-linux
 create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-mingw
 create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-musl
meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common new file +3 -0
new file mode 100644
index 00000000000..0d7c5fa3f8c
@@ -0,0 +1,3 @@
+[properties]
+# On all known supported architectures the stack grows down
+growing_stack = false
meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-glibc renamed from meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross +0 -5
similarity index 56%
rename from meta/recipes-core/glib-2.0/glib-2.0/glib-meson.cross
rename to meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-glibc
index 5246c776014..c4648f58c78 100644
@@ -3,8 +3,3 @@ have_c99_vsnprintf = true
 have_c99_snprintf = true
 have_unix98_printf = true
 va_val_copy = true
-growing_stack = false
-have_proc_self_cmdline = true
-
-[binaries]
-env = "/usr/bin/env"
meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-linux new file +5 -0
new file mode 100644
index 00000000000..83596e0efbb
@@ -0,0 +1,5 @@
+[properties]
+have_proc_self_cmdline = true
+
+[binaries]
+env = "/usr/bin/env"
meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-mingw new file +6 -0
new file mode 100644
index 00000000000..75f911ba1ed
@@ -0,0 +1,6 @@
+[properties]
+have_c99_vsnprintf = false
+have_c99_snprintf = false
+have_unix98_printf = false
+va_val_copy = true
+have_proc_self_cmdline = false
meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-musl new file +6 -0
new file mode 100644
index 00000000000..3049e5116ec
@@ -0,0 +1,6 @@
+[properties]
+have_c99_vsnprintf = true
+have_c99_snprintf = true
+have_unix98_printf = true
+va_val_copy = true
+have_strlcpy = true
meta/recipes-core/glib-2.0/glib-2.0_2.62.4.bb +25 -1
index 7bf8648cade..953fba501a7 100644
@@ -18,7 +18,31 @@ SRC_URI = "${GNOME_MIRROR}/glib/${SHRT_VER}/glib-${PV}.tar.xz \
            "
 
 SRC_URI_append_class-native = " file://relocate-modules.patch"
-SRC_URI_append_class-target = " file://glib-meson.cross"
 
 SRC_URI[md5sum] = "d52234ecba128932bed90bbc3553bfe5"
 SRC_URI[sha256sum] = "4c84030d77fa9712135dfa8036ad663925655ae95b1d19399b6200e869925bbc"
+
+# Find any meson cross files in FILESPATH that are relevant for the current
+# build (using siteinfo) and add them to EXTRA_OEMESON.
+inherit siteinfo
+def find_meson_cross_files(d):
+    if bb.data.inherits_class('native', d):
+        return ""
+
+    import collections
+    sitedata = siteinfo_data(d)
+    # filename -> found
+    files = collections.OrderedDict()
+    for path in d.getVar("FILESPATH").split(":"):
+        for element in sitedata:
+            filename = os.path.join(path, "meson.cross.d", element)
+            files[filename] = os.path.exists(filename)
+
+    items = ["--cross-file=" + k for k,v in files.items() if v]
+    d.appendVar("EXTRA_OEMESON", " " + " ".join(items))
+    items = ["%s:%s" % (k, "True" if v else "False") for k,v in files.items()]
+    d.appendVarFlag("do_configure", "file-checksums", " " + " ".join(items))
+
+python () {
+    find_meson_cross_files(d)
+}
meta/recipes-core/glib-2.0/glib.inc +0 -1
index e811b42d773..f4aff297e57 100644
@@ -49,7 +49,6 @@ PACKAGECONFIG[libelf] = ",,elfutils"
 PACKAGECONFIG[tests] = "-Dinstalled_tests=true,-Dinstalled_tests=false,dbus"
 
 EXTRA_OEMESON = "-Ddtrace=false -Dfam=false -Dsystemtap=false -Dselinux=disabled"
-EXTRA_OEMESON_append_class-target = " --cross-file ${WORKDIR}/glib-meson.cross"
 
 do_configure_prepend() {
 	sed -i -e '1s,#!.*,#!${USRBINPATH}/env python3,' ${S}/gio/gdbus-2.0/codegen/gdbus-codegen.in
Signature · 1 line
2.20.1
#1 lore raw
Quoted 30 lines · Ross Burton

Build systems have a common problem that some tests can only be done by
executing a piece of test code (compared to just compiling or linking test
code). In a cross-compilation the execution of this code isn't possible and the
Meson solution to this is to allow 'cross properties' to be specified in the
cross files.

GLib has a number of these, for example determining the direction the stack
grows, whether /proc/self/cmdline exists, or the behaviour of snprintf().
Previously we'd passed values for these to the Glib build for target builds, but
this misses out nativesdk builds (which are also cross-compiled) and the fact
that some of these values are specific to the platform, some are specific to the
host OS, and some are specific to the libc implementation.

This problem has already been solved for autotools with the siteinfo class,
which turns the target platform/OS/libc variables into filenames (such as common
common-linux common-glibc). We can look for these in FILESDIR and use them as
cross files.

Quoted 4 lines

Assuming that there are no problems with this appoach it can be moved into
meson.bbclass so that all Meson recipes can use it for their cross files.

FWIW this is continuing to cause selftest failures, despite my patch :(

https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/610

Cheers,

Richard