Ross Burton
01a13b11ad
For reasons, hafnium doesn't use host binaries for stuff like GN, Ninja, Clang, GCC, or Qemu. Instead it ships binaries that it uses during the build, but these binaries are only available for x86-64. Attempts to use external tools (so the recipe can just DEPENDS as usual) were not successful (clang being the problem) so just forcible stop the recipe building on anything but x86-64 for now. Change-Id: I144309d15fa1265b2b105981cd2bfcd376aab7ad Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
Introduction
This repository contains Arm layers for OpenEmbedded
meta-arm: This layer provides support for general recipes for the Arm architecture. Anything that's not needed explicitly for BSPs, the IOTA distribution, or destined to be upstreamed belongs here.
meta-arm-bsp: This layer provides support for Arm reference platforms
meta-arm-iota: This layer provides support for Arm's IOTA Linux Distribution
meta-arm-toolchain: This layer provides support for Arm's GNU-A toolset releases
meta-arm-autonomy: This layer provides a reference stack for autonomous systems.
Contributing
Currently, we only accept patches from the meta-arm mailing list. For general information on how to submit a patch, please read https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
E-mail meta-arm@lists.yoctoproject.org with patches created using this process. You can configure git-send-email to automatically use this address for the meta-arm repository with the following git command:
$ git config --local --add sendemail.to meta-arm@lists.yoctoproject.org
Commits and patches added should follow the OpenEmbedded patch guidelines:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
The component being changed in the shortlog should be prefixed with the layer name (without the meta- prefix), for example:
arm-bsp/trusted-firmware-a: decrease frobbing level
arm-toolchain/gcc: enable foobar v2
Reporting bugs
E-mail meta-arm@lists.yoctoproject.org with the error encountered and the steps to reproduce the issue.
Maintainer(s)
- Jon Mason jon.mason@arm.com
- Ross Burton ross.burton@arm.com