[OE-core] Changes in Linaro layers for OpenEmbedded

Marcin Juszkiewicz marcin.juszkiewicz at linaro.org
Thu May 9 16:57:47 UTC 2013


NOTE: I skipped "openembedded-devel" ML cause most of users of Linaro
layers also read OE Core ML.

As I will leave Linaro at the end of May I would like to write some kind
of summary of current state of Linaro layers for OpenEmbedded.

At Linaro we have 3 layers:

1. meta-aarch64
2. meta-linaro
3. meta-linaro-toolchain

First one is BSP kind. I know that it had some issues which affected
each build which had it in BBLAYERS but I fixed those issues. I would
like to thank Khem Raj for pointing me at those.

We have git version of binutils there due to some changes which were not
present in 2.23 line. But use of this version is not required as builds
are fine with OE Core one.

We have "tune-armv8.inc" in this layer as well. There was attempt to
merge that into OE Core but "/lib or /lib64" discussion started and at
that time I decided to skip it. There are similar discussions at GCC and
Glibc mailing lists. Once they sort that out OE tune file will be
adapted by someone (I hope).

Rest of recipes can be split into 2-3 types. Few (like sysprof, emacs)
just disable recipes for AArch64. Other have extra patches to add
missing functionality or defines. And we have Linaro kernel for AArch64
there.

Second layer contains ARMv7a(b) machine definitions used for our machine
independent builds and some recipes.

There are no patches for OE recipes here. The only exception is busybox
where we enable "dpkg(-deb)" command which we need for our tools used to
merge rootfs with hardware support.

We have "recipes-extra" where we keep new recipes which may not be in a
nicest state so are not yet merged into OpenEmbedded (or have no use
there like "meta-toolchain-hhvm" one).

"recipes-linaro" is for our stuff. Images, automatic root shell on
serial port etc.

And last but not least is toolchain layer. Everything here is related to
gcc-linaro and Linaro binary cross toolchains (armv7a and aarch64 ones).
GCC 4.6 and 4.7 is there but 4.6 one will be removed when 4.8 will be
added into OE Core.

Who will maintain those layers after my leave? This was not decided yet.
There are few guys at Linaro who know how to use OpenEmbedded but most
of them is outside of Builds and Baselines team.

If you have any questions then better ask now.




More information about the Openembedded-core mailing list