[yocto] Moving angstrom under the yocto banner

Koen Kooi koen at dominion.thruhere.net
Fri Mar 30 14:12:49 PDT 2012


My apologies for loosing the reply indent, I blame apple mail

Op 30 mrt. 2012, om 14:01 heeft Osier-mixon, Jeffrey het volgende geschreven:
> 
> Angstrom does use oe-core, but I don't think it uses linux-yocto (right?) and definitely not meta-yocto. 

linux-yocto is a kernel, which is used by machines in meta-intel, which angstrom supports (only fri2 atm), so the choice to use or not use linux-yocto is up to th e BSP, not to angstrom. OE was founded on the principle that machines, images and distros are orthogonal. Angstrom does cheat a bit with images, but it is *not* changing any machine definitions.

This is what angstrom is currently using:

[koen at Angstrom-F16-vm-rpm setup-scripts]$ cat sources/layers.txt 
# Name,repo-uri,branch,rev
bitbake,git://github.com/openembedded/bitbake.git,master,HEAD
meta-angstrom,git://github.com/Angstrom-distribution/meta-angstrom,master,HEAD
meta-openembedded,git://github.com/openembedded/meta-oe.git,master,HEAD
meta-ti,git://git.yoctoproject.org/meta-ti,master,HEAD
meta-ettus,git://github.com/balister/meta-ettus.git,master,HEAD
meta-efikamx,git://github.com/kraj/meta-efikamx.git,master,HEAD
meta-nslu2,git://github.com/kraj/meta-nslu2.git,master,HEAD
meta-smartphone,http://git.shr-project.org/repo/meta-smartphone.git,master,HEAD
meta-intel,git://git.yoctoproject.org/meta-intel,master,HEAD
meta-xilinx,git://git.yoctoproject.org/meta-xilinx,master,HEAD
meta-openpandora,git://github.com/openpandora/meta-openpandora.git,master,HEAD
meta-handheld,git://git.openembedded.org/meta-handheld,master,HEAD
meta-opie,git://github.com/bluelightning/meta-opie.git,master,HEAD
meta-java,git://github.com/woglinde/meta-java.git,master,HEAD
meta-mozilla,git://github.com/OSSystems/meta-mozilla.git,master,HEAD
meta-mono,git://github.com/KokoFitClub/meta-mono.git,master,HEAD
openembedded-core,git://github.com/openembedded/oe-core.git,master,HEAD

It will add more bsp layers soon (fsl-ppc, fsl-arm, etc) before the release.

And the layer config:

[koen at Angstrom-F16-vm-rpm setup-scripts]$ cat conf/bblayers.conf 
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "4"
TOPDIR := "${@os.path.dirname(os.path.dirname(d.getVar('FILE', True)))}"

BBPATH = "${TOPDIR}"

BBFILES = ""

# These layers hold recipe metadata not found in OE-core, but lack any machine or distro content
BASELAYERS ?= " \
  ${TOPDIR}/sources/meta-openembedded/meta-oe \
  ${TOPDIR}/sources/meta-openembedded/toolchain-layer \
  ${TOPDIR}/sources/meta-openembedded/meta-efl \
  ${TOPDIR}/sources/meta-openembedded/meta-gpe \
  ${TOPDIR}/sources/meta-openembedded/meta-gnome \
  ${TOPDIR}/sources/meta-openembedded/meta-xfce \
  ${TOPDIR}/sources/meta-openembedded/meta-initramfs \
  ${TOPDIR}/sources/meta-opie \
  ${TOPDIR}/sources/meta-java \
  ${TOPDIR}/sources/meta-mozilla \
"

# These layers hold machine specific content, aka Board Support Packages
BSPLAYERS ?= " \
  ${TOPDIR}/sources/meta-ti \
  ${TOPDIR}/sources/meta-efikamx \
  ${TOPDIR}/sources/meta-nslu2 \
  ${TOPDIR}/sources/meta-smartphone/meta-htc \
  ${TOPDIR}/sources/meta-smartphone/meta-nokia \
  ${TOPDIR}/sources/meta-smartphone/meta-openmoko \
  ${TOPDIR}/sources/meta-smartphone/meta-palm \
  ${TOPDIR}/sources/meta-handheld \
  ${TOPDIR}/sources/meta-intel \
  ${TOPDIR}/sources/meta-intel/meta-sugarbay \
  ${TOPDIR}/sources/meta-intel/meta-crownbay \
  ${TOPDIR}/sources/meta-intel/meta-emenlow \
  ${TOPDIR}/sources/meta-intel/meta-fishriver \
  ${TOPDIR}/sources/meta-intel/meta-jasperforest \
  ${TOPDIR}/sources/meta-intel/meta-n450 \
"

# Add your overlay location to EXTRALAYERS
# Make sure to have a conf/layers.conf in there
EXTRALAYERS ?= ""

BBLAYERS = " \
  ${TOPDIR}/sources/meta-angstrom \
  ${BASELAYERS} \
  ${BSPLAYERS} \
  ${EXTRALAYERS} \
  ${TOPDIR}/sources/openembedded-core/meta \
  "

regards,

Koen


More information about the yocto mailing list