On Thu, 2017-12-07 at 11:27 -0800, Andre McCurdy wrote: > On Fri, Nov 17, 2017 at 4:02 AM, Alexander Kanavin > <alexander.kana...@linux.intel.com> wrote: > > + > > +MESON_HOST_ENDIAN = "${@bb.utils.contains('SITEINFO_ENDIANNESS', 'be', > > 'big', 'little', d)}" > > SITEINFO_ENDIANNESS returns the endianness of the target, not the > host.
Isn't the host what you call target? When cross-compiling, the host machine normally refers to the system where the built programs will be run, and target machine to where the a compiler will run, in case a compiler is being (cross-)compiled. ${MESON_HOST_ENDIAN} is used inside the [host_machine] statement, so this looks right. > [...] > > > +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. ${MESON_TARGET_ENDIAN} is used inside a [target_machine] statement, though. Not sure about the naming and intention here... Cheers, Andre' -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core