Hi,
With RPB environment I can easily add some new layer via a local_manifest
way on top of rpb manifest.
In this case, I see a potential issue and I would like to open a
discussion about it.
If I add a layer:
- bsp layer: env setup script take into account all the bsp layer
available on the source tree.
- framework layer (like meta-qt5, meta-browser, ...): in this case there
is no automatic way to use this layer on the build, we must manually change
the bblayers.conf file before the compilation to take into account the
framework layer.
Question:
Have you some plan to support such request ?
The goal are to provide a reproducible build which are as based on RPB
which add the support of new frameworks by using the same way to initialize
the environment without making manual change on bblayers.conf.
Proposal:
- if there is bblayers.conf and local.conf files on local_manifest, this
files will overwrote the default files available on manifest via the env
setup script.
Thanks for your feedback.
Regards
Christophe Priouzeau
--
Christophe Priouzeau
Software Engineer from STMicroelectronics
Group: LHG (Linaro Digital Home Group)
STMicroelectronics | 9 Rue Pierre Felix Delarue | 72000 Le mans | France
I am trying to create an image in openembedded similar to the
hikey-jessie_developer_20151130-387.img. I created an image with 2
partitions, boot (fat32) and rootfs (ext4). My kernel (Image) and device
tree are located in the boot partition. When I put the card in the dev
board and turn it on it does not boot. I get a message "Fail to start
BootNext". I can boot the kernel using the sd card grub option on the
eMMC, but not by default. Are there directions on how to create an sd
card image like the hikey-jessie_developer_20151130-387.img?
-Machon
On Fri, Feb 19, 2016 at 1:38 PM, Xi Zhou Zhou <joel.zhou(a)broadcom.com> wrote:
> I download the pre-built toolchain for one of our armv6 board.
> https://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-…
This is the embedded toolchain, for systems not running linux.
> After plug it into Yocto as an external toolchain, it failed to install it
> correctly.
Yocto is linux, so there is a contradiction here. It isn't clear why
you are trying to do this, as this is not expected to work.
> ../meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb,
> do_install
> | DEBUG: Executing shell function do_install
> | cp: cannot stat
> `/opt/gcc-linaro-arm-none-eabi-4.8-2014.04_linux/arm-none-eabi/libc/lib/*':
> No such file or directory
Yocto is looking for the linux toolchain sysroot, but this isn't a
linux toolchain, so there is no sysroot.
If Yocto is supposed to work with embedded toolchains, then you need
to fix the yocto scripts to make the toolchain sysroot optional.
Or if you are really trying to download the linux toolchain, then you
should instead grab
https://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-…
Jim
Hi all,
I download the pre-built toolchain for one of our armv6 board.
https://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-…
After plug it into Yocto as an external toolchain, it failed to install it
correctly.
../meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/
external-linaro-toolchain.bb, do_install
| DEBUG: Executing shell function do_install
| cp: cannot stat
`/opt/gcc-linaro-arm-none-eabi-4.8-2014.04_linux/arm-none-eabi/libc/lib/*':
No such file or directory
Any suggestion?
Thanks,
Joel
