I've been working to enable putting a cross-compiler on a regular Yocto target (as opposed to SDKs), and these are the changes needed in oe-core to enable that.
Two of them swap TARGET for HOST (the terminology is set by the GNU project, it is confusing, but it still needs to be followed), one allows populating the native sysroot of a target recipe with the output of two different cross recipes building for different TARGETs. The actual cross-compiler is available from here, please refer to the README: https://github.com/kanavin/meta-cross-toolchain The plan is to further investigate what happens inside gcc's build system so that the way that layer works can be better aligned with oe-core. Alexander Kanavin (3): base/staging: use HOST_PREFIX, not TARGET_PREFIX sstate: do not add TARGET_ARCH to pkgarch for cross recipes. insane: use HOST_ variables, not TARGET_ to determine the cross system meta/classes/base.bbclass | 2 +- meta/classes/insane.bbclass | 8 ++++---- meta/classes/sstate.bbclass | 3 +-- meta/classes/staging.bbclass | 4 ++-- meta/lib/oe/sstatesig.py | 2 +- 5 files changed, 9 insertions(+), 10 deletions(-) -- 2.20.1
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162315): https://lists.openembedded.org/g/openembedded-core/message/162315 Mute This Topic: https://lists.openembedded.org/mt/89366541/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
