Hi Ross, According to https://mesonbuild.com/Cross-compilation.html
There are two different values for the CPU. The first one is cpu_family. It is a general type of the CPU. This should have a value from the CPU Family table <https://mesonbuild.com/Reference-tables.html#cpu-families>. *Note* that meson does not add el to end cpu_family value for little endian systems. Big endian and little endian mips are both just mips, with the endian field set approriately. The second value is cpu which is a more specific subtype for the CPU. Typical values for a x86 CPU family might include i386 or i586 and for arm family armv5 or armv7hl. Note that CPU type strings are very system dependent. You might get a different value if you check its value on the same machine but with different operating systems. At the moment both 'cpu_family' and 'cpu' are being set to TARGET_ARCH (like x86_64) in meson cross file. TUNE_CCARSG usually contains the exact subfamily either as -march= or -mcpu= The meson_cpu function will use regex to search for -march and if that's missing for -mcpu value. If both flags are missing it defaults to TARGET_ARCH. Ruslan On Mon, Jul 27, 2020 at 3:52 AM Ross Burton <[email protected]> wrote: > On Sun, 26 Jul 2020 at 02:56, Ruslan Babayev <[email protected]> wrote: > > 'cpu' unlike 'cpu_family' must be a more specific subtype for the CPU. > > Can you elaborate here some more? > > Ross >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#141011): https://lists.openembedded.org/g/openembedded-core/message/141011 Mute This Topic: https://lists.openembedded.org/mt/75796683/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
