On Wed, 2020-01-08 at 17:19 +0000, Ross Burton wrote: > 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.
FWIW this is continuing to cause selftest failures, despite my patch :( https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/610 Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
