Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Koen Kooi
file 54 lines (34 sloc) 2.189 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master
revision: HEAD

And the layers found in the meta-openembedded repo. At least 'meta-oe' and 'meta-systemd' are needed. The instructions below will take care of everything automagically.

URI: git://git.openembedded.org/meta-openembedded
branch: master
revision: HEAD

==============================
           Setup
==============================

It is recommended to follow the instruction at http://www.angstrom-distribution.org/building-angstrom

This will set it up for the OpenEmbedded-core layout needed for this layer instead of the old OpenEmbedded-dev layout.

==============================
       Test Reports
==============================

To see which machines and packages were successfully built, check the buildhistory git repository:

https://github.com/Angstrom-distribution/buildhistory

==============================
       Branching
==============================

When branching 'master' for a release ensure that:

1) conf/distro/angstrom-${VERSION}.conf is created
2) DISTRO_VERSION is set to vYYYY.MM (e.g. 2014.06)
3) classes/angstrom-mirrors.bbclass is pointing to the correct source mirror
4) recipes-angstrom/angstrom/angstrom-feed-configs.bb has PV = "${DISTRO_VERSION}"

==============================
          Patches
==============================

Send pull requests to angstrom-distro-devel@linuxtogo.org with '[meta-angstrom]' in the subject'

When sending single patches, please use something like 'git send-email -1 --to angstrom-distro-devel@linuxtogo.org --subject-prefix meta-angstrom'

You are encouraged to fork the mirror on github https://github.com/koenkooi/meta-angstrom to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainers: Koen Kooi <koen@dominion.thruhere.net>
                        Khem Raj <raj.khem@gmail.com>


Something went wrong with that request. Please try again.