Category Archives: Uncategorized

Introduction

Ångström was started by a small group of people who worked on the OpenEmbedded, OpenZaurus and OpenSimpad projects to unify their effort to make a stable and userfriendly distribution for embedded devices like handhelds, set top boxes and network-attached storage devices and more.

Our name is Ångström, not OpenEmbedded Ångström. While Ångström is currently using OpenEmbedded heavily through the Yocto Project it isn’t including it in its name. So if you send out a press-release, please use the proper name.

Ångström is versatile, it scales down to devices with 4MB of flash to devices with terabytes of RAID storage. Someday it might even run on a toaster :)

 

Yocto Project Compatible, 1.6

As of today the Angstrom v2014.06 release is officially Yocto Project 1.6 Compatible! To build that follow the instruction from the ‘Developers’ link above and use the ‘angstrom-v2014.06-yocto1.6′ branch of the setup-scripts repo.

Yocto Project Compatible, 1.5

As of today the Angstrom v2013.12 release is officially Yocto Project 1.5 Compatible! To build that follow the instruction from the ‘Developers’ link above and use the ‘angstrom-v2013.12-yocto1.5′ branch of the setup-scripts repo.

Yocto Project Compatible status

As of today the Angstrom v2013.06 release is officially Yocto Project 1.4 Compatible! To build that follow the instruction from the ‘Developers’ link above and use the ‘angstrom-v2013.06-yocto1.4′ branch of the setup-scripts repo.

The v2012.12 release was granted Yocto Project Compatible 1.3 status a while ago.

Contribution to Angstrom, where do I send patches to for buildsystem related issues?

Angstrom is using OpenEmbedded as buildsystem and heavily uses its layer features. Let’s take the v2012.05 release (which matches the yocto 1.2 (‘denzil’) release) as an example. All layers have their patch submission policy documented in a README file in each layer. Here is a summary of those:

For the specific example of the v2012.05 release there are some extra steps involved since only backports are allowed in the release branches of the various layers. Whenever possible do your patch on the ‘next’ branch of the setup-scripts to track the latest upstream and then get it accepted upstream and ask for a backport to the matching release branch. Policy on that varies, but adding a ‘[for-denzil]‘ tag to your emails will usually do the trick.

Of the above layers only the meta-angstrom layer is controlled by angstrom developers, all other layers are out of angstrom control.