Logically, the project has been divided in macro sets:
Yocto Base
Set of layer used as core, together with Poky, for the Clea OS distros.
Name | Description | URL | Owner |
---|
poky | Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. As an integration layer, Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems. | source code | Yocto Project |
meta-openembedded | This repository is a collection of layers to supplement OE-Core with additional packages. Each layer has a designated maintainer. Please see the respective READMEs in the layer subdirectories. | source code | OpenEmbedded |
meta-clang | This layer provides clang/llvm based cross compiler. Currently working on it for ARM and x86. | source code | OpenEmbedded |
meta-timesys | Timesys layer for Vigiles Yocto CVE monitoring, security notifications, and image manifest generation. | source code | OpenEmbedded |
Yocto Extended
Name | Description | URL | Owner |
---|
meta-virtualization | This layer provides support for building Xen, KVM, Libvirt, and associated packages necessary for building OE-based virtualized solutions. | source code | OpenEmbedded |
meta-rauc | RAUC is a lightweight update client that runs on your embedded device and reliably controls the procedure of updating your device with a new firmware revision. RAUC is also the tool on your host system that lets you create, inspect and modify update artifacts for your device. RAUC is written in C using GLib and licensed under LGPL2-1. With the meta-rauc layer you can easily integrate RAUC into your embedded project. It adds all required tools to your rootfs and automates building update bundles from your images. For information about using and configuring RAUC visit Welcome to the RAUC documentation!. | source code | Pengutronix/
OpenEmbedded |
meta-browser | Web browsers (Chromium, Firefox, etc.) | source code | OpenEmbedded |
meta-openembedded/meta-networking | Contains networking-related packages, tools and configurations. Supplements packages from oe-core. | source code | OpenEmbedded |
meta-openembedded/meta-filesystems | Tools for providing and working with additional filesystems. | source code | OpenEmbedded |
meta-security | This layer provides security tools, hardening tools for Linux kernels and libraries for implementing security mechanisms. | source code | Yocto Project |
meta-arm | This repository contains the Arm layers for OpenEmbedded. | source code | Yocto Project |
Frameworks
Layers adding common framework to the distribution. Some of them are to be intended to be optionally integrated.
Name | Description | URL | Owner |
---|
meta-lts-mixins | (Used for RUST 1.75 support in Kirkstone) "Mixin" layer for adding latest Docker versions into the Yocto Project LTS. This is a supplementary layer to dunfell/go branch of meta-lts-mixins. As that layer updates go toolchain to newer versions, this renders the docker recipes from dunfell branch of meta-virtualization unbuildable. The purpose of this layer is to backport latest, compatible docker from meta-virtualization master to dunfell. | source code | Yocto Project |
meta-python2 | This is the home for your python2 recipes. Python3 recipes will continue to be supported via the original meta-python layer. Python2 is going EOL (end of life) in January 2020. This means that all support for the language will be on the shoulders of the community and the upstream python developers will no longer be supporting it. This has been in the works for several years and it should come as no surprise to ANYONE that the support is ending. In light of the above, oe-core, meta-oe, meta-python and other layers are actively dropping python2 recipes. This also means that the core developers for YP/OE will no longer have any motivation to maintain python2 or python2 recipes. This includes the creator of this layer | source code | OpenEmbedded |
meta-qt5 | Recipes for Qt5 modules | source code | OpenEmbedded |
meta-qt6 | Recipes for Qt6 modules | source code | OpenEmbedded |
SOC
Clea OS is designed to be compatible with the vast majority of the Embedded Systems produced by SECO, having both ARM and x86 architectures.
In order to extend the support of Clea OS there are layers for hardware that do not come from SECO: Raspberry PI.
NXP
Name | Description | URL | Owner |
---|
meta-seco-imx | This layer is intended to hold all recipes needed to build the Board Support Package (BSP) for all NXP CPU-based SECO boards supporting Clea OS. The layer contains the reference to the actual Kernel, U-Boot and mkimage repositories and to the commit SHAs that are used in the image build process. | source code | SECOClea |
meta-freescale | This layer provides support for NXP's platforms for use with OpenEmbedded and/or Yocto Project. | source code | community |
Rockchip
Name | Description | URL | Owner |
---|
meta-seco-rk | This layer is intended to hold all recipes needed to build the Board Support Package (BSP) for all Rockchip CPU-based SECO boards supporting Clea OS. The layer contains the reference to the actual Kernel and U-Boot repositories and to the corresponding commit SHAs that are used in the image build process. | source code | SECO/Clea |
Intel
Name | Description | URL | Owner |
---|
meta-seco-intel | This layer is intended to hold all recipes needed to build the Board Support Package (BSP) for Intel CPU-based SECO boards supporting Clea OS. | source code | SECO/Clea |
meta-intel | The Yocto layer containing Intel hardware support metadata. | source code | Yocto Project |
Name | Description | URL | Owner |
---|
meta-seco-mtk | This layer is intended to hold all recipes needed to build the Board Support Package (BSP) for MediaTek CPU-based SECO boards supporting Clea OS. | source code | SECO/Clea |
meta-mediatek-bsp | This layer provides a minimal BSP and rootfs for booting MediaTek boards. | source code | MediaTek |
meta-rity | The RITY repository is a collection of layer in order to demo the usage of MediaTek BSP. | source code | MediaTek |
Raspberry Pi
Name | Description | URL | Owner |
---|
meta-seco-intel | This layer is intended to hold all recipes needed to build the Board Support Package (BSP) for Raspberry PI boards supporting Clea OS. | source code | SECO/Clea |
meta-raspberrypi | The Yocto layer containing Raspberry Pi board support metadata. | source code | Raspberry |