Re: [RFC] [PATCH 0/9] Initial cross-compilation support

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-06-13 15:07, Alexander Smirnov wrote:
> Hi all,
> 
> this series introduces basic cross-compilation support for Isar. The implementation
> is based around new entity - buildchroot-cross, which is quite similar to original
> buildchroot, but has host architecture.
> 
> This series tested for the following configuration only:
> 
>  $ bitbake multiconfig:qemui386
> 
> In this build:
>  - libhello is cross-compiled
>  - example-hello is compiled traditionally (but it's successfully linked with libhello)
> 
> TODO list:
>  - Depending on the target architecture, various host tools should be installed. For example
>    binutils package has the following names:
>    * binutils
>    * binutils-x86-64-linux-gnu
>    * binutils-arm-linux-gnueabihf
>  - Cross-dependency installation. This topic is still open for me because 'mk-build-deps' tool
>    doesn't work here correctly. For example package depends on binutils, but instead of
>    installation of 'binutils-arm-linux-gnueabihf' it tries to install 'binutils:armhf' and ruins
>    the rootfs.
> 
> So, as usually, comments and suggestions are welcome :-)
> 

Cool, that comes just in time! We have more and more ARM/ARM64 packages
that would benefit from the speedup.

Concrete question: What do I have to do in order to run, e.g., the
kernel build in [1] for qemuarm64 in this new cross environment?

Jan

[1] https://github.com/siemens/jailhouse-images

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux