使用armhf作为Yocto中的辅助工具链 [英] Using armhf as a secondary toolchain in Yocto

问题描述

我目前正在使用aarch64在64位模式下启动板，我有一个u-boot在32位模式，我会使用arm-linux-gnueabihf。

I am currently working on a board booting in 64 bit mode using aarch64 and I have a u-boot in 32 bit mode, I would use arm-linux-gnueabihf.

我环顾四周，但除了使用辅助工具链，没有别的办法：
open-embedded教程使用辅助工具链

I looked around but there's no other way than using a secondary toolchain via: open-embedded tutorial to use a secondary toolchain

但是，不可能使它工作。英特尔制作了一个图层（meta-tc-icc），但是它老了，我也没有设法使它工作。

Nevertheless, impossible to make it work. Intel made a layer (meta-tc-icc) but it's old and I didn't manage to make it work neither.

有什么想法如何配置？ p>

Any idea how to configure it ?

推荐答案

这里有几个方法。

你的问题是，你需要有两个machine.conf文件为这个特定的设置，构建32位U-Boot与32位机器，构建一切与64位配置和级别以上的任何控制运行bitbake确保你建立两个机器

The general answer for your problem is that you need to have two machine.conf files for this particular setup, build 32bit U-Boot with the 32bit machine, build everything else with the 64bit configuration and at the level above whatever controls running bitbake ensure that you build both machine types before passing the outputs on to whomever needs them.

一个更复杂的方法是说你使用一个全系统的工具链（你可以通过OE生成通过元工具链并安装它），然后在你的自定义U-Boot配方中，重写EXTRA_OEMAKE是你强制它使用你的工具链。

A more hacky approach would be to say that you use a system-wide toolchain (which you could have OE generate via meta-toolchain and install that) and then in your custom U-Boot recipe, override EXTRA_OEMAKE is that you force it to use your toolchain instead.

第三种方法，我意识到是不太可能，但作为U-Boot保管人我觉得我应该把平台移到64位U-Boot（或告诉供应商他们应该），我们有许多armv8平台今天和很多例子供应商谁采取他们的32位支持并添加在64位。

And a third approach, which I realize isn't likely, but as the U-Boot custodian I feel I should bring up, move the platform to 64bit U-Boot (or tell the vendor they should), we have many armv8 platforms today and lots of examples of vendors who took their 32bit support and added in 64bit.

这篇关于使用armhf作为Yocto中的辅助工具链的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！