On 12/07/2017 09:27 PM, Andre McCurdy wrote:
On Fri, Nov 17, 2017 at 4:02 AM, Alexander Kanavin <[email protected]> wrote:+ +MESON_HOST_ENDIAN = "${@bb.utils.contains('SITEINFO_ENDIANNESS', 'be', 'big', 'little', d)}"SITEINFO_ENDIANNESS returns the endianness of the target, not the host. Perhaps this is just a confusingly named variable though? (it doesn't make much sense to expect the user to tell the build system what endianness it's running on, the build system should be able to determine that on it's own).+MESON_TARGET_ENDIAN = "${@bb.utils.contains('TUNE_FEATURES', 'bigendian', 'big', 'little', d)}"This won't work for all targets (e.g. PowerPC is big endian but doesn't include "bigendian" in TUNE_FEATURES). To determine the endianness of the target, use SITEINFO_ENDIANNESS instead.
I have reviewed the source code of meson for uses of the endian parameter and couldn't find any whatsoever. Its presence in config file is however enforced. I'll set both of these to 'bogus-endian' and see if that makes any difference.
Alex -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
