All Projects → Angstrom-distribution → meta-angstrom

Angstrom-distribution / meta-angstrom

Licence: MIT license
MIrror of Angstrom metadata layer

Programming Languages

BitBake
79 projects
shell
77523 projects
Batchfile
5799 projects
HTML
75241 projects
PHP
23972 projects - #3 most used programming language
assembly
5116 projects
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 https://github.com/Angstrom-distribution/angstrom-manifest

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:

	2) DISTRO_VERSION is set to vYYYY.MM (e.g. 2014.06)
	1) FEED_BASEPATH is changed in angstrom.conf to use DISTRO_VERSION instead of 'next'
	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 [email protected] with '[meta-angstrom]' in the subject'

When sending single patches, please use something like 'git send-email -1 --to [email protected] --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 <[email protected]>
                        Khem Raj <[email protected]>


Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].