# bldcontrol_buildenvironment

bbaddress: localhost
sourcedir: /opt/dreyna/yp_5_3_postpoky/bitbake-builds/poky-master-poky-distro_poky-machine_qemux86-64/build
created: 2025-11-13 17:01:41.509105
updated: 2025-11-13 17:24:28.981384
builddir:
  /opt/dreyna/yp_5_3_postpoky/bitbake-builds/poky-master-poky-distro_poky-machine_qemux86-64/build/build


# orm_build

machine: qemux86-64
distro: poky
distro_version: 5.2.99+snapshot-e556df28f47e754b53e1f46c97dde2b19fd8fad1
started_on: 2025-11-13 17:20:50.061526
completed_on: 2025-11-13 17:22:14.418642
build_name: 20251113172202
bitbake_version: 2.15.2
cooker_log_path:
  /opt/dreyna/yp_5_3_postpoky/bitbake-builds/poky-master-poky-distro_poky-machine_qemux86-64/build/build-toaster-2/tmp/log/cooker/qemux86-64/build_20251113_092131.175.log


machine: qemux86-64
distro: poky
distro_version: 5.2.4
started_on: 2025-11-13 17:23:03.286454
completed_on: 2025-11-13 17:24:28.975685
build_name: 20251113172416
bitbake_version: 2.12.1
cooker_log_path:
  /opt/dreyna/yp_5_3_postpoky/bitbake-builds/poky-master-poky-distro_poky-machine_qemux86-64/build/build-toaster-3/tmp/log/cooker/qemux86-64/build_20251113_092342.957.log


# orm_helptext

key: B
text:
  The Build Directory. The OpenEmbedded build system places generated objects into the Build Directory during a recipe's build process.


key: IMAGE_LINGUAS
text:
  Specifies the list of locales to install into the image during the root filesystem construction process.


key: PREFERRED_PROVIDER_virtual/libc
text:
  If multiple recipes provide an item, this variable determines which recipe should be given preference.


key: SRC_URI
text:
  The list of source files - local or remote. This variable tells the OpenEmbedded build system what bits to pull in for the build and how to pull them in.


key: KERNEL_MODULE_PROBECONF
text:
  Lists kernel modules for which the build system expects to find module_conf_* values that specify configuration for each of the modules


key: ASSUME_PROVIDED
text:
  List of packages (recipes actually) that are assumed to be implicitly available. BitBake does not build these packages.


key: INCOMPATIBLE_LICENSE
text:
  Specifies a space-separated list of license names (as they would appear in LICENSE) that should be excluded from the build. Wildcard is supported, such as '*GPL-3.0*'


key: RSUGGESTS
text:
  A list of additional packages that you can suggest for installation by the package manager at the time a package is installed. Not all package managers support this functionality.


key: FILESYSTEM_PERMS_TABLES
text:
  Allows you to define your own file permissions settings table as part of your configuration for the packaging process.


key: KARCH
text:
  Defines the kernel architecture used when assembling the configuration. You define the KARCH variable in the BSP Descriptions.


key: REQUIRED_COMBINED_FEATURES
text:
  When a recipe inherits the features_check class, all items in this variable must be included in COMBINED_FEATURES.


key: PACKAGE_INSTALL_ATTEMPTONLY
text:
  List of packages attempted to be installed. If a listed package fails to install, the build system does not generate an error. This variable is generally not user-defined.


key: COMPLEMENTARY_GLOB
text:
  Defines wildcards to match when installing a list of complementary packages for all the packages installed in an image.


key: do_package
text:
  Analyzes the content of the holding area and splits it into subsets based on available packages and files


key: TOOLCHAIN_TARGET_TASK
text:
  This variable lists packages the OpenEmbedded build system uses when it creates the target part of an SDK, which includes libraries and headers.


key: DISTRO
text:
  The short name of the distribution. If the variable is blank, meta/conf/distro/defaultsetup.conf will be used.


key: CFLAGS
text:
  Flags passed to the C compiler for the target system. This variable evaluates to the same as TARGET_CFLAGS.


key: BB_DISKMON_DIRS
text:
  Monitors disk space and available inodes during the build and allows you to control the build based on these parameters.


key: EXTERNALSRC
text:
  If externalsrc.bbclass is inherited, this variable points to the source tree, which is outside of the OpenEmbedded build system.


key: AUTOREV
text:
  When SRCREV is set to the value of this variable, it specifies to use the latest source revision in the repository.


key: PREFERRED_VERSION
text:
  If there are multiple versions of recipes available, this variable determines which recipe should be given preference.


key: IMAGE_OVERHEAD_FACTOR
text:
  Defines a multiplier that the build system applies to the initial image size for cases when the multiplier times the returned disk usage value for the image is greater than the sum of IMAGE_ROOTFS_SIZE and IMAGE_ROOTFS_EXTRA_SPACE.


key: do_spdx
text:
  A build stage that takes the source code and scans it on a remote FOSSOLOGY server in order to produce an SPDX document


key: BP
text:
  The base recipe name and version but without any special recipe name suffix (i.e. -native, lib64-, and so forth). BP is comprised of ${BPN}-${PV}


key: ROOTFS_POSTPROCESS_COMMAND
text:
  Added by classes to run post processing commands once the OpenEmbedded build system has created the root filesystem.


key: EXTRA_USERS_PARAMS
text:
  When a recipe inherits the extrausers class, this variable provides image level user and group operations.


key: GTKIMMODULES_PACKAGES
text:
  For recipes that inherit the gtk-immodules-cache class, this variable specifies the packages that contain the GTK+ input method modules being installed when the modules are in packages other than the main package.


key: MACHINE_FEATURES_BACKFILL_CONSIDERED
text:
  Features from MACHINE_FEATURES_BACKFILL that should not be backfilled (i.e. added to MACHINE_FEATURES) during the build.


key: LICENSE
text:
  The list of source licenses for the recipe. Logical operators '&' or '|' and parentheses can be used.


key: EXTRA_IMAGE_FEATURES
text:
  The list of additional features to include in an image. Configure this variable in the conf/local.conf file in the Build Directory.


key: LAYERDEPENDS
text:
  Lists the layers, separated by spaces, upon which this recipe depends. This variable is used in the conf/layer.conf file and must be suffixed with the name of the specific layer.


key: PE
text:
  The epoch of the recipe. The default value is '0'. The field is used to make upgrades possible when the versioning scheme changes in some backwards incompatible way.


key: BB_NUMBER_THREADS
text:
  The maximum number of tasks BitBake should run in parallel at any one time. A good rule of thumb is to set this variable to twice the number of cores.


key: SPDX_IMPORTS
text:
  SPDX_IMPORTS is the base variable that describes how to     reference external SPDX ids. Each import is defined as a key in this     variable with a suffix to describe to as a suffix to look up more     information about the import. Each key can have the following variables:         SPDX_IMPORTS_<key>_spdxid: The Fully qualified SPDX ID of the object         SPDX_IMPORTS_<key>_uri: The URI where the SPDX Document that contains             the external object can be found. Optional but recommended         SPDX_IMPORTS_<key>_hash_<hash>: The Checksum of the SPDX Document that             contains the External ID. <hash> must be one the valid SPDX hashing             algorithms, as described by the HashAlgorithm vocabulary in the            SPDX 3 spec. Optional but recommended


key: TESTIMAGE_AUTO
text:
  Enables test booting of virtual machine images under the QEMU emulator after any root filesystems are created and runs tests against those images each time an image is built.


key: MACHINEOVERRIDES
text:
  Lists overrides specific to the current machine. By default, this list includes the value of MACHINE.


key: EXTRA_QMAKEVARS_PRE
text:
  Configuration variables or options you want to pass to qmake when the arguments need to be before the .pro file list on the command line.


key: SPDX_PACKAGE_ADDITIONAL_PURPOSE
text:
  The list of additional purposes to assign to     the generated packages for a recipe. The primary purpose is always `install`.     Packages overrides are allowed to override the additional purposes for     individual packages.


key: KERNEL_IMAGETYPE
text:
  The type of kernel to build for a device, usually set by the machine configuration files and defaults to 'zImage'.


key: SRCREV
text:
  The revision of the source code used to build the package. This variable applies to Subversion, Git, Mercurial and Bazaar only.


key: CONFLICT_DISTRO_FEATURES
text:
  When a recipe inherits the features_check class, no item in this variable can be included in DISTRO_FEATURES.


key: SPDX_INVOKED_BY
text:
  The base variable name to describe the Agent that     invoked the build, which builds will link to if specified. Requires     SPDX_INCLUDE_BITBAKE_PARENT_BUILD. NOTE: Setting this will likely result in     non-reproducible SPDX output


key: SYSROOT_PREPROCESS_FUNCS
text:
  A list of functions to execute after files are staged into the sysroot. These functions are usually used to apply additional processing on the staged files, or to stage additional files.


key: SPDX_PACKAGE_URL
text:
  Provides a place for the SPDX data creator to record the package URL string (in accordance with the Package URL specification) for a software Package.


key: TARGET_CFLAGS
text:
  Flags passed to the C compiler for the target system. This variable evaluates to the same as CFLAGS.


key: EXTRA_QMAKEVARS_POST
text:
  Configuration variables or options you want to pass to qmake when the arguments need to be after the .pro file list on the command line.


key: FONT_EXTRA_RDEPENDS
text:
  When a recipe inherits the fontcache class, this variable specifies runtime dependencies for font packages. This variable defaults to 'fontconfig-utils'.


key: SPDX_INCLUDE_TIMESTAMPS
text:
  Include time stamps in SPDX output. This is     useful if you want to know when artifacts were produced and when builds     occurred, but will result in non-reproducible SPDX output


key: SRC_URI_OVERRIDES_PACKAGE_ARCH
text:
  By default, the OpenEmbedded build system automatically detects whether SRC_URI contains files that are machine-specific. If so, the build system automatically changes PACKAGE_ARCH. Setting this variable to '0' disables this behavior.


key: USERADD_GID_TABLES
text:
  Specifies a password file to use for obtaining static group identification (gid) values when the OpenEmbedded build system adds a group to the system during package installation.


key: STAMP
text:
  Specifies the base path used to create recipe stamp files. The path to an actual stamp file is constructed by evaluating this string and then appending additional information.


key: USERADD_ERROR_DYNAMIC
text:
  If set to 'error', forces the OpenEmbedded build system to produce an error if the user identification (uid) and group identification (gid) values are not defined in any of the files listed in USERADD_UID_TABLES and USERADD_GID_TABLES. If set to 'warn', a warning will be issued instead.


key: SUMMARY
text:
  The short (80 characters or less) summary of the binary package for packaging systems such as opkg, rpm or dpkg. By default, SUMMARY is used to define the DESCRIPTION variable if DESCRIPTION is not set in the recipe.


key: WARN_QA
text:
  Specifies the quality assurance checks whose failures are reported as warnings by the OpenEmbedded build system.


key: KBRANCH_DEFAULT
text:
  Defines the Linux kernel source repository's default branch used to build the Linux kernel. Unless you specify otherwise, the variable initializes to 'master'.


key: SSTATE_MIRRORS
text:
  Configures the OpenEmbedded build system to search other mirror locations for prebuilt cache data objects before building out the data. You can specify a filesystem directory or a remote URL such as HTTP or FTP.


key: KERNEL_EXTRA_ARGS
text:
  Specifies additional make command-line arguments the OpenEmbedded build system passes on when compiling the kernel.


key: MACHINE
text:
  Specifies the target device for which the image is built. You define MACHINE in the conf/local.conf file in the Build Directory.


key: SPDX_ON_BEHALF_OF
text:
  The base variable name to describe the Agent on who's     behalf the invoking Agent (SPDX_INVOKED_BY) is running the build. Requires     SPDX_INCLUDE_BITBAKE_PARENT_BUILD. NOTE: Setting this will likely result in     non-reproducible SPDX output


key: DEPLOY_DIR
text:
  Points to the general area that the OpenEmbedded build system uses to place images, packages, SDKs and other output files that are ready to be used outside of the build system.


key: CONFLICT_MACHINE_FEATURES
text:
  When a recipe inherits the features_check class, no item in this variable can be included in MACHINE_FEATURES.


key: CONFIG_SITE
text:
  A list of files that contains autoconf test results relevant to the current build. This variable is used by the Autotools utilities when running configure.


key: SPDX_INCLUDE_BITBAKE_PARENT_BUILD
text:
  Report the parent invocation of bitbake     for each Build object. This allows you to know who invoked bitbake to perform     a build, but will result in non-reproducible SPDX output.


key: do_configure
text:
  Configures the source by enabling and disabling any build-time and configuration options for the software being built


key: SELECTED_OPTIMIZATION
text:
  The variable takes the value of FULL_OPTIMIZATION unless DEBUG_BUILD = '1'. In this case, the value of DEBUG_OPTIMIZATION is used.


key: DL_DIR
text:
  The central download directory used by the build process to store downloads. By default, the directory is 'downloads' in the Build Directory.


key: RM_WORK_EXCLUDE
text:
  With rm_work enabled, this variable specifies a list of packages whose work directories should not be removed.


key: FAKEROOT_QA
text:
  QA tests which need to run under fakeroot. If any enabled tests are listed here, the do_package_qa task will run under fakeroot.


key: BBFILE_PRIORITY_core
text:
  Assigns the priority for recipe files in each layer. Setting this variable allows you to prioritize a layer against other layers that contain the same recipe.


key: TEST_SERIALCONTROL_EXTRA_ARGS
text:
  For automated hardware testing, specifies additional arguments to pass through to the command specified in TEST_SERIALCONTROL_CMD


key: SSTATE_HASHEQUIV_REPORT_TASKDATA
text:
  Report additional useful data to the     hash equivalency server, such as PN, PV, taskname, etc. This information     is very useful for developers looking at task data, but may leak sensitive     data if the equivalence server is public.     


key: T
text:
  This variable points to a directory were BitBake places temporary files, which consist mostly of task logs and scripts, when building a particular recipe.


key: FEED_DEPLOYDIR_BASE_URI
text:
  Allow to serve ipk deploy directory as an ad hoc feed (bogofeed). Set to base URL of the directory as exported by HTTP. Set of ad hoc feed configs will be generated in the image.


key: DISTRO_EXTRA_RRECOMMENDS
text:
  Specifies a list of distro-specific packages to add to all images if the packages exist. The list of packages are automatically installed but you can remove them.


key: PROVIDES
text:
  A list of aliases that a recipe also provides. These aliases are useful for satisfying dependencies of other recipes during the build as specified by DEPENDS.


key: TARGET_ARCH
text:
  The architecture of the device being built. The OpenEmbedded build system supports the following architectures: arm, mips, ppc, x86, x86-64.


key: PACKAGE_CLASSES
text:
  This variable specifies the package manager to use when packaging data. It is set in the conf/local.conf file in the Build Directory.


key: KERNEL_SRC
text:
  The location of the kernel sources. This variable is set to the value of the STAGING_KERNEL_DIR within the module class (module.bbclass).


key: RPROVIDES
text:
  A list of package name aliases that a package also provides. These aliases are useful for satisfying runtime dependencies of other packages both during the build and on the target.


key: PYPI_PACKAGE
text:
  The python package name to use for fetching from pypi. Default is parsed from the recipe name, but can be overridden if upstream name is different than recipe name.


key: BUILDSTATS_BASE
text:
  Points to the location of the directory that holds build statistics when you use and enable the buildstats class.


key: SPDX_AUTHORS
text:
  A space separated list of the document authors. Each item     is used to name a base variable like SPDX_AUTHORS_<AUTHOR> that     describes the author.


key: FULL_OPTIMIZATION
text:
  The options to pass in TARGET_CFLAGS and CFLAGS when compiling an optimized system. This variable defaults to '-O2 ${DEBUG_LEVELFLAG}'.


key: PACKAGE_INSTALL
text:
  List of the packages to be installed into the image. The variable is generally not user-defined and uses IMAGE_INSTALL as part of the list.


key: PYPI_SRC_URI
text:
  The URI to use to fetch from pypi, default uses pythonhosted.org and is constructed from PYPI_PACKAGE, PYPI_PACKAGE_EXT and PV.


key: USERADD_UID_TABLES
text:
  Specifies a password file to use for obtaining static user identification (uid) values when the OpenEmbedded build system adds a user to the system during package installation.


key: QA_EMPTY_DIRS_RECOMMENDATION
text:
  This specifies a recommendation for a directory why it must be empty, which will be included in the error message if the directory is not empty.


key: MACHINE_FEATURES_BACKFILL
text:
  Features to be added to MACHINE_FEATURES if not also present in MACHINE_FEATURES_BACKFILL_CONSIDERED. This variable is set in the meta/conf/bitbake.conf file and is not intended to be user-configurable.


key: EXTRA_IMAGEDEPENDS
text:
  A list of recipes to build that do not provide packages for installing into the root filesystem. Use this variable to list recipes that are required to build the final image, but not needed in the root filesystem.


key: SECTION
text:
  The section in which packages should be categorized. Package management utilities can make use of this variable.


key: SPDX_IMAGE_PURPOSE
text:
  The list of purposes to assign to the generated images.     The first listed item will be the Primary Purpose and all additional items will     be added as additional purposes


key: MACHINE_EXTRA_RRECOMMENDS
text:
  A list of machine-specific packages to install as part of the image being built that are not essential for booting the machine. The image being built has no build dependencies on the packages in this list.


key: LAYERVERSION_yoctobsp
text:
  Optionally specifies the version of a layer as a single number. This variable is used in the conf/layer.conf file and must be suffixed with the name of the specific layer.


key: BAD_RECOMMENDATIONS
text:
  A list of packages not to install despite being recommended by a recipe. Support for this variable exists only when using the IPK or RPM packaging backends.


key: TEST_POWERCONTROL_EXTRA_ARGS
text:
  For automated hardware testing, specifies additional arguments to pass through to the command specified in TEST_POWERCONTROL_CMD


key: CLASSOVERRIDE
text:
  An internal variable specifying the special class override that should currently apply (e.g. "class-target", "class-native", and so forth).


key: FONT_PACKAGES
text:
  When a recipe inherits the fontcache class, this variable identifies packages containing font files that need to be cached by Fontconfig.


key: BUSYBOX_SPLIT_SUID
text:
  For the BusyBox recipe, specifies whether to split the output executable file into two parts: one for features that require setuid root, and one for the remaining features.


key: TCMODE
text:
  Enables an external toolchain (where provided by an additional layer) if set to a value other than 'default'.


key: RCONFLICTS
text:
  The list of packages that conflict with another package. Note that the package will not be installed if the conflicting packages are not first removed.


key: COMPATIBLE_MACHINE
text:
  A regular expression that resolves to one or more target machines with which a recipe is compatible.


key: TEST_QEMUBOOT_TIMEOUT
text:
  The time in seconds allowed for an image to boot before automated runtime tests begin to run against an image.


key: LOG_DIR
text:
  Specifies the directory to which the OpenEmbedded build system writes overall log files. The default directory is ${TMPDIR}/log


key: BBFILE_PATTERN_core
text:
  Variable that expands to match files from BBFILES in a particular layer. This variable is used in the layer.conf file and must be suffixed with the name of a layer.


key: RDEPENDS
text:
  Lists a package's runtime dependencies (i.e. other packages) that must be installed for the package to be built. They must be the names of other packages as listed in the PACKAGES variable, not recipe names (PN).


key: DISTRO_EXTRA_RDEPENDS
text:
  Specifies a list of distro-specific packages to add to all images. The variable only applies to the images that include packagegroup-base.


key: SSTATE_HASHEQUIV_METHOD
text:
  The fully-qualified function used to calculate     the output hash for a task, which in turn is used to determine equivalency.     


key: DEPLOYDIR
text:
  For recipes that inherit the deploy class, the DEPLOYDIR points to a temporary work area for deployed files.


key: PKGDEST
text:
  Points to the parent directory for files to be packaged after they have been split into individual packages.


key: PACKAGE_EXTRA_ARCHS
text:
  Specifies the list of architectures compatible with the device CPU. This variable is useful when you build for several different devices that use miscellaneous processors.


key: PF
text:
  Specifies the recipe or package name and includes all version and revision numbers. This variable is comprised of ${PN}-${EXTENDPE}${PV}-${PR}.


key: INITSCRIPT_PACKAGES
text:
  A list of the packages that contain initscripts. This variable is used in recipes when using update-rc.d.bbclass. The variable is optional and defaults to the PN variable.


key: BBCLASSEXTEND
text:
  Allows you to extend a recipe so that it builds variants of the software. Common variants for recipes are 'native', 'cross', 'nativesdk' and multilibs.


key: TOOLCHAIN_HOST_TASK
text:
  This variable lists packages the OpenEmbedded build system uses when building an SDK, which contains a cross-development environment.


key: PARALLEL_MAKE
text:
  Specifies extra options that are passed to the make command during the compile tasks. This variable is usually in the form -j 4, where the number represents the maximum number of parallel threads make can run.


key: MODULE_TARBALL_DEPLOY
text:
  Controls creation of the modules-*.tgz file. Set this variable to "0" to disable creation of this file, which contains all of the kernel modules resulting from a kernel build.


key: LINUX_VERSION_EXTENSION
text:
  A string extension compiled into the version string of the Linux kernel built with the OpenEmbedded build system. You define this variable in the kernel recipe.


key: do_populate_sysroot
text:
  Copies a subset of files installed by do_install into the sysroot in order to make them available to other recipes


key: SYSTEMD_AUTO_ENABLE
text:
  For recipes that inherit the systemd class, this variable specifies whether the service you have specified in SYSTEMD_SERVICE should be started automatically or not.


key: SPDX_INCLUDE_VEX
text:
  Controls what VEX information is in the output. Set to     'none' to disable all VEX data. Set to 'current' to only include VEX data     for vulnerabilities not already fixed in the upstream source code     (recommended). Set  to 'all' to get all known historical vulnerabilities,     including those already fixed upstream (warning: This can be large and     slow).


key: TEST_SERIALCONTROL_PS1
text:
  For automated hardware testing, specifies a regex string representing an empty prompt on the target terminal. Example: 'root@target:.*#'. Defaults to 'root@${MACHINE}:.*#'.


key: SYSTEMD_SERVICE
text:
  For recipes that inherit the systemd class, this variable specifies the systemd service name for a package.


key: EXTENDPE
text:
  Used with file and pathnames to create a prefix for a recipe's version based on the recipe's PE value. If PE is set and greater than zero for a recipe, EXTENDPE becomes that value.


key: do_validate_branches
text:
  Ensures that the source/meta branches are on the locations specified by their SRCREV values for a linux-yocto style kernel


key: DEBUG_BUILD
text:
  Specifies to build packages with debugging information. This influences the value of the SELECTED_OPTIMIZATION variable.


key: GRUB_TIMEOUT
text:
  Specifies the timeout before executing the default LABEL in the GNU GRand Unified Bootloader (GRUB).


key: PRIORITY
text:
  Indicates the importance of a package.  The default value is 'optional'.  Other standard values are 'required', 'standard' and 'extra'.


key: KERNEL_FEATURES
text:
  Includes additional metadata from the Yocto Project kernel Git repository. The metadata you add through this variable includes config fragments and features descriptions.


key: SPDX_BUILD_HOST
text:
  The base variable name to describe the build host on     which a build is running. Must be an SPDX_IMPORTS key. Requires     SPDX_INCLUDE_BITBAKE_PARENT_BUILD. NOTE: Setting this will result in     non-reproducible SPDX output


key: TUNE_PKGARCH
text:
  The package architecture understood by the packaging system to define the architecture, ABI, and tuning of output packages.


key: BBPATH
text:
  Used by BitBake to locate .bbclass and configuration files. This variable is analogous to the PATH variable.


key: LEAD_SONAME
text:
  Specifies the lead (or primary) compiled library file (.so) that the debian class applies its naming policy to given a recipe that packages multiple libraries.


key: MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS
text:
  A list of recommended machine-specific packages to install as part of the image being built. Because this is a 'machine essential' variable, the list of packages are essential for the machine to boot.


key: ANY_OF_MACHINE_FEATURES
text:
  When a recipe inherits the features_check class, at least one item in this variable must be included in MACHINE_FEATURES.


key: USERADD_PARAM
text:
  When a recipe inherits the useradd class, this variable specifies for a package what parameters should be passed to the useradd command if you wish to add a user to the system when the package is installed.


key: PACKAGES_DYNAMIC
text:
  A promise that your recipe satisfies runtime dependencies for optional modules that are found in other recipes.


key: ERROR_QA
text:
  Specifies the quality assurance checks whose failures are reported as errors by the OpenEmbedded build system.


key: INHIBIT_DEFAULT_DEPS
text:
  Prevents the default dependencies, namely the C compiler and standard C library (libc), from being added to DEPENDS.


key: PIXBUF_PACKAGES
text:
  When a recipe inherits the pixbufcache class, this variable identifies packages that contain the pixbuf loaders used with gdk-pixbuf.


key: TARGET_FPU
text:
  Specifies the method for handling FPU code. For FPU-less targets, which include most ARM CPUs, the variable must be set to 'soft'. If not, the kernel emulation gets used, which results in a performance penalty.


key: ASSUME_SHLIBS
text:
  List of shlib:package[_version] mappings. Useful for lib packages in ASSUME_PROVIDED, for which automatic shlib dependency tracking does not work.


key: TCLIBC
text:
  Specifies C library (libc) variant to use during the build process. You can select 'baremetal', 'glibc', 'musl', 'newlib', or 'picolibc'.


key: SPDX_SDK_PURPOSE
text:
  The list of purposes to assign to the generate SDK installer.     The first listed item will be the Primary Purpose and all additional items will     be added as additional purposes


key: CLEANBROKEN
text:
  Specifies if 'make clean' does not work for a recipe (and therefore the build system should not try to use it during do_configure)


key: SPDX_INCLUDE_BUILD_VARIABLES
text:
  If set to '1', the bitbake variables for a     recipe will be included in the Build object. This will most likely result     in non-reproducible SPDX output


key: CONFLICT_COMBINED_FEATURES
text:
  When a recipe inherits the features_check class, no item in this variable can be included in COMBINED_FEATURES.


key: MULTIMACH_TARGET_SYS
text:
  Separates files for different machines such that you can build for multiple target machines using the same output directories.


key: SPECIAL_PKGSUFFIX
text:
  A list of prefixes for PN used by the OpenEmbedded build system to create variants of recipes or packages. The list specifies the prefixes to strip off during certain circumstances such as the generation of the BPN variable.


key: SDKIMAGE_FEATURES
text:
  Equivalent to IMAGE_FEATURES. However, this variable applies to the SDK generated from an image using the command 'bitbake -c populate_sdk imagename'.


key: IMAGE_ROOTFS_EXTRA_SPACE
text:
  Defines additional free disk space created in the image in Kbytes. By default, this variable is set to '0'.


key: DEPLOY_DIR_IMAGE
text:
  Points to the area that the OpenEmbedded build system uses to place images and other associated output files that are ready to be deployed onto the target machine.


key: DISTRO_FEATURES_BACKFILL
text:
  Features to be added to DISTRO_FEATURES if not also present in DISTRO_FEATURES_BACKFILL_CONSIDERED. This variable is set in the meta/conf/bitbake.conf file and it is not intended to be user-configurable.


key: PN
text:
  PN refers to a recipe name in the context of a file used by the OpenEmbedded build system as input to create a package. It refers to a package name in the context of a file created or produced by the OpenEmbedded build system.


key: LINUX_VERSION
text:
  The Linux version from kernel.org on which the Linux kernel image being built using the OpenEmbedded build system is based. You define this variable in the kernel recipe.


key: PKGD
text:
  Points to the destination directory for files to be packaged before they are split into individual packages.


key: TEST_TARGET
text:
  For automated runtime testing, specifies the method of deploying the image and running tests on the target machine


key: USE_DEVFS
text:
  When building images, specifies to populate or not /dev. This variable defaults to '1' (leave directory empty, surely because devtmpfs do the job). Set it to '0' to use makedevs (or consider using a custom file with IMAGE_DEVICE_TABLES).


key: DESCRIPTION
text:
  The package description used by package managers. If not set, DESCRIPTION takes the value of the SUMMARY variable.


key: COMPATIBLE_HOST
text:
  A regular expression that resolves to one or more hosts (when the recipe is native) or one or more targets (when the recipe is non-native) with which a recipe is compatible.


key: NO_RECOMMENDATIONS
text:
  When set to '1', no recommended packages will be installed. Realize that some recommended packages might be required for certain system functionality, such as kernel-modules. It is up to the user to add packages to IMAGE_INSTALL as needed.


key: TEST_SUITES
text:
  An ordered list of tests (modules) to run against an image when performing automated runtime testing.


key: TRANSLATED_TARGET_ARCH
text:
  A sanitized version of TARGET_ARCH. This variable is used where the architecture is needed in a value where underscores are not allowed.


key: LAYERDIR
text:
  When used inside the layer.conf configuration file, this variable provides the path of the current layer.


key: USERADDEXTENSION
text:
  When set to 'useradd-staticids', causes the OpenEmbedded build system to base all user and group additions on files listed in USERADD_UID_TABLES and USERADD_GID_TABLES.


key: INHERIT
text:
  Causes the named class to be inherited at this point during parsing. The variable is only valid in configuration files.


key: SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
text:
  A list of recipe dependencies that should not be used to determine signatures of tasks from one recipe when they depend on tasks from another recipe.


key: REQUIRED_MACHINE_FEATURES
text:
  When a recipe inherits the features_check class, all items in this variable must be included in MACHINE_FEATURES.


key: IMAGE_BOOT_FILES
text:
  Whitespace separated list of files from ${DEPLOY_DIR_IMAGE} to place in boot partition. Entries will be installed under a same name as the source file. To change the destination file name, pass a desired name after a semicolon (eg. u-boot.img;uboot).


key: COMMON_LICENSE_DIR
text:
  Points to meta/files/common-licenses in the Source Directory, which is where generic license files reside.


key: SOLIBSDEV
text:
  Defines the suffix for the development symbolic link (symlink) for shared libraries on the target platform.


key: KERNEL_IMAGETYPES
text:
  The list of types of kernel to build for a device, usually set by the machine configuration files and defaults to KERNEL_IMAGETYPE.


key: FILESPATH
text:
  The default set of directories the OpenEmbedded build system uses when searching for patches and files. It is defined in the base.bbclass class found in meta/classes in the Source Directory. Do not hand-edit the FILESPATH variable.


key: INITSCRIPT_PARAMS
text:
  Specifies the options to pass to update-rc.d. The variable is mandatory and is used in recipes when using update-rc.d.bbclass.


key: BPN
text:
  The bare name of the recipe. This variable is a version of the PN variable but removes common suffixes and prefixes.


key: DEBUG_OPTIMIZATION
text:
  The options to pass in TARGET_CFLAGS and CFLAGS when compiling a system for debugging. This variable defaults to '-Og ${DEBUG_LEVELFLAG}'.


key: KBRANCH
text:
  A regular expression used by the build process to explicitly identify the kernel branch that is validated, patched and configured during a build.


key: INITRAMFS_FSTYPES
text:
  Defines the format for the output image of an initial RAM disk (initramfs), which is used during boot.


key: HOST_SYS
text:
  Specifies the system, including the architecture and the operating system, for with the build is occurring in the context of the current recipe.


key: CCACHE_NATIVE_RECIPES_ALLOWED
text:
  A list of native recipes to use Ccache, this variable is useful to bypass a circular dependency between ccache-native and cmake-native that inhibits to use Ccache in other native recipes.


key: GROUPADD_PARAM
text:
  When a recipe inherits the useradd class, this variable specifies for a package what parameters should be passed to the groupadd command if you wish to add a group to the system when the package is installed.


key: OE_TERMINAL
text:
  Controls how the OpenEmbedded build system spawns interactive terminals on the host development system.


key: TEST_POWERCONTROL_CMD
text:
  For automated hardware testing, specifies the command to use to control the power of the target machine under test


key: ANY_OF_DISTRO_FEATURES
text:
  When a recipe inherits the features_check class, at least one item in this variable must be included in DISTRO_FEATURES.


key: OE_BINCONFIG_EXTRA_MANGLE
text:
  When a recipe inherits the binconfig.bbclass class, this variable specifies additional arguments passed to the "sed" command.


key: ENABLE_BINARY_LOCALE_GENERATION
text:
  Controls which locales for glibc are generated during the build. The variable is useful if the target device has 64Mbytes of RAM or less.


key: INHERIT_DISTRO
text:
  Lists classes that will be inherited at the distribution level. It is unlikely that you want to edit this variable.


key: SITEINFO_ENDIANNESS
text:
  Specifies the endian byte order of the target system. The value should be either 'le' for 'little-endian' or 'be' for 'big-endian'.


key: LOCALE_PATHS
text:
  Whitespace separated list of paths that are scanned to construct locale packages. The list already contains ${datadir}/locale by default. Note that all subdirectories in these paths are assumed to be locales.


key: TMPDIR
text:
  The temporary directory the OpenEmbedded build system uses when it does its work building images. By default, the TMPDIR variable is named tmp within the Build Directory.


key: SRCDATE
text:
  The date of the source code used to build the package. This variable applies only if the source was fetched from a Source Code Manager (SCM).


key: SYSTEMD_PACKAGES
text:
  For recipes that inherit the systemd class, this variable locates the systemd unit files when they are not found in the main recipe's package.


key: USERADD_PACKAGES
text:
  When a recipe inherits the useradd class, this variable specifies the individual packages within the recipe that require users and/or groups to be added.


key: PARALLEL_MAKEINST
text:
  Extra options passed to the make install command during the do_install task in order to specify parallel installation.


key: EXTERNALSRC_BUILD
text:
  If externalsrc.bbclass is inherited, this variable points to the directory in which the recipe's source code is built, which is outside of the OpenEmbedded build system.


key: PYPI_PACKAGE_EXT
text:
  The archive file extension to use for fetching from pypi. Default is tar.gz, but can be overridden if upstream uses a different compression scheme.


key: PACKAGE_BEFORE_PN
text:
  Enables easily adding packages to PACKAGES before ${PN} so that the packages can pick up files that would normally be included in the default package.


key: RRECOMMENDS
text:
  A list of packages that extends the usability of a package being built. The package being built does not depend on this list of packages in order to successfully build, but needs them for the extended usability.


key: LOCALE_UTF8_IS_DEFAULT
text:
  If set, locale names are renamed such that those lacking an explicit encoding (e.g. en_US) will always be UTF-8, and non-UTF-8 encodings are renamed to, e.g., en_US.ISO-8859-1. Otherwise, the encoding is specified by glibc's SUPPORTED file. Not supported for precompiled locales.


key: DISTRO_FEATURES_BACKFILL_CONSIDERED
text:
  Features from DISTRO_FEATURES_BACKFILL that should not be backfilled (i.e. added to DISTRO_FEATURES) during the build.


key: PKGDESTWORK
text:
  Points to a temporary work area used by the do_package task to write output from the do_packagedata task.


key: ANY_OF_COMBINED_FEATURES
text:
  When a recipe inherits the features_check class, at least one item in this variable must be included in COMBINED_FEATURES.


key: GROUPMEMS_PARAM
text:
  When a recipe inherits the useradd class, this variable specifies for a package what parameters should be passed to the groupmems command if you wish to modify the members of a group when the package is installed.


key: BINCONFIG_GLOB
text:
  When inheriting binconfig.bbclass from a recipe, this variable specifies a wildcard for configuration scripts that need editing.


key: IMAGE_INSTALL
text:
  Specifies the packages to install into an image. Image recipes set IMAGE_INSTALL to specify the packages to install into an image through image.bbclass.


key: BB_DISKMON_WARNINTERVAL
text:
  Defines the disk space and free inode warning intervals. To set these intervals, define the variable in the conf/local.conf file in the Build Directory.


key: MACHINE_EXTRA_RDEPENDS
text:
  A list of machine-specific packages to install as part of the image being built that are not essential for the machine to boot. However, the build process for more fully-featured images depends on the packages being present.


key: SOC_FAMILY
text:
  Groups together machines based upon the same family of SOC (System On Chip). You typically set this variable in a common .inc file that you include in the configuration files of all the machines.


key: TOPDIR
text:
  The Build Directory. BitBake automatically sets this variable. The OpenEmbedded build system uses the Build Directory when building images.


key: WORKDIR
text:
  The pathname of the working directory in which the OpenEmbedded build system builds a recipe. This directory is located within the TMPDIR directory structure and changes as different packages are built.


key: FILESEXTRAPATHS
text:
  Extends the search path the OpenEmbedded build system uses when looking for files and patches as it processes recipes and append files.


key: TEST_SERIALCONTROL_CONNECT_TIMEOUT
text:
  For automated hardware testing, specifies the timeout in seconds for the initial connection to the target. Defaults to '10'.


key: BBLAYERS
text:
  Lists the layers to enable during the build. This variable is defined in the bblayers.conf configuration file.


key: MLPREFIX
text:
  Specifies a prefix has been added to PN to create a special version of a recipe or package, such as a Multilib version.


key: IMAGE_POSTPROCESS_COMMAND
text:
  Added by classes to run post processing commands once the OpenEmbedded build system has created the image.


key: KFEATURE_DESCRIPTION
text:
  Provides a short description of a configuration fragment. You use this variable in the .scc file that describes a configuration fragment file.


key: TEST_SERIALCONTROL_CMD
text:
  For automated hardware testing, specifies the command to use to connect to the serial console of the target machine under test


key: OVERRIDES
text:
  BitBake uses OVERRIDES to control what variables are overridden after BitBake parses recipes and configuration files.


key: RREPLACES
text:
  A list of packages replaced by a package. The package manager uses this variable to determine which package should be installed to replace other package(s) during an upgrade.


key: DISTROOVERRIDES
text:
  Lists overrides specific to the current distribution. By default, the variable list includes the value of the DISTRO variable.


key: MACHINE_ESSENTIAL_EXTRA_RDEPENDS
text:
  A list of required machine-specific packages to install as part of the image being built. Because this is a 'machine essential' variable, the list of packages are essential for the machine to boot.


key: CORE_IMAGE_EXTRA_INSTALL
text:
  Specifies the list of packages to be added to the image. You should only set this variable in the conf/local.conf file in the Build Directory.


key: REQUIRED_DISTRO_FEATURES
text:
  When a recipe inherits the features_check class, all items in this variable must be included in DISTRO_FEATURES.


key: EXTRA_OESCONS
text:
  When a recipe inherits the scons class, this variable specifies additional configuration options you want to pass to the scons command line.


key: ICECC_RECIPE_ENABLE
text:
  Identifies user recipes that use an empty PARALLEL_MAKE variable that you want to force remote distributed compilation on using the Icecream distributed compile support.


# orm_layer

up_date: 2025-10-20 15:10:00
name: openembedded-core
vcs_url: git://git.openembedded.org/openembedded-core
vcs_web_url: http://cgit.openembedded.org/openembedded-core
vcs_web_tree_base_url: http://cgit.openembedded.org/openembedded-core/tree/%path%?h=%branch%
vcs_web_file_base_url: http://cgit.openembedded.org/openembedded-core/tree/%path%?h=%branch%
summary: Core metadata
description:
  OpenEmbedded-Core is a layer containing the core metadata for current versions of OpenEmbedded. It is distro-less (can build a functional image with DISTRO = "") and contains only emulated machine support.


up_date: 2025-02-26 19:02:35
name: meta-hipos
vcs_url: https://github.com/DFE/meta-hipos.git
vcs_web_url: http://github.com/DFE/meta-hipos
vcs_web_tree_base_url: http://github.com/DFE/meta-hipos/tree/%branch%/
vcs_web_file_base_url: http://github.com/DFE/meta-hipos/blob/%branch%/
summary: BSP and related Distro for embedded devices from the DResearch Fahrzeugelektronik GmbH
description:
  HIPOS is an Open Source, Yocto/OpenEmbedded based BSP and Linux distribution for embedded devices mainly from the DResearch Fahrzeugelektronik GmbH.


up_date: 2025-10-29 17:10:52
name: meta-initramfs
vcs_url: git://git.openembedded.org/meta-openembedded
vcs_web_url: http://cgit.openembedded.org/meta-openembedded
vcs_web_tree_base_url: http://cgit.openembedded.org/meta-openembedded/tree/%path%?h=%branch%
vcs_web_file_base_url: http://cgit.openembedded.org/meta-openembedded/tree/%path%?h=%branch%
summary: initramfs tools
description:
  This layer contains the metadata necessary to build the klibc library and utilities (shared and static) plus other tools useful for the creation of small-sized initramfses.


up_date: 2024-09-20 08:09:30
name: meta-mono
vcs_url: https://github.com/DynamicDevices/meta-mono.git
vcs_web_url: http://github.com/DynamicDevices/meta-mono
vcs_web_tree_base_url: http://github.com/DynamicDevices/meta-mono/tree/%branch%/
vcs_web_file_base_url: http://github.com/DynamicDevices/meta-mono/blob/%branch%/
summary: Mono / dotNet
description:
  meta-mono is an OpenEmbedded layer that builds mono runtime and mono libraries to allow users to run .NET applications under linux built using OE. More recently contributors have added support for the dotNet runtime framework


up_date: 2025-10-29 17:10:25
name: meta-networking
vcs_url: git://git.openembedded.org/meta-openembedded
vcs_web_url: http://cgit.openembedded.org/meta-openembedded
vcs_web_tree_base_url: http://cgit.openembedded.org/meta-openembedded/tree/%path%?h=%branch%
vcs_web_file_base_url: http://cgit.openembedded.org/meta-openembedded/tree/%path%?h=%branch%
summary: Network-related software
description:
  This layer is intended to be a central point for networking-related
  packages and configuration.  It should be useful directly on top of
  oe-core and compliments meta-openembedded.  It should be primarily useful
  to the following groups:

        - Anyone building a small networking device (eg. a home router /
          bridge / switch).

        - Anyone wanting to add network services to their device (eg.
          anything that might benefit from a small ftp/tftp server)


up_date: 2018-09-27 00:09:15
name: meta-opie
vcs_url: git://git.openembedded.org/meta-opie
vcs_web_url: http://cgit.openembedded.org/meta-opie
vcs_web_tree_base_url: http://cgit.openembedded.org/meta-opie/tree/%path%?h=%branch%
vcs_web_file_base_url: http://cgit.openembedded.org/meta-opie/tree/%path%?h=%branch%
summary: Opie UI support
description:
  This layer provides the metadata necessary to build Opie, Qt/Embedded 2.3.10, related libraries and 3rd-party Qtopia applications.


up_date: 2018-09-27 00:09:15
name: meta-qt3
vcs_url: git://git.yoctoproject.org/meta-qt3
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3/tree/%path%?h=%branch%
summary: Qt 3.x support
description:
  Qt 3.x supportThis layer provides Qt 3.x libraries. Its intended use is for passing LSB tests as Qt3 is a requirement for LSB; however the libraries may also be used for any other purpose requiring Qt3.


up_date: 2018-09-27 00:09:15
name: meta-realtime
vcs_url: git://git.yoctoproject.org/meta-realtime
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-realtime
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-realtime/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-realtime/tree/%path%?h=%branch%
summary: Additional realtime support
description:
  This layer is intended to be a central point for realtime related kernel and
  system development. It also contains utilities, and configuration useful for
  tuning a realtime system. It should be useful directly on top of oe-core.  It
  should be primarily useful to the following groups:

        - Anyone working on Linux kernel realtime development (preempt-rt, 
          sched_dealine, posix realtime).

        - Anyone experimenting with alternative pairing of general purpose 
          OSs and realtime OS divisions. Whether that be AMP, userspace RTOS
          or realtime hypervisors.

        - Anyone working on cpu isolation, system partitioning and related userspace
          applications.

        - Anyone benchmarking and performance profiling a Linux system.


up_date: 2025-03-05 10:03:12
name: meta-virtualization
vcs_url: git://git.yoctoproject.org/meta-virtualization
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/%path%?h=%branch%
summary: Hypervisor, virtualization tool stack, and cloud support
description:
  This layer provides support for building Xen, KVM, Libvirt, and associated packages necessary for constructing OE-based virtualized solutions.


up_date: 2018-09-27 00:09:15
name: meta-chiefriver
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel Chief River platform BSP
description:
  BSP for the 'Chief River' platform (which consists of the Intel Ivy Bridge processor, plus the Panther Point PCH). This BSP assumes that the Ivy Bridge integrated graphics are being used.


up_date: 2018-09-27 00:09:15
name: meta-crownbay
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel Crown Bay platform BSP
description:
  BSP for the Intel Crown Bay platform, which consists of the Intel Atom E6xx processor,
  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).


up_date: 2018-09-27 00:09:15
name: meta-emenlow
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel eMenlow platform BSP
description:
  BSP for the Intel 'eMenlow' platform, consisting of the Intel Atom Z5xx processor, plus the Intel US15W System Controller Hub.


up_date: 2018-09-27 00:09:15
name: meta-jasperforest
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel Jasper Forest platform BSP
description:
  BSP for the Intel Jasper Forest platform, consisting of Intel Xeon C5500/C3500 processors combined with the Intel 3420 PCH chipset (Ibex Peak) making up the
  'Picket Post' reference board.


up_date: 2018-09-27 00:09:15
name: meta-n450
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel N450 platform BSP
description:
  BSP for the Intel Luna Pier platform, consisting of the Intel Atom E4xx processor (Pineview), plus the Intel 82801Hm I/O Controller. This is suitable for use with the Intel Embedded Development Board 1-N450 ("Black Sand").


up_date: 2018-09-27 00:09:15
name: meta-romley
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel Romley platform BSP
description:
  BSP for the Intel Romley Sandy Bridge / Ivy Bridge platform, which consists of Intel Xeon E5-2600 and E5-2400 Series processors, plus the Intel C604/C602-J chipset
  (Sandy Bridge-EP/EN + Patsburg) or Intel Xeon E5-2600
  and E5-2400 v2 Series processors with the Intel C604/C602-J chipset
  (Ivy Bridge-EP/EN + Patsburg).


up_date: 2018-09-27 00:09:15
name: meta-sugarbay
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Intel Sugar Bay platform BSP
description:
  BSP for the Intel Sugar Bay platform, consisting of the Intel Sandy Bridge processor,
  plus the Cougar Point PCH (Q67 Express or B65 Express chipsets).  This BSP assumes that the Sandy Bridge integrated graphics are being used.


up_date: 2018-09-27 00:09:15
name: meta-sys940x
vcs_url: git://git.yoctoproject.org/meta-intel
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/%path%?h=%branch%
summary: Inforce Computing SYS940x BSP
description:
  BSP for the Inforce Computing SYS940x boards, which utilise the Intel Queens Bay platform consisting of the Intel Atom E6xx processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).


up_date: 2018-09-27 00:09:15
name: meta-tlk
vcs_url: git://git.yoctoproject.org/meta-tlk
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-tlk
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-tlk/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-tlk/tree/%path%?h=%branch%
summary: Time Limited Kernel layer
description:
  This layer makes the appropriate kernel modifications to enable a 10 day time limit in the official BSP images produced using the Yocto Project autobuilder, in order to encourage people to produce their own images for production whilst still allowing the images to be useful for testing and debugging.


up_date: 2023-09-29 01:09:18
name: meta-luneos-backports-2-8
vcs_url: https://github.com/webOS-ports/meta-webos-ports
vcs_web_url: http://github.com/webOS-ports/meta-webos-ports
vcs_web_tree_base_url: http://github.com/webOS-ports/meta-webos-ports/tree/%branch%/
vcs_web_file_base_url: http://github.com/webOS-ports/meta-webos-ports/blob/%branch%/
summary: Backports from Yocto 2.8 Zeus used by LuneOS distribution
description:
  This is a layer where we backport recipes and bbclasses from newer Yocto (with minimal modifications needed to make it compatible with the old one we're using).

  That way when upgrading to newer Yocto we just delete all meta-luneos-backports-* layers and we shouldn't loose anything. Instead of searching for all backported changes in meta-luneos layer and separating luneos modifications to bbappend when the main recipe is already elsewhere in upstream.


up_date: 2018-10-02 19:10:51
name: meta-ivi
vcs_url: git://git.yoctoproject.org/meta-ivi
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/%path%?h=%branch%
summary: Collection of software related to In-Vehicle Infotainment systems
description:
  This layer's purpose is to add In-Vehicle Infotainment (IVI) support when
  used with Poky.  The goal is to be able to build a GENIVI compliant baseline
  image.


up_date: 2018-09-27 00:09:15
name: meta-netmodule
vcs_url: https://github.com/netmodule/meta-netmodule.git
vcs_web_url: http://github.com/netmodule/meta-netmodule
vcs_web_tree_base_url: http://github.com/netmodule/meta-netmodule/tree/%branch%/
vcs_web_file_base_url: http://github.com/netmodule/meta-netmodule/blob/%branch%/
summary: BSP Layer from NetModule for various boards
description:
  Contains recipes for SoMs and Eval Boards used by NetModule.
  Additionally there are some recipes included which are used by NetModule for development.


up_date: 2018-09-27 00:09:15
name: meta-gstreamer10
vcs_url: https://github.com/dv1/meta-gstreamer1.0.git
vcs_web_url: http://github.com/dv1/meta-gstreamer1.0
vcs_web_tree_base_url: http://github.com/dv1/meta-gstreamer1.0/tree/%branch%/
vcs_web_file_base_url: http://github.com/dv1/meta-gstreamer1.0/blob/%branch%/
summary: OpenEmbedded layer for GStreamer 1.0
description:
  This layer provides support for GStreamer 1.0 . It is intended to be used with danny and dylan, until GStreamer 1.0 support is integrated into oe-core.


up_date: 2018-09-27 00:09:15
name: meta-hamradio
vcs_url: https://github.com/hambedded-linux/meta-hamradio.git
vcs_web_url: http://github.com/hambedded-linux/meta-hamradio
vcs_web_tree_base_url: http://github.com/hambedded-linux/meta-hamradio/tree/%branch%/
vcs_web_file_base_url: http://github.com/hambedded-linux/meta-hamradio/blob/%branch%/
summary: Hamradio related software
description:
  This layer includes hamradio related packages and aims to provide a repository for all hamradio related applications.


up_date: 2018-09-27 00:09:15
name: meta-clutter
vcs_url: https://github.com/Guacamayo/meta-clutter.git
vcs_web_url: http://github.com/Guacamayo/meta-clutter
vcs_web_tree_base_url: http://github.com/Guacamayo/meta-clutter/tree/%branch%/
vcs_web_file_base_url: http://github.com/Guacamayo/meta-clutter/blob/%branch%/
summary: Recipes for cogl, clutter and friends
description:
  meta-clutter provides recipes for cogl, clutter and related packages (such as mx and mutter) and aims to provide frequent updates in keeping with upstream releases when possible.

  meta-clutter is intended for use with the current stable release of oe-core.


up_date: 2018-09-27 00:09:15
name: meta-sunxi
vcs_url: https://github.com/linux-sunxi/meta-sunxi
vcs_web_url: http://github.com/linux-sunxi/meta-sunxi
vcs_web_tree_base_url: http://github.com/linux-sunxi/meta-sunxi/tree/%branch%/
vcs_web_file_base_url: http://github.com/linux-sunxi/meta-sunxi/blob/%branch%/
summary: Allwinner sunxi board support
description:
  BSP for the Allwinner sunxi platform (http://linux-sunxi.org). This layer contains Machine definition for cubieboard, mele a1000/2000, olinuxino-a10, ...


up_date: 2022-04-10 17:04:40
name: meta-gumstix-extras
vcs_url: https://github.com/gumstix/meta-gumstix-extras.git
vcs_web_url: http://github.com/gumstix/meta-gumstix-extras
vcs_web_tree_base_url: http://github.com/gumstix/meta-gumstix-extras/tree/%branch%/
vcs_web_file_base_url: http://github.com/gumstix/meta-gumstix-extras/blob/%branch%/
summary: Gumstix board support extras (official)
description:
  Yocto layer for images and extra recipes for Gumstix products. This layer complements the meta-gumstix BSP layer.


up_date: 2018-09-27 00:09:15
name: meta-fsl-demos
vcs_url: https://github.com/Freescale/meta-fsl-demos.git
vcs_web_url: http://github.com/Freescale/meta-fsl-demos
vcs_web_tree_base_url: http://github.com/Freescale/meta-fsl-demos/tree/%branch%/
vcs_web_file_base_url: http://github.com/Freescale/meta-fsl-demos/blob/%branch%/
summary: OpenEmbedded/Yocto layer for Freescale's Demonstration images
description:
  This layer provides support for Freescale's Demonstration images for
  use with OpenEmbedded and/or Yocto Freescale's BSP layer.


up_date: 2018-09-27 00:09:15
name: meta-kernel-dev
vcs_url: git://git.yoctoproject.org/meta-yocto-kernel-extras
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto-kernel-extras
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto-kernel-extras/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto-kernel-extras/tree/%path%?h=%branch%
summary: Kernel development extras
description:
  A gathering place for extensions to the linux-yocto (or really any) kernel recipes that facilitate the creation and development of kernel features, BSPs or configuration.


up_date: 2018-09-27 00:09:15
name: meta-eca
vcs_url: git://git.yoctoproject.org/meta-eca
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/tree/%path%?h=%branch%
summary: Mobile access point
description:
  meta-eca is used to build ECA (Embedded Connectivity Appliance). ECA is a platform for building network appliances. One such use case is mobile access point which uses ConnMan tethering functionality to tether wifi, bluetooth, USB gadget and ethernet connections.


up_date: 2022-04-10 03:04:21
name: meta-minnow
vcs_url: git://git.yoctoproject.org/meta-minnow
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-minnow/tree/%path%?h=%branch%
summary: MinnowBoard BSP layer
description:
  BSP for the MinnowBoard v1, a board targeting the small and low-cost embedded market for the developer and maker community, based on an Intel Atom E640T processor coupled with an Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff = Queens Bay).


up_date: 2022-06-21 04:06:10
name: meta-security
vcs_url: git://git.yoctoproject.org/meta-security
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-security
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-security/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-security/tree/%path%?h=%branch%
summary: Security tools for Internet Connected devices
description:
  This layer provides security tools, hardening tools for Linux kernels and libraries for implementing security mechanisms.


up_date: 2018-09-27 00:09:15
name: meta-ro-rootfs
vcs_url: https://github.com/MentorEmbedded/meta-ro-rootfs
vcs_web_url: http://github.com/MentorEmbedded/meta-ro-rootfs
vcs_web_tree_base_url: http://github.com/MentorEmbedded/meta-ro-rootfs/tree/%branch%/
vcs_web_file_base_url: http://github.com/MentorEmbedded/meta-ro-rootfs/blob/%branch%/
summary: Staging area for improvements to read-only-rootfs handling
description:
  A temporary staging area for improvements to read-only root filesystem handling. To contribute to this layer, please fork and submit pull requests to the github repository.


up_date: 2018-09-27 00:09:15
name: meta-measured
vcs_url: https://github.com/flihp/meta-measured.git
vcs_web_url: http://github.com/flihp/meta-measured
vcs_web_tree_base_url: http://github.com/flihp/meta-measured/tree/%branch%/
vcs_web_file_base_url: http://github.com/flihp/meta-measured/blob/%branch%/
summary: Tools and utilities related to measuring software and trusted computing
description:
  meta-measured is a collection of recipes and configurations that enable software measurement in Linux distros based on OE. Currently this includes the open source TCG TSS, related TPM tools, and tools enabling the use of Intels TXT. Reference images are also provided as a reference for the use of these tools in minimal builds.

  My goals for this layer include:
  1) extending the measurement scheme to arbitrary software components (not just boot modules & fs images) at boot and runtime
  2) enabling measured launch for arbitrary system images
  3) supporting non-Intel platforms with hardware support for boot time measurements and the TPM.


up_date: 2023-09-29 03:09:49
name: meta-openstack-qemu
vcs_url: git://git.yoctoproject.org/meta-cloud-services
vcs_web_url: https://git.yoctoproject.org/meta-cloud-services
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-cloud-services/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-cloud-services/tree/%path%?h=%branch%
summary: OpenStack QEMU image support
description:
  Provides support configuring and deploying OpenStack images that are destined to be run under QEMU system emulation.


up_date: 2018-09-27 00:09:15
name: meta-openclovis
vcs_url: https://github.com/joaohf/meta-openclovis
vcs_web_url: http://github.com/joaohf/meta-openclovis
vcs_web_tree_base_url: http://github.com/joaohf/meta-openclovis/tree/%branch%/
vcs_web_file_base_url: http://github.com/joaohf/meta-openclovis/blob/%branch%/
summary: Layer to support SAFplus midleware components
description:
  SAFplus is a Midleware that provides libraries, GUI, and code generator to design multi-node (clustered) applications that are highly available, redundant, and scalable.

  This layer provide base components which is used by SAFplus.


up_date: 2018-09-27 00:09:15
name: meta-cloud-services
vcs_url: git://git.yoctoproject.org/meta-cloud-services
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/%path%?h=%branch%
summary: General package support for cloud and clustering development
description:
  Support libraries and packages that are not directly coupled to a particular cloud solution (i.e openstack).


up_date: 2025-09-05 12:09:24
name: meta-bytesatwork
vcs_url: https://github.com/bytesatwork/meta-bytesatwork.git
vcs_web_url: http://github.com/bytesatwork/meta-bytesatwork
vcs_web_tree_base_url: http://github.com/bytesatwork/meta-bytesatwork/tree/%branch%/
vcs_web_file_base_url: http://github.com/bytesatwork/meta-bytesatwork/blob/%branch%/
summary: Official distribution layer for bytesatwork's platforms
description:
  Official yocto distribution layer for bytesatwork's platforms.
  Supports byteDEVKIT-AM62X, byteDEVKIT-IMX8MM, byteDEVKIT-IMX8MP, byteDEVKIT-IMX93, and byteDEVKIT-STM32MP1.


up_date: 2022-04-10 04:04:53
name: meta-digi-arm
vcs_url: https://github.com/digi-embedded/meta-digi
vcs_web_url: https://github.com/digi-embedded/meta-digi
vcs_web_tree_base_url: https://github.com/digi-embedded/meta-digi/tree/%branch%/
vcs_web_file_base_url: https://github.com/digi-embedded/meta-digi/blob/%branch%/
summary: Support for Digi ConnectCore/ConnectCard Modules
description:
  This layer provides support for Digi's ConnnecCore platforms for use with OpenEmbedded and/or Yocto.


up_date: 2018-09-27 00:09:15
name: meta-digi-dey
vcs_url: https://github.com/digi-embedded/meta-digi
vcs_web_url: http://github.com/digi-embedded/meta-digi
vcs_web_tree_base_url: http://github.com/digi-embedded/meta-digi/tree/%branch%/
vcs_web_file_base_url: http://github.com/digi-embedded/meta-digi/blob/%branch%/
summary: Provides the Digi Embedded Yocto distribution images
description:
  This layer provides the Digi Embedded Yocto distribution images.  This builds on top of the core functionality provided by meta-digi-arm by providing additional contents for one's rootfs.

  This includes modifications and additions to the core tools available on one's userspace image as well as providing several convenient images that one can build for digi targets (e.g. dey-image-minimal, dey-image-graphical).


up_date: 2018-09-27 00:09:15
name: meta-alt-desktop-extras
vcs_url: https://github.com/sarnold/meta-alt-desktop-extras
vcs_web_url: http://github.com/sarnold/meta-alt-desktop-extras
vcs_web_tree_base_url: http://github.com/sarnold/meta-alt-desktop-extras/tree/%branch%/
vcs_web_file_base_url: http://github.com/sarnold/meta-alt-desktop-extras/blob/%branch%/
summary: Lightweight (legacy) X desktop, tools, and recipe extensions
description:
  Small-footprint lightweight X desktop with openbox, tint2 and basic apps, with system-level tools, compilers, and a few extras.  See the github wiki for more info.


up_date: 2023-12-20 20:12:32
name: meta-amd
vcs_url: git://git.yoctoproject.org/meta-amd
vcs_web_url: https://git.yoctoproject.org/meta-amd/
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/tree/%path%?h=%branch%
summary: AMD board support common layer (official)
description:
  Official layer for AMD common platform/board support. This layer contains common elements and relies on additional layers for each BSP.  Look for BSP layers to be listed separately.


up_date: 2023-09-28 21:09:16
name: meta-mel-support
vcs_url: https://github.com/MentorEmbedded/meta-mentor
vcs_web_url: http://github.com/MentorEmbedded/meta-mentor
vcs_web_tree_base_url: http://github.com/MentorEmbedded/meta-mentor/tree/%branch%/
vcs_web_file_base_url: http://github.com/MentorEmbedded/meta-mentor/blob/%branch%/
summary: Mentor Embedded Linux Support Layer for Yocto/OE
description:
  This layer holds the bits useful for Mentor Embedded Linux, but which aren't appropriate for inclusion in the distro layer.


up_date: 2018-09-27 00:09:15
name: meta-mentor-staging
vcs_url: https://github.com/MentorEmbedded/meta-mentor
vcs_web_url: http://github.com/MentorEmbedded/meta-mentor
vcs_web_tree_base_url: http://github.com/MentorEmbedded/meta-mentor/tree/%branch%/
vcs_web_file_base_url: http://github.com/MentorEmbedded/meta-mentor/blob/%branch%/
summary: Mentor Graphics Staging Layer for Yocto/OE
description:
  This layer holds the bits we need for Mentor Embedded Linux, but which we intend to get merged upstream. This is our staging area. Nothing should be in this layer permanently, other than layer.conf and associated bits.


up_date: 2021-06-02 15:06:47
name: meta-exynos
vcs_url: https://github.com/slimlogic/meta-exynos.git
vcs_web_url: http://github.com/slimlogic/meta-exynos
vcs_web_tree_base_url: http://github.com/slimlogic/meta-exynos/tree/%branch%/
vcs_web_file_base_url: http://github.com/slimlogic/meta-exynos/blob/%branch%/
summary: BSP layer for exynos based machines
description:
  Layer currently contains BSP for

   * Arndale
   * Arndale Octa
   * Chrome Book Snow (Samsung ARM Chromebook)

  Patches welcome for other machines.


up_date: 2022-04-10 18:04:19
name: meta-tizen
vcs_url: git://review.tizen.org/scm/bb/meta-tizen
summary: Tizen reference for the Yocto Project
description:
  Tizen reference for the Yocto Project.
  Tizen on Yocto is a project which aims at building a full Tizen image with the building Tools of the Yocto project. The project is hosted and developed on the Tizen web site, following Tizen platform development process and mirrored on Yocto repositories.


up_date: 2018-12-07 21:12:37
name: meta-wolfssl
vcs_url: https://github.com/wolfSSL/meta-wolfssl
vcs_web_url: http://github.com/wolfSSL/meta-wolfssl
vcs_web_tree_base_url: http://github.com/wolfSSL/meta-wolfssl/tree/%branch%/
vcs_web_file_base_url: http://github.com/wolfSSL/meta-wolfssl/blob/%branch%/
summary: Lightweight, portable, C-language-based SSL/TLS library
description:
  The wolfSSL embedded SSL/TLS library is a lightweight TLS library written in ANSI C and targeted for embedded, RTOS, and resource-constrained environments - primarily because of its small size, speed, and feature set. wolfSSL supports industry standards up to the current TLS 1.3 and DTLS 1.2 levels, is up to 20 times smaller than OpenSSL, and offers progressive ciphers such as ChaCha20, Curve25519, NTRU, and Blake2b. wolfSSL is able to use a FIPS 140-2 validated version of wolfCrypt if needed.


up_date: 2021-01-28 19:01:27
name: meta-kf5
vcs_url: https://invent.kde.org/packaging/yocto-meta-kf5
vcs_web_url: https://invent.kde.org/packaging/yocto-meta-kf5
vcs_web_tree_base_url: https://invent.kde.org/packaging/yocto-meta-kf5/tree/%branch%/%path%
vcs_web_file_base_url: https://invent.kde.org/packaging/yocto-meta-kf5/blob/%branch%/%path%
summary: KDE Frameworks 5
description:
  The KDE Frameworks 5 consists of a set of Qt add-on modules extending and improving Qt. Developed by and for the KDE project, but in no way tied to the KDE Plasma desktop.


up_date: 2018-09-27 00:09:15
name: meta-nilrt
vcs_url: https://github.com/ni/meta-nilrt.git
vcs_web_url: http://github.com/ni/meta-nilrt
vcs_web_tree_base_url: http://github.com/ni/meta-nilrt/tree/%branch%/
vcs_web_file_base_url: http://github.com/ni/meta-nilrt/blob/%branch%/
summary: NI Linux Real-Time Distribution
description:
  The NI Linux Real-Time distribution supplies a real-time operating system that runs on National Instruments RT targets, such as NI CompactRIO.


up_date: 2018-09-27 00:09:15
name: meta-crosswalk
vcs_url: https://github.com/crosswalk-project/meta-crosswalk
vcs_web_url: http://github.com/crosswalk-project/meta-crosswalk
vcs_web_tree_base_url: http://github.com/crosswalk-project/meta-crosswalk/tree/%branch%/
vcs_web_file_base_url: http://github.com/crosswalk-project/meta-crosswalk/blob/%branch%/
summary: Crosswalk is a web runtime for ambitious HTML5 applications.
description:
  Many HTML5 applications need more than just a browser  they need all the features of a native application.

  Crosswalk provides all the features of a modern browser, combined with deep device integration and an API for adding native extensions. It is especially suited to mobile devices, with support for Android, Tizen and Yocto.


up_date: 2018-09-27 00:09:15
name: meta-musl
vcs_url: https://github.com/kraj/meta-musl.git
vcs_web_url: http://github.com/kraj/meta-musl
vcs_web_tree_base_url: http://github.com/kraj/meta-musl/tree/%branch%/
vcs_web_file_base_url: http://github.com/kraj/meta-musl/blob/%branch%/
summary: Support for the musl C library
description:
  Provides musl as an alternative to system C library for OpenEmbedded based distributions along with uClibc and eglibc/glibc


up_date: 2018-09-27 00:09:15
name: meta-go
vcs_url: https://github.com/mem/oe-meta-go
vcs_web_url: http://github.com/mem/oe-meta-go
vcs_web_tree_base_url: http://github.com/mem/oe-meta-go/tree/%branch%/
vcs_web_file_base_url: http://github.com/mem/oe-meta-go/blob/%branch%/
summary: This layer provides support for cross-compiling programs written in Go language
description:
  Cross-compiling Go projects is pretty easy, as it builds statically linked binaries which don't care what version of OS the target runs, as it doesn't use the Standard C Library. However, many system-level projects started to emerge recently, and Docker is a good example.


up_date: 2023-09-29 03:09:23
name: meta-cgl
vcs_url: git://git.yoctoproject.org/meta-cgl
vcs_web_url: https://git.yoctoproject.org/meta-cgl
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-cgl/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-cgl//tree/%path%?h=%branch%
summary: Carrier Grade Linux compliance packages
description:
  The meta-cgl layer tries to offer CGL (Carrier Grade Linux) compliant packages to be used for a Linux distribution.
  The layer contains a core package group (packagegroup-cgl.bb) that
  should aggregate all the other available package groups.
  The recommandation is to group all CGL compliant features into specific
  package groups.
  An CGL compliant Linux image is also available into the layer. Its use
  is to facilitate the development of a CGL compliant OS.
  The core image name is: cgl-image-core.bb


up_date: 2023-09-28 22:09:10
name: meta-ivi-demo
vcs_url: git://git.yoctoproject.org/meta-ivi
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/%path%?h=%branch%
summary: GENIVI Yocto Demo Platform
description:
  The GENIVI Demo Platform is a technology demonstrator.

  * It showcases a concrete and live incarnation of the GENIVI software and design.
  * It is made available by the GENIVI Alliance as a starter kit that can be publicly downloaded and customized by the wider developer community.


up_date: 2022-04-24 19:04:12
name: meta-spec
vcs_url: https://ohwr.org/project/meta-spec.git
vcs_web_url: http://www.ohwr.org/projects/meta-spec/repository
summary: Support for the Simple PCIe FMC Carrier (SPEC)
description:
  The Simple PCIe FMC Carrier (SPEC) is an FMC carrier that can hold one FMC card and an SFP connector. On the PCIe side it has a 4-lane interface, while the FMC mezzanine slot uses a low-pin count connector. This board is optimised for cost and is usable with most of the FMC cards designed within the OHR project (e.g. ADC cards, Fine Delay). The board is commercially available.

  This Yocto/OpenEmbedded layer provides support for both the SPEC Software and Getting Started projects, from gateware bitstreams, user-space tools, dynamic libraries and kernel modules. It can be used with both x86 and x86-64 target machines featuring one or more SPEC boards.


up_date: 2018-09-27 00:09:15
name: meta-openhab
vcs_url: https://github.com/ulfwin/meta-openhab
vcs_web_url: http://github.com/ulfwin/meta-openhab
vcs_web_tree_base_url: http://github.com/ulfwin/meta-openhab/tree/%branch%/
vcs_web_file_base_url: http://github.com/ulfwin/meta-openhab/blob/%branch%/
summary: Yocto layer providing openHAB (home automation software)
description:
  openHAB provides open source automation software for your home. 

  The tasks of the layer are:
  - download runtime files and place in rootfs
  - download addon files and place in rootfs
  - append meta-oracle-java to place a link to the executable in a bin directory

  Although addons are included, wanted addons has to be manually copied over to the runtime location


up_date: 2018-09-27 00:09:15
name: meta-intel-iot-middleware
vcs_url: git://git.yoctoproject.org/meta-intel-iot-middleware
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware/tree/%path%?h=%branch%
summary: Shared middleware recipes for Intel IoT platforms
description:
  This was the middleware layer for the Intel IoT developer kit. Here are
  middleware parts useful for the iot-devkit but not shipped as part of meta-oe
  or backports from newer versions of meta-oe which are not appropriate for
  meta-oe itself.


up_date: 2022-04-10 03:04:08
name: meta-intel-quark
vcs_url: git://git.yoctoproject.org/meta-intel-quark
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-quark
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-quark/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-quark/tree/%path%?h=%branch%
summary: Intel Quark platform support
description:
  This is the BSP layer for the Intel Quark SoC as found in the Intel Galileo gen1 &
  gen2 development boards.


up_date: 2018-09-27 00:09:15
name: meta-intel-galileo
vcs_url: git://git.yoctoproject.org/meta-intel-galileo
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-galileo
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-galileo/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-galileo/tree/%path%?h=%branch%
summary: Intel Galileo platform support
description:
  Layer providing additional support for the Arduino-compatible Intel Galileo board (gen1 &
  gen2). Things that are generic to the Quark SoC are handled by the meta-intel-quark layer.


up_date: 2018-09-27 00:09:15
name: meta-debian
vcs_url: https://github.com/meta-debian/meta-debian.git
vcs_web_url: http://github.com/meta-debian/meta-debian
vcs_web_tree_base_url: http://github.com/meta-debian/meta-debian/tree/%branch%/
vcs_web_file_base_url: http://github.com/meta-debian/meta-debian/blob/%branch%/
summary: Using Debian source code to bitbake images
description:
  Meta-debian enables to use Debian source code to build root filesystem. On Daisy branch, it focuses to use Debian 8 (jessie) sources. Please check the README for more detail.

  Requirements of current implementation as the follows: 
    (1) All package sources needs to be converted to git repository one by one. 
    (2) Tested on Debian 8 (x86-32bit and x86-64bit)


up_date: 2018-09-27 00:09:15
name: meta-security-smack
vcs_url: https://github.com/01org/meta-intel-iot-security.git
vcs_web_url: http://github.com/01org/meta-intel-iot-security
vcs_web_tree_base_url: http://github.com/01org/meta-intel-iot-security/tree/%branch%/
vcs_web_file_base_url: http://github.com/01org/meta-intel-iot-security/blob/%branch%/
summary: adds the Smack LSM to OpenEmbedded distros
description:
  meta-security-smack adds Smack support and file system setup via several .bbappends and the userspace utility library.


up_date: 2018-09-27 00:09:15
name: meta-security-framework
vcs_url: https://github.com/01org/meta-intel-iot-security.git
vcs_web_url: http://github.com/01org/meta-intel-iot-security
vcs_web_tree_base_url: http://github.com/01org/meta-intel-iot-security/tree/%branch%/
vcs_web_file_base_url: http://github.com/01org/meta-intel-iot-security/blob/%branch%/
summary: adds higher-level security middleware and tools
description:
  The layer adds userspace components like Cynara, a daemon for managing access permissions.

  It can be used in combination with meta-security-smack, but may also be useful without that.


up_date: 2018-09-27 00:09:15
name: meta-odroid
vcs_url: https://github.com/akuster/meta-odroid
vcs_web_url: http://github.com/akuster/meta-odroid
vcs_web_tree_base_url: http://github.com/akuster/meta-odroid/tree/%branch%/
vcs_web_file_base_url: http://github.com/akuster/meta-odroid/blob/%branch%/
summary: This support the series of Odroid boards made by Hardkernel
description:
  The ODROID is a series of single-board computers and tablet computers created by Hardkernel Co., Ltd., an open-source hardware company.


up_date: 2018-09-27 00:09:15
name: meta-qt5-extra
vcs_url: https://github.com/schnitzeltony/meta-qt5-extra.git
vcs_web_url: http://github.com/schnitzeltony/meta-qt5-extra
vcs_web_tree_base_url: http://github.com/schnitzeltony/meta-qt5-extra/tree/%branch%/
vcs_web_file_base_url: http://github.com/schnitzeltony/meta-qt5-extra/blob/%branch%/
summary: Desktop environments and applications based on qt5
description:
  Recipes to build desktop environments and applications based on Qt5 e.g KDE5 / lxqt / hawaii / sddm ...


up_date: 2019-12-04 08:12:55
name: meta-atmel
vcs_url: https://github.com/linux4sam/meta-atmel.git
vcs_web_url: http://github.com/linux4sam/meta-atmel
vcs_web_tree_base_url: http://github.com/linux4sam/meta-atmel/tree/%branch%/
vcs_web_file_base_url: http://github.com/linux4sam/meta-atmel/blob/%branch%/
summary: Official Yocto Project layer for Microchip SoCs
description:
  This layer provides support for Microchip microprocessors (aka AT91).
  It is the official layer built by Microchip employees and the AT91 community.

  For more information about the Microchip MPU product line see:
  http://www.microchip.com/design-centers/32-bit-mpus
  Linux & Open Source on Microchip microprocessors:
  http://www.linux4sam.org
  The official Linux4SAM demos are built with this meta-atmel Yocto Project layer.


up_date: 2018-09-27 00:09:15
name: meta-maker
vcs_url: http://git.yoctoproject.org/git/meta-maker
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-maker
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-maker/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-maker/tree/%path%?h=%branch%
summary: OpenEmbedded recipes for makers.
description:
  This layer is intended to be the home of applications and tools for Makers 
  in OpenEmbedded. While initial focus is on 3D printing, this is by no means
  intended to be an exclusive layer. Other applications for CNC machining,
  lasercutting, knitting, etc. are expected to follow and are welcome.


up_date: 2018-09-27 00:09:15
name: meta-security-isafw
vcs_url: https://github.com/01org/meta-security-isafw
vcs_web_url: http://github.com/01org/meta-security-isafw
vcs_web_tree_base_url: http://github.com/01org/meta-security-isafw/tree/%branch%/
vcs_web_file_base_url: http://github.com/01org/meta-security-isafw/blob/%branch%/
summary: Image Security Analyser FW layer
description:
  meta-security-isafw is an OE layer that allows enabling the Image Security Analysis Framework (isafw) for your image builds.

  The primary purpose of isafw is to provide an extensible framework for analysing different security aspects of images during the build process.

  The isafw project itself can be found at https://github.com/01org/isafw

  The framework supports a number of callbacks (such as process_package(), process_filesystem(), and etc.) that are invoked by the bitbake during different stages of package and image build. These callbacks are then forwarded for processing to the available ISA FW plug-ins that have registered for these callbacks. Plug-ins can do their own processing on each stage of the build process and produce security reports.


up_date: 2018-09-27 00:09:15
name: meta-overc
vcs_url: https://github.com/OverC/meta-overc.git
vcs_web_url: http://github.com/OverC/meta-overc
vcs_web_tree_base_url: http://github.com/OverC/meta-overc/tree/%branch%/
vcs_web_file_base_url: http://github.com/OverC/meta-overc/blob/%branch%/
summary: Full featured, container based distribution
description:
  OverC is a distribution composed of building blocks that implement a set of related functionality. Examples are:

  dom0: provides control services to the platform and is responsible for launching other containers in the system. Dom0 is not manipulated by non admin users.

  dom1: provides system services (such as ntpd, etc) to the platform. This is not used by a typical user.

  domE: provides full 'enterprise' functionality. This includes man pages, development tools, graphical desktop, etc. This domain is the primary environment for most users.

  OverC also has two essential image types, that provide a foundation for the
  container runtimes. These are: pod-builder: This is the image which lists all the packages required to boot the platform. pod-builder is also capable of self hosting and building the platform itself. pod-essential: This is a minimal runtime which is used for both the installer and pod-essential in the fully assembled system.


up_date: 2018-09-27 00:09:15
name: meta-webkit
vcs_url: https://github.com/Igalia/meta-webkit
vcs_web_url: http://github.com/Igalia/meta-webkit
vcs_web_tree_base_url: http://github.com/Igalia/meta-webkit/tree/%branch%/
vcs_web_file_base_url: http://github.com/Igalia/meta-webkit/blob/%branch%/
summary: WebKit engines and browsers: WPE / WebKitGTK+
description:
  This layer provides recipes of WebKit based engines and browsers for use with OpenEmbedded and/or Yocto. Currently it provides recipes for WPE and WebKitGTK+


up_date: 2018-09-27 00:09:16
name: meta-chip
vcs_url: https://github.com/agherzan/meta-chip.git
vcs_web_url: http://github.com/agherzan/meta-chip
vcs_web_tree_base_url: http://github.com/agherzan/meta-chip/tree/%branch%/
vcs_web_file_base_url: http://github.com/agherzan/meta-chip/blob/%branch%/
summary: Yocto BSP layer for C.H.I.P. boards
description:
  C.H.I.P. are popular as known to be the first 9$ computer. This layer adds yocto support for this board.


up_date: 2018-09-27 00:09:16
name: meta-pareon
vcs_url: https://github.com/vectorfabrics/meta-pareon
vcs_web_url: http://github.com/vectorfabrics/meta-pareon
vcs_web_tree_base_url: http://github.com/vectorfabrics/meta-pareon/tree/%branch%/
vcs_web_file_base_url: http://github.com/vectorfabrics/meta-pareon/blob/%branch%/
summary: This layer automates using Pareon Verify with OpenEmbedded
description:
  Vector Fabrics' Pareon tool suite helps programmers to find potential parallelism (Pareon Profile) or software bugs (Pareon Verify) in their software.

  The Pareon tools work by instrumenting source code during compilation and then observing the behaviour at run-time. This is also called "dynamic analysis".

  By popular request, we created a meta-pareon layer to be used to instrument base libraries and applications in the platform that is built using bitbake.


up_date: 2018-09-27 00:09:16
name: meta-qt4
vcs_url: git://git.yoctoproject.org/meta-qt4
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt4/tree/%path%?h=%branch%
summary: Qt 4.x support
description:
  This layer provides Qt 4.x libraries as well as applications. Its primary use is for passing LSB tests as Qt4 is a requirement for LSB; however the libraries may also be used for any other purpose requiring Qt4.


up_date: 2018-09-27 00:09:16
name: meta-axon
vcs_url: https://github.com/joaohf/meta-axon
vcs_web_url: http://github.com/joaohf/meta-axon
vcs_web_tree_base_url: http://github.com/joaohf/meta-axon/tree/%branch%/
vcs_web_file_base_url: http://github.com/joaohf/meta-axon/blob/%branch%/
summary: Using Erlang on YP
description:
  This layer's purpose is to create a set of examples to guide meta-erlang users how to set and use Erlang with Yocto Project


up_date: 2018-09-27 00:09:16
name: meta-jz-mips
vcs_url: https://github.com/leon-anavi/meta-jz-mips.git
vcs_web_url: http://github.com/leon-anavi/meta-jz-mips
vcs_web_tree_base_url: http://github.com/leon-anavi/meta-jz-mips/tree/%branch%/
vcs_web_file_base_url: http://github.com/leon-anavi/meta-jz-mips/blob/%branch%/
summary: BSP for devices with Ingenic MIPS SoC.
description:
  BSP for devices with Ingenic MIPS SoC. This layer contains Machine definition for Imagination Ci20 with Ingenic JZ4780.


up_date: 2018-09-27 00:09:16
name: meta-openwrt
vcs_url: https://github.com/kraj/meta-openwrt
vcs_web_url: http://github.com/kraj/meta-openwrt
vcs_web_tree_base_url: http://github.com/kraj/meta-openwrt/tree/%branch%/
vcs_web_file_base_url: http://github.com/kraj/meta-openwrt/blob/%branch%/
summary: OE Metadata for OpenWRT packages
description:
  There are several packages which are unique to OpenWRT. This layer is collection of recipes for OpenEmbedded Infrastructure to be able to build those packages.


up_date: 2018-09-27 00:09:16
name: meta-cpan
vcs_url: https://github.com/rehsack/meta-cpan.git
vcs_web_url: http://github.com/rehsack/meta-cpan
vcs_web_tree_base_url: http://github.com/rehsack/meta-cpan/tree/%branch%/
vcs_web_file_base_url: http://github.com/rehsack/meta-cpan/blob/%branch%/
summary: CPAN distributions as meant by CPAN authors
description:
  meta-cpan provides recipes for openembedded packaging distributions as they meant by the CPAN authors.


up_date: 2018-09-27 00:09:16
name: meta-office
vcs_url: https://github.com/schnitzeltony/meta-office.git
vcs_web_url: http://github.com/schnitzeltony/meta-office
vcs_web_tree_base_url: http://github.com/schnitzeltony/meta-office/tree/%branch%/
vcs_web_file_base_url: http://github.com/schnitzeltony/meta-office/blob/%branch%/
summary: Office applications and libs
description:
  This layer contains libreoffice recipes, import filters and helper libraries required by libreoffice.


up_date: 2018-09-27 00:09:16
name: meta-security-rockwell
vcs_url: https://github.com/IrdetoServices/meta-security-rockwell.git
vcs_web_url: http://github.com/IrdetoServices/meta-security-rockwell
vcs_web_tree_base_url: http://github.com/IrdetoServices/meta-security-rockwell/tree/%branch%/
vcs_web_file_base_url: http://github.com/IrdetoServices/meta-security-rockwell/blob/%branch%/
summary:
  meta-security-rockwell is an OE layer that assists developers in hardening their Yocto-built systems, focusing on the Daisy release.

description:
  meta-security-rockwell is an OE layer that assists developers in hardening their Yocto-built systems, focusing on the Daisy release.

  Eventually, meta-security-rockwell should fail the build on security issues, requiring an explicit exemption (similar to accepting licenses). At present, security issues found in a build will be (at least) noisy. We have some work to do before we get this layer to where we want it and help is welcomed.

  Currently, this layer brings together components from the following open source projects

  meta-security-isafw -- we enable the security build flags audit (CFA) and make patches to make the isafw layer work in daisy
  grsec (a small piece thereof) -- we extract the MPROTECT kernel patch and add a bbclass to grant wx exceptions to applications via bitbake variables
  the security_flags.inc file of yocto/poky -- we 'automatically' enable these within this layer
  This layer also adds the following:

  a kernel config checker which we have built around a set of hardening recommendations for Linux


up_date: 2018-09-27 00:09:16
name: meta-rslsync
vcs_url: https://github.com/imyller/meta-rslsync.git
vcs_web_url: http://github.com/imyller/meta-rslsync
vcs_web_tree_base_url: http://github.com/imyller/meta-rslsync/tree/%branch%/
vcs_web_file_base_url: http://github.com/imyller/meta-rslsync/blob/%branch%/
summary: Resilio Sync recipes
description:
  Resilio Sync from Resilio Inc. is a simple tool that applies P2P protocol for direct live folder sync with maximum security, network speed and storage capacity. It has native versions for Mac, Windows and Linux, as well as native NAS integration.

  The scope of this layer is to provide latest OpenEmbedded package recipes for server version of Resilio Sync.


up_date: 2023-12-20 20:12:49
name: meta-seattle
vcs_url: git://git.yoctoproject.org/meta-amd
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/tree/%path%?h=%branch%
summary: BSP for AMD AMDs 64bit ARM-based processor (codenamed "Seattle")
description:
  BSP for the AMD Opteron A1100-Series, AMDs first 64-bit ARM-based processor, codenamed "Seattle". Support for running 32b applications included.


up_date: 2018-09-27 00:09:16
name: meta-swupd
vcs_url: git://git.yoctoproject.org/meta-swupd
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-swupd
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-swupd/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-swupd/tree/%path%?h=%branch%
summary: swupd (software updater from Clear Linux) integration layer
description:
  Metadata to enable integration of the swupd (https://clearlinux.org/features/software-update) software updater into an image.


up_date: 2018-09-27 00:09:16
name: meta-talologger
vcs_url: https://github.com/hlounent/meta-talologger
vcs_web_url: http://github.com/hlounent/meta-talologger
vcs_web_tree_base_url: http://github.com/hlounent/meta-talologger/tree/%branch%/
vcs_web_file_base_url: http://github.com/hlounent/meta-talologger/blob/%branch%/
summary: Packages the taloLogger home automation data collection software suite
description:
  meta-talologger provides OpenEmbedded metadata for the taloLogger home automation software suite.

  Additionally meta-talologger provides a taloLogger image for Raspberry Pi, which directly allows for building a completely custom image for Raspberry Pi that contains taloLogger software.

  See http://olammi.iki.fi/sw/taloLogger/ for more information on the taloLogger software suite.


up_date: 2018-09-27 00:09:16
name: meta-openbmc
vcs_url: https://github.com/facebook/openbmc
vcs_web_url: http://github.com/facebook/openbmc
vcs_web_tree_base_url: http://github.com/facebook/openbmc/tree/%branch%/
vcs_web_file_base_url: http://github.com/facebook/openbmc/blob/%branch%/
summary:
  OpenBMC is an open software framework to build a complete Linux image for a Board Management Controller (BMC).

description:
  A BMC is a specialized controller embedded in servers. It often comes in the form of a system-on-chip (SoC), with its own CPU, memory, and storage and lots of IO. A BMC connects to sensors to read environmental conditions and to fans to control temperature. It also provides other system management functions, including remote power control, serial over LAN, and monitoring and error logging of the server host CPU and memory.

  By itself, BMC hardware is a computer system. Compared with modern computer systems, the hardware resources in a BMC are very limited. A slow CPU, less than 32 MB flash as storage, and less than 256 MB RAM are common in BMC hardware. Because of this, OpenBMC is designed as a complete Linux distribution, with flexibility to be customized to support different BMC SoC or boards.

  The OpenBMC image includes a bootloader (u-boot), a Linux kernel, open source packages, and board-specific packages:

  - Both the bootloader and the Linux kernel include various hardware drivers for the BMC SoC, including an i2c driver, USB driver, PWM driver, and SPI driver.
  - The open source packages include common applications such as BusyBox, i2c-tools, lm-sensors, OpenSSH, and Python.
  - The board-specific packages include initialization scripts and tools for a particular board. For example, it includes a tool to dump asset info from the EEPROM and a fan-controller daemon to control the fan speed based on environment readings.

  Please see https://code.facebook.com/posts/1601610310055392/introducing-openbmc-an-open-software-framework-for-next-generation-system-management/ for more information.


up_date: 2018-09-27 00:09:16
name: meta-mender-core
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: Mender over-the-air (OTA) software updater
description:
  Mender is an image-based software updater tightly integrated with the Yocto project, licensed under the Apache License Version 2.0 and written in Golang. Mender uses an A/B dual rootfs+kernel partition layout for update resiliency, to handle power loss, storage errors and other failures that could otherwise brick a device.

  Mender is a client-server application, where the client runs on the target device, allowing updates to be deployed remotely.

  This meta layer compiles the Mender client and contains the required configuration to partition the target device and create sdcard images.

  You may also need to include a layer specific to your machine, e.g. `meta-mender-raspberrypi` or `meta-mender-qemu`. See the documentation for more information on how to use this layer: https://docs.mender.io/Artifacts/Building-Mender-Yocto-image.


up_date: 2023-09-29 01:09:44
name: meta-agl
vcs_url: https://git.automotivelinux.org/AGL/meta-agl
vcs_web_url: https://git.automotivelinux.org/AGL/meta-agl/
vcs_web_tree_base_url: https://git.automotivelinux.org/AGL/meta-agl/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.automotivelinux.org/AGL/meta-agl/tree/%path%?h=%branch%
summary: Automotive Grade Linux (distro layer)
description:
  This layer contains the Automotive Grade Linux distribution part and can be built on-top of OE. 

  It provides minimal images without the UI part. 

  For the UI part you'll have to add the meta-agl-demo layer, too.


up_date: 2023-09-29 02:09:50
name: meta-agl-demo
vcs_url: https://git.automotivelinux.org/AGL/meta-agl-demo
vcs_web_url: https://git.automotivelinux.org/AGL/meta-agl-demo
vcs_web_tree_base_url: https://git.automotivelinux.org/AGL/meta-agl-demo/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.automotivelinux.org/AGL/meta-agl-demo/tree/%path%?h=%branch%
summary: Automotive Grade Linux (demo apps layer)
description:
  This layer contains the Automotive Grade Linux UI/Framework/Demo and can be built on-top of OE and meta-agl. 

  It provides the image 'agl-demo-platform' .

  Dependency is "meta-agl"


up_date: 2018-09-27 00:09:16
name: meta-golang
vcs_url: https://github.com/madisongh/meta-golang
vcs_web_url: http://github.com/madisongh/meta-golang
vcs_web_tree_base_url: http://github.com/madisongh/meta-golang/tree/%branch%/
vcs_web_file_base_url: http://github.com/madisongh/meta-golang/blob/%branch%/
summary: Go language support
description:
  Layer for building the Go toolchain, along with classes and recipes for cross-building Go packages for OE-Core based projects.

  Supports automatic creation of ptest packages that map to the go test framework.


up_date: 2023-09-28 22:09:21
name: meta-resin-daisy
vcs_url: https://github.com/resin-os/meta-resin
vcs_web_url: http://github.com/resin-os/meta-resin
vcs_web_tree_base_url: http://github.com/resin-os/meta-resin/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/meta-resin/blob/%branch%/
summary: Base resinOS layer (daisy)
description:
  The base resinOS layer which provides components for running resin on supported machines. Can be used in conjunction with resin infrastructure or simply for running docker containers on various targets.

  This sub-layer contains daisy specific changes and depends on the main meta-resin-common layer.


up_date: 2023-09-28 22:09:36
name: meta-resin-fido
vcs_url: https://github.com/resin-os/meta-resin
vcs_web_url: http://github.com/resin-os/meta-resin
vcs_web_tree_base_url: http://github.com/resin-os/meta-resin/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/meta-resin/blob/%branch%/
summary: Base resinOS layer (fido)
description:
  The base resinOS layer which provides components for running resin on supported machines. Can be used in conjunction with resin infrastructure or simply for running docker containers on various targets.

  This sub-layer contains fido specific changes and depends on the main meta-resin-common layer.


up_date: 2023-09-28 22:09:33
name: meta-resin-jethro
vcs_url: https://github.com/resin-os/meta-resin
vcs_web_url: http://github.com/resin-os/meta-resin
vcs_web_tree_base_url: http://github.com/resin-os/meta-resin/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/meta-resin/blob/%branch%/
summary: Base resinOS layer (jethro)
description:
  The base resinOS layer which provides components for running resin on supported machines. Can be used in conjunction with resin infrastructure or simply for running docker containers on various targets.

  This sub-layer contains jethro specific changes and depends on the main meta-resin-common layer.


up_date: 2021-10-11 11:10:44
name: meta-resin-common
vcs_url: https://github.com/resin-os/meta-resin
vcs_web_url: http://github.com/resin-os/meta-resin
vcs_web_tree_base_url: http://github.com/resin-os/meta-resin/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/meta-resin/blob/%branch%/
summary: Base resinOS layer (common)
description:
  The base resinOS layer which provides components for running resin on supported machines. Can be used in conjunction with resin infrastructure or simply for running docker containers on various targets.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:59
name: meta-resin-raspberrypi
vcs_url: https://github.com/resin-os/resin-raspberrypi
vcs_web_url: http://github.com/resin-os/resin-raspberrypi
vcs_web_tree_base_url: http://github.com/resin-os/resin-raspberrypi/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-raspberrypi/blob/%branch%/
summary: Raspberry Pi resinOS layer
description:
  This layer adds resinOS support on Raspberry Pi boards.


  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2021-10-11 11:10:59
name: meta-resin-zc702
vcs_url: https://github.com/resin-os/resin-zc702
vcs_web_url: http://github.com/resin-os/resin-zc702
vcs_web_tree_base_url: http://github.com/resin-os/resin-zc702/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-zc702/blob/%branch%/
summary: Zynq ZC702 resinOS layer
description:
  This layer adds resinOS support on Zynq ZC702 boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:21
name: meta-resin-ts
vcs_url: https://github.com/resin-os/resin-ts
vcs_web_url: http://github.com/resin-os/resin-ts
vcs_web_tree_base_url: http://github.com/resin-os/resin-ts/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-ts/blob/%branch%/
summary: Technologic resinOS layer
description:
  This layer adds resinOS support on Technologic boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2021-10-11 11:10:38
name: meta-resin-toradex
vcs_url: https://github.com/resin-os/resin-toradex
vcs_web_url: http://github.com/resin-os/resin-toradex
vcs_web_tree_base_url: http://github.com/resin-os/resin-toradex/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-toradex/blob/%branch%/
summary: Toradex resinOS layer
description:
  This layer adds resinOS support on Toradex boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:45
name: meta-resin-qemu
vcs_url: https://github.com/resin-os/resin-qemu
vcs_web_url: http://github.com/resin-os/resin-qemu
vcs_web_tree_base_url: http://github.com/resin-os/resin-qemu/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-qemu/blob/%branch%/
summary: Qemu resinOS layer
description:
  This layer adds resinOS support on Qemu boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2021-10-11 11:10:42
name: meta-resin-parallella
vcs_url: https://github.com/resin-os/resin-parallella
vcs_web_url: http://github.com/resin-os/resin-parallella
vcs_web_tree_base_url: http://github.com/resin-os/resin-parallella/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-parallella/blob/%branch%/
summary: Parallella resinOS layer
description:
  This layer adds resinOS support on Parallella boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:06
name: meta-resin-odroid
vcs_url: https://github.com/resin-os/resin-odroid
vcs_web_url: http://github.com/resin-os/resin-odroid
vcs_web_tree_base_url: http://github.com/resin-os/resin-odroid/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-odroid/blob/%branch%/
summary: Odroid resinOS layer
description:
  This layer adds resinOS support on Odroid boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:35
name: meta-resin-genericx86
vcs_url: https://github.com/resin-os/resin-intel
vcs_web_url: http://github.com/resin-os/resin-intel
vcs_web_tree_base_url: http://github.com/resin-os/resin-intel/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-intel/blob/%branch%/
summary: Intel resinOS layer
description:
  This layer adds resinOS support on Intel boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:56
name: meta-resin-fsl-arm
vcs_url: https://github.com/resin-os/resin-fsl-arm
vcs_web_url: http://github.com/resin-os/resin-fsl-arm
vcs_web_tree_base_url: http://github.com/resin-os/resin-fsl-arm/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-fsl-arm/blob/%branch%/
summary: Freescale ARM resinOS layer
description:
  This layer adds resinOS support on Freescale ARM boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:13
name: meta-resin-edison
vcs_url: https://github.com/resin-os/resin-edison
vcs_web_url: http://github.com/resin-os/resin-edison
vcs_web_tree_base_url: http://github.com/resin-os/resin-edison/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-edison/blob/%branch%/
summary: Edison resinOS layer
description:
  This layer adds resinOS support on Intel Edison boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:28
name: meta-resin-beaglebone
vcs_url: https://github.com/resin-os/resin-beaglebone
vcs_web_url: http://github.com/resin-os/resin-beaglebone
vcs_web_tree_base_url: http://github.com/resin-os/resin-beaglebone/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-beaglebone/blob/%branch%/
summary: Beaglebone resinOS layer
description:
  This layer adds resinOS support on Beaglebone boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2023-09-28 22:09:15
name: meta-resin-artik
vcs_url: https://github.com/resin-os/resin-artik
vcs_web_url: http://github.com/resin-os/resin-artik
vcs_web_tree_base_url: http://github.com/resin-os/resin-artik/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-artik/blob/%branch%/
summary: Artik resinOS layer
description:
  This layer adds resinOS support on Artik boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2021-10-11 11:10:43
name: meta-resin-via-arm
vcs_url: https://github.com/resin-os/resin-via-arm
vcs_web_url: http://github.com/resin-os/resin-via-arm
vcs_web_tree_base_url: http://github.com/resin-os/resin-via-arm/tree/%branch%/
vcs_web_file_base_url: http://github.com/resin-os/resin-via-arm/blob/%branch%/
summary: VIA ARM resinOS layer
description:
  This layer adds resinOS support on VIA ARM boards.

  Resin.io makes it simple to deploy, update, and maintain code running on remote devices. We are bringing the web development and deployment workflow to hardware. Using tools like git and docker to allow you to seamlessly update all your embedded linux devices in the wild. We handle cross-compilation, device monitoring, VPNs, and log collection, so you can focus on your product and not the infrastructure.

  https://resin.io


up_date: 2018-09-27 00:09:16
name: meta-exotic
vcs_url: https://github.com/peteasa/meta-exotic.git
vcs_web_url: http://github.com/peteasa/meta-exotic
vcs_web_tree_base_url: http://github.com/peteasa/meta-exotic/tree/%branch%/
vcs_web_file_base_url: http://github.com/peteasa/meta-exotic/blob/%branch%/
summary: Yocto layer to support cross compiler creation for exotic or foreign microcontrollers
description:
  The meta-exotic layer is a proof of concept layer to prove a generic method of creating the set of cross compiler tools needed to support a Microcontroller or other secondary processor in the Yocto environment.


up_date: 2018-09-27 00:09:16
name: meta-epiphany
vcs_url: https://github.com/peteasa/meta-epiphany.git
vcs_web_url: http://github.com/peteasa/meta-epiphany
vcs_web_tree_base_url: http://github.com/peteasa/meta-epiphany/tree/%branch%/
vcs_web_file_base_url: http://github.com/peteasa/meta-epiphany/blob/%branch%/
summary: Yocto layer to support the Epiphany processor
description:
  The meta-epiphany layer is a proof of concept layer to prove a generic method of creating the set of tools needed to support a Microcontroller or other secondary processor in the Yocto environment.

  This layer has been proven with the Parallella board http://www.parallella.org/ that has an Epiphany processor in addition to the classical ARM target running linux


up_date: 2018-09-27 00:09:16
name: meta-asteroid
vcs_url: https://github.com/AsteroidOS/meta-asteroid
vcs_web_url: http://github.com/AsteroidOS/meta-asteroid
vcs_web_tree_base_url: http://github.com/AsteroidOS/meta-asteroid/tree/%branch%/
vcs_web_file_base_url: http://github.com/AsteroidOS/meta-asteroid/blob/%branch%/
summary: Distro layer for AsteroidOS
description:
  AsteroidOS is a free and open-source operating system for smartwatches. This layer provides recipes for building an AsteroidOS image.


up_date: 2018-09-27 00:09:16
name: meta-snappy
vcs_url: https://github.com/morphis/meta-snappy.git
vcs_web_url: http://github.com/morphis/meta-snappy
vcs_web_tree_base_url: http://github.com/morphis/meta-snappy/tree/%branch%/
vcs_web_file_base_url: http://github.com/morphis/meta-snappy/blob/%branch%/
summary: Snap support layer
description:
  This meta layer adds support for Ubuntu Snappy for all OpenEmbedded/ Yocto based devices. For more details about what snaps are and what they provide have a look at http://snapcraft.io/


up_date: 2018-09-27 00:09:16
name: meta-img
vcs_url: https://github.com/MIPS/meta-img.git
vcs_web_url: http://github.com/MIPS/meta-img
vcs_web_tree_base_url: http://github.com/MIPS/meta-img/tree/%branch%/
vcs_web_file_base_url: http://github.com/MIPS/meta-img/blob/%branch%/
summary: BSP layer for providing MIPS based machine targets
description:
  A layer which adds BSPs for some MIPS based platforms and qemu machine targets.

  Check out the README.md file for more information


up_date: 2018-09-27 00:09:16
name: meta-zulu-java
vcs_url: https://github.com/zulu-openjdk/meta-zulu-java.git
vcs_web_url: http://github.com/zulu-openjdk/meta-zulu-java
vcs_web_tree_base_url: http://github.com/zulu-openjdk/meta-zulu-java/tree/%branch%/
vcs_web_file_base_url: http://github.com/zulu-openjdk/meta-zulu-java/blob/%branch%/
summary: Provides recipes for packaging Azul's Zulu Java releases
description:
  Zulu is a certified build of OpenJDK that is fully compliant with the Java SE standard. Zulu is 100% open source and freely downloadable.  There are packages to support both Intel and ARM v7 (with hard float support) processors.


up_date: 2018-09-27 00:09:16
name: meta-mibtec
vcs_url: https://github.com/rob-w/meta-mibtec
vcs_web_url: http://github.com/rob-w/meta-mibtec
vcs_web_tree_base_url: http://github.com/rob-w/meta-mibtec/tree/%branch%/
vcs_web_file_base_url: http://github.com/rob-w/meta-mibtec/blob/%branch%/
summary: Layer to support MIS/MIBTEC baseboards and modules
description:
  This Layer aims to bring support to all MIS/MIBTEC boards and modules, currently focused around am437x designs.


up_date: 2023-09-29 03:09:26
name: meta-lxde
vcs_url: git://git.toradex.com/meta-lxde.git
vcs_web_url: http://git.toradex.com/cgit/meta-lxde.git/
vcs_web_tree_base_url: http://git.toradex.com/cgit/meta-lxde.git/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.toradex.com/cgit/meta-lxde.git/tree/%path%?h=%branch%
summary: Software layer providing recipes for the LXDE desktop
description:
  This layer provides recipes and package groups which allow to build the Lightweight X11 Desktop Environment (LXDE).


up_date: 2023-11-13 09:11:01
name: meta-toradex-bsp-common
vcs_url: https://git.toradex.com/meta-toradex-bsp-common.git
vcs_web_url: https://git.toradex.com/cgit/meta-toradex-bsp-common.git/
vcs_web_tree_base_url: https://git.toradex.com/cgit/meta-toradex-bsp-common.git/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.toradex.com/cgit/meta-toradex-bsp-common.git/tree/%path%?h=%branch%
summary: BSP for Toradex Computer on Modules, SoC independent part
description:
  This layer provides support for ARM based Toradex computer on modules (COM) common to all used SoCs for use with OpenEmbedded and/or Yocto. It is to be used together with meta-toradex-nxp and/or meta-toradex-tegra layers.


up_date: 2023-11-13 09:11:50
name: meta-toradex-nxp
vcs_url: https://git.toradex.com/meta-toradex-nxp.git
vcs_web_url: https://git.toradex.com/cgit/meta-toradex-nxp.git/
vcs_web_tree_base_url: https://git.toradex.com/cgit/meta-toradex-nxp.git/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.toradex.com/cgit/meta-toradex-nxp.git/tree/%path%?h=%branch%
summary: BSP for Toradex Computer on Modules based on NXP SoCs
description:
  This layer provides support for ARM based Toradex computer on modules (COM) featuring NXP i.MX6, i.MX7, i.MX8, and Vybrid SoCs for use with OpenEmbedded and/or Yocto. The layer amends to the community BSP in meta-freescale and meta-freescale-3rdparty. It contains stuff which has not yet been upstreamed to the community BSP.


up_date: 2023-11-13 09:11:56
name: meta-toradex-tegra
vcs_url: https://git.toradex.com/meta-toradex-tegra.git
vcs_web_url: https://git.toradex.com/cgit/meta-toradex-tegra.git
vcs_web_tree_base_url: https://git.toradex.com/cgit/meta-toradex-tegra.git/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.toradex.com/cgit/meta-toradex-tegra.git/tree/%path%?h=%branch%
summary: BSP for Toradex Computer on Modules based on NVIDIA SoCs
description:
  This layer provides support for ARM based Toradex computer on modules (COM) featuring NVIDIA T20, T30, and TK1 SoCs for use with OpenEmbedded and/or Yocto.


up_date: 2023-11-13 09:11:08
name: meta-toradex-demos
vcs_url: https://git.toradex.com/meta-toradex-demos.git
vcs_web_url: https://git.toradex.com/cgit/meta-toradex-demos.git
vcs_web_tree_base_url: https://git.toradex.com/cgit/meta-toradex-demos.git/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.toradex.com/cgit/meta-toradex-demos.git/tree/%path%?h=%branch%
summary: Software layer providing recipes to build the Toradex demo images
description:
  This layer provides recipes used for demo images targeting ARM based Toradex System on Modules (SoM) featuring NXP i.MX and TI SoCs.


up_date: 2021-09-29 12:09:59
name: meta-arduino
vcs_url: https://gitlab.com/toganlabs/meta-arduino
vcs_web_url: http://gitlab.com/toganlabs/meta-arduino
vcs_web_tree_base_url: http://gitlab.com/toganlabs/meta-arduino/tree/%branch%/
vcs_web_file_base_url: http://gitlab.com/toganlabs/meta-arduino/blob/%branch%/
summary: Board Support for the Arduino Yún
description:
  This OpenEmbedded BSP layer supports the Arduino Yún board and is based on previous work from OpenWRT. Future support is planned for the Arduino Industrial 101 board and the Arduino Yún Shield.

  We are not associated with Arduino LLC in any way. This is solely a community supported alternative to the LininoOS OpenWRT based solution. Support requests and bug reports should go directly to the maintainers and not the nice folks at Arduino.


up_date: 2022-04-24 18:04:57
name: meta-bc
vcs_url: https://gitlab.linphone.org/BC/public/meta-bc.git
vcs_web_url: http://github.com/BelledonneCommunications/meta-bc
vcs_web_tree_base_url: http://github.com/BelledonneCommunications/meta-bc/tree/%branch%/
vcs_web_file_base_url: http://github.com/BelledonneCommunications/meta-bc/blob/%branch%/
summary: Linphone VoIP library support
description:
  This layer provides support for building liblinphone and associated packages necessary for running linphonec or linphone-daemon and making successful audio and video SIP  calls. 
  This is the official layer written by Belledonne Communications, responsible of Linphone.


up_date: 2022-07-26 07:07:07
name: meta-updater
vcs_url: https://github.com/uptane/meta-updater
vcs_web_url: https://github.com/uptane/meta-updater
vcs_web_tree_base_url: https://github.com/uptane/meta-updater/tree/%branch%/
vcs_web_file_base_url: https://github.com/uptane/meta-updater/blob/%branch%/
summary: OTA Software Updates using OSTree
description:
  OTA Software updates using OSTree. This generates images that are atomically updated and supports incremental downloading changes.

  Includes an update client to fetch updates and report status to an update server.


up_date: 2018-09-27 00:09:16
name: meta-rauc
vcs_url: https://github.com/rauc/meta-rauc.git
vcs_web_url: http://github.com/rauc/meta-rauc
vcs_web_tree_base_url: http://github.com/rauc/meta-rauc/tree/%branch%/
vcs_web_file_base_url: http://github.com/rauc/meta-rauc/blob/%branch%/
summary: RAUC update handler support
description:
  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 http://rauc.readthedocs.io.


up_date: 2022-04-10 18:04:27
name: meta-spdxscanner
vcs_url: https://git.yoctoproject.org/meta-spdxscanner
vcs_web_url: https://git.yoctoproject.org/meta-spdxscanner/
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-spdxscanner/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-spdxscanner/tree/%path%?h=%branch%
summary: spdx support
description:
  This meta generates an OSS SPDX (Software Package Data Exchange) file built by yocto.
  * https://spdx.org/
  This meta has the following features.
      - Supports multiple licensed scanners
        Multiple licensed scanners, including FOSSology and scancode-tk
      - High Performance
        Uses cache to reduce generation time
      - Ensure complete compliance with OSS
        Execute the do_spdx phase when building each OSS to create a complete SPDX file.


up_date: 2018-09-27 00:09:16
name: meta-mender-beaglebone
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: Mender over-the-air (OTA) updater beaglebone support
description:
  Beaglebone Black device support in the Mender OTA updater client. See the documentation for  how to use this layer: https://docs.mender.io/Artifacts/Building-Mender-Yocto-image.


up_date: 2018-09-27 00:09:16
name: meta-mender-demo
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: Mender over-the-air (OTA) updater demo configuration
description:
  Configuration for meta-mender-core convenient for testing and demoing, like default certificates and configuration settings. See the documentation for how to use this layer: https://docs.mender.io/Artifacts/Building-Mender-Yocto-image.

  Please do not use in production!


up_date: 2018-09-27 00:09:16
name: meta-mender-qemu
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: Mender over-the-air (OTA) updater QEMU support
description:
  Virtual QEMU device support using the machine `vexpress-qemu` in the Mender OTA updater client. See the documentation for how to use this layer: https://docs.mender.io/Artifacts/Building-Mender-Yocto-image.


up_date: 2018-09-27 00:09:16
name: meta-mender-raspberrypi
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: Mender over-the-air (OTA) updater raspberrypi support
description:
  Raspberry Pi support in the Mender OTA updater client. See the documentation for how to use this layer: https://docs.mender.io/Artifacts/Building-Mender-Yocto-image.


up_date: 2025-01-28 17:01:26
name: meta-gplv2
vcs_url: git://git.yoctoproject.org/meta-gplv2
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-gplv2
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-gplv2/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-gplv2/tree/%path%?h=%branch%
summary:
  Recipes corresponding to old, obsolete versions of software that are GPLv2 licensed where the upstream have moved to GPLv3 licenses.

description:
  This layer contains a set of recipes corresponding to old, obsolete versions of
  software that are GPLv2 licensed where the upstreams have moved to GPLv3 licenses.

  These were part of OE-Core until it was realised they are a ticking timebomb
  with regard to security updates and general maintenance. By splitting into a separate
  layer, it's hoped people realise these may not be the best solution to the 
  "no GPLv3 problem" and it should also make it clear there is a different quality of
  service applied to these recipes.

  For now, they do continue to get minimal testing by the Yocto Project but this will
  eventually be stopped, with anyone wanting to use them taking up the maintainership.


up_date: 2018-09-27 00:09:16
name: meta-azul-zulu-java
vcs_url: https://github.com/zulu-openjdk/meta-zulu-java.git
vcs_web_url: http://github.com/zulu-openjdk/meta-zulu-java
vcs_web_tree_base_url: http://github.com/zulu-openjdk/meta-zulu-java/tree/%branch%/
vcs_web_file_base_url: http://github.com/zulu-openjdk/meta-zulu-java/blob/%branch%/
summary: Azul Zulu Java JDK Releases
description:
  Zulu is a certified build of OpenJDK that is fully compliant with the Java SE standard. Zulu is 100% open source and freely downloadable. There are packages that support 32 and 64 bit Intel and 32 bit ARM v7 processors with soft floating point or hard floating point support.


up_date: 2022-04-10 18:04:44
name: meta-runit-init
vcs_url: https://github.com/cshoredaniel/meta-runit-init.git
vcs_web_url: http://github.com/cshoredaniel/meta-runit-init
vcs_web_tree_base_url: http://github.com/cshoredaniel/meta-runit-init/tree/%branch%/
vcs_web_file_base_url: http://github.com/cshoredaniel/meta-runit-init/blob/%branch%/
summary: Use busybox 'runit' commands as main init
description:
  An alternative to standard rc-scripts (e.g. busybox-init or sysvinit)
  or systemd (which is rather large), this layer allow the use of the
  busybox-equivalents of the 'runit' package as the main init system.
  (NB: runit itself is not in Yocto/OE, but busybox version and
  daemontools are).

  Was an interesting experiment, but after evaluating this approach vs. biting the bullet and accepting the size of systemd the original author has come to the conclusion that the effort required to make a runit approach comparable to systemd isn't worth it on modern embedded devices, and he wishes to focus his energy on other projects than dealing with hardware that will be deprecated and eliminated much sooner than easier to deal with hardware.


up_date: 2022-04-10 18:04:16
name: meta-earlyinit
vcs_url: https://github.com/cshoredaniel/meta-earlyinit.git
vcs_web_url: http://github.com/cshoredaniel/meta-earlyinit
vcs_web_tree_base_url: http://github.com/cshoredaniel/meta-earlyinit/tree/%branch%/
vcs_web_file_base_url: http://github.com/cshoredaniel/meta-earlyinit/blob/%branch%/
summary: Instead of initramfs, especially when using read-only-rootfs on small systems
description:
  This layer is intended to be used on systems where one doesn't wish to use space for an initramfs that isn't used in actual operation, but still need to do some setup before the main init system.

  It also incorporates handling for a combination or read-only-rootfs, volatile storage, and persistent storage for system where one wants to be able have configuration changes, but doesn't want excessive writes to fs (e.g. on flash storage), and/or persistent storage is at a premium.


up_date: 2022-04-10 18:04:45
name: meta-cshored
vcs_url: https://github.com/cshoredaniel/meta-cshored.git
vcs_web_url: http://github.com/cshoredaniel/meta-cshored
vcs_web_tree_base_url: http://github.com/cshoredaniel/meta-cshored/tree/%branch%/
vcs_web_file_base_url: http://github.com/cshoredaniel/meta-cshored/blob/%branch%/
summary: CShore Embedded Distribution - OE/Yocto-based routers and network appliances - pre-alpha
description:
  Early work on CShore Embedded Distribution (OE/Yocto + most likely OpenWrt/LEDE network stack and LuCI-based UI) which is intended primarily for quite small targets (e.g. 16MB flash/256 MB RAM is considered large) with read-only-rootfs but still having volatile and persistent storage intended for use as routers or network appliances.  At the moment it's been brought up on qemux86-64 to console-based mutli-user, and similarly on the Raspberry Pi.  Those targets are larger than the desired targets, but the snag with smaller targets is that their support mostly exists as OpenWrt/LEDE technical debt (i.e. not upstreamed) for things like ar71xx SoC, so currently emphasis is on the secondary goals of supporting router functionality with a factory reset (e.g. squashfs rootfs, with a default configuration that exists until you update the config on persistent storage).

  This project is deprecated as, except for earlyinit which may prove to remain useful, the original author has decided that using modern (albeit somewhat larger) technologies like systemd on modern hardware (since even for embedded devices the size isn't unacceptably large on new hardware) and avoiding spending time and effort on hardware that is irrelevant for most vendors and will be disappear by attrition sooner than the time to really get this approach to desired goal state.  It's simply easier to pick a battle that involves forward motion than backward looking efforts.


up_date: 2024-03-01 10:03:11
name: meta-ampliphy
vcs_url: git://git.phytec.de/meta-ampliphy
vcs_web_url: https://git.phytec.de/meta-ampliphy/
vcs_web_tree_base_url: https://git.phytec.de/meta-ampliphy/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.phytec.de/meta-ampliphy/tree/%path%?h=%branch%
summary: PHYTEC ampliPHY distribution
description:
  ampliPHY is PHYTEC's integration and verification distribution based on Poky. We build our development kits and hardware development images using this layer. We also stage some of our upstream and customer projects work here. You might find some useful stuff. The layer is formerly known as meta-yogurt and got renamed after dunfell.
  Notable supported features are:

  - hw verification tools for fully functional CI testing
  - systemd/networkd/pspslash/weston/wayland setup
  - secure boot and secure provisioning for production
  - rauc remote A/B system update client integration
  - partup board factory flashing
  - docker/podman/container runtime


up_date: 2018-09-27 00:09:16
name: meta-debian-extra
vcs_url: https://github.com/meta-debian/meta-debian-extra
vcs_web_url: http://github.com/meta-debian/meta-debian-extra
vcs_web_tree_base_url: http://github.com/meta-debian/meta-debian-extra/tree/%branch%/
vcs_web_file_base_url: http://github.com/meta-debian/meta-debian-extra/blob/%branch%/
summary: Build Debian packages whose versions are different from meta-debian.
description:
  meta-debian-extra has additional recipes to meta-debian. These recipes have upper version than recipes in meta-debian.

  For now, jethro branch in meta-debian has recipe for jessie(debian 8) package. On the other hand, jethro branch in meta-deiban-extra has recipes for jessie-backports/stretch pakcages.

  The branch name is one-to-one correspondence between meta-debian and meta-debian-extra.


up_date: 2018-09-27 00:09:16
name: meta-redhawk-sdr
vcs_url: http://github.com/geontech/meta-redhawk-sdr
vcs_web_url: http://github.com/geontech/meta-redhawk-sdr
vcs_web_tree_base_url: http://github.com/geontech/meta-redhawk-sdr/tree/%branch%/
vcs_web_file_base_url: http://github.com/geontech/meta-redhawk-sdr/blob/%branch%/
summary: REDHAWK SDR Dependencies
description:
  The layer contains the various dependencies and images for installing REDHAWK SDR onto a target platform.  The platform can run as a stand-alone or as a Node integrated with a Domain (default expectation).


up_date: 2018-09-27 00:09:16
name: meta-swupdate-boards
vcs_url: https://github.com/sbabic/meta-swupdate-boards
vcs_web_url: http://github.com/sbabic/meta-swupdate-boards
vcs_web_tree_base_url: http://github.com/sbabic/meta-swupdate-boards/tree/%branch%/
vcs_web_file_base_url: http://github.com/sbabic/meta-swupdate-boards/blob/%branch%/
summary: Layer with examples how to use SWUpdate
description:
  The layer contains some examples with "standard" boards (Beaglebone Black, etc.) to show how to integrate SWUpdate in own projects.


up_date: 2018-09-27 00:09:16
name: meta-synopsys
vcs_url: https://github.com/foss-for-synopsys-dwc-arc-processors/meta-synopsys
vcs_web_url: http://github.com/foss-for-synopsys-dwc-arc-processors/meta-synopsys
vcs_web_tree_base_url: http://github.com/foss-for-synopsys-dwc-arc-processors/meta-synopsys/tree/%branch%/
vcs_web_file_base_url: http://github.com/foss-for-synopsys-dwc-arc-processors/meta-synopsys/blob/%branch%/
summary: Synopsys ARC hardware support
description:
  Support for Synopsys Designware ARC cores. It contains machine's definitions for ARC700 and ARC HS38 cores and some boards like nSIM and AXS10x.


up_date: 2025-06-22 09:06:55
name: meta-barebox-legacy
vcs_url: https://github.com/menschel-d/meta-barebox.git
vcs_web_url: http://github.com/menschel-d/meta-barebox
vcs_web_tree_base_url: http://github.com/menschel-d/meta-barebox/tree/%branch%/
vcs_web_file_base_url: http://github.com/menschel-d/meta-barebox/blob/%branch%/
summary: Support for the barebox bootloader.
description:
  meta-barebox was a software layer for the Yocto Project and OpenEmbedded build system which provided support for the barebox bootloader.
  The layer was under active development from 2016 until 2024.
  The supported Yocto versions range from 2.3 (pyro) up to 5.1 (styhead).
  With the release of Yocto version 5.2 (walnascar), barebox is now officially supported by openembedded-core.

  That means meta-barebox has fulfilled its purpose and is now obsolete.
  This layer has been renamed from meta-barebox to meta-barebox-legacy in order to free up the original name in the OpenEmbedded layer index, in case anybody wants to start a new layer that is related to barebox.
  The layer's Git repository has not been renamed so legacy users won't be disrupted.


up_date: 2018-09-27 00:09:16
name: meta-iot-cloud
vcs_url: https://github.com/intel-iot-devkit/meta-iot-cloud.git
vcs_web_url: http://github.com/intel-iot-devkit/meta-iot-cloud
vcs_web_tree_base_url: http://github.com/intel-iot-devkit/meta-iot-cloud/tree/%branch%/
vcs_web_file_base_url: http://github.com/intel-iot-devkit/meta-iot-cloud/blob/%branch%/
summary: OpenEmbedded layer to add support for multiple cloud service provider solutions.
description:
  OpenEmbedded layer to add support for multiple cloud service provider solutions including IBM Bluemix, Microsoft Azure, Amazon Web Services (AWS) & Google Cloud Platform.


up_date: 2023-08-03 01:08:21
name: meta-efi-secure-boot
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: https://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Support UEFI Secure Boot and MOK Secure Boot
description:
  This layer consists of two widely used secure boot technologies: UEFI Secure
  Boot and MOK (Machine Owner Key) Secure Boot.


up_date: 2023-08-03 01:08:50
name: meta-encrypted-storage
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: http://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Provide secure storage for application data
description:
  This feature gives 2 types of granularity for storage encryption. Data volume encryption allows the user to create encryption partition with a passphrase typed by the end user. Root filesystem encryption enables the data encryption on the entire rootfs except the boot partition.


up_date: 2023-08-03 01:08:44
name: meta-integrity
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: https://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Provide Linux integrity support
description:
  The Linux IMA subsystem introduces hooks within the Linux kernel to support measuring the integrity of files that are loaded (including application code) before it is executed or mmap()ed to memory. The measured value (hash) is then registered in a log that can be consulted by administrators.


up_date: 2023-08-03 01:08:57
name: meta-signing-key
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: http://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Provide user and sample key store support
description:
  The sample keys, by default, are used by build system to sign bootloader, kernel, IMA signature, RPM and so on. It is used for development and demonstration. The user must know what te risk is to use the sample keys in the product. The user key in a general sense is able to be used in the product with contrary of the sample key. This document defines the definitions for the uses of various keys.


up_date: 2023-08-03 01:08:37
name: meta-tpm
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: http://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Provide TPM 1.x support
description:
  This feature enables tpm 1.2 support, including kernel option changes to enable tpm drivers, and picking up packages trousers, tpm-tools, openssl-tpm-engine, tpm-quote-tools and so on.


up_date: 2023-08-03 01:08:36
name: meta-tpm2
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: https://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Provide TPM 2.x support
description:
  This layer enables Trusted Platform Module (TPM 2.0) support, including kernel option changes to enable tpm drivers, and picking up TPM 2.0 packages.


up_date: 2023-08-03 01:08:59
name: meta-secure-core
vcs_url: https://github.com/Wind-River/meta-secure-core
vcs_web_url: https://github.com/Wind-River/meta-secure-core
vcs_web_tree_base_url: https://github.com/Wind-River/meta-secure-core/tree/%branch%/
vcs_web_file_base_url: https://github.com/Wind-River/meta-secure-core/blob/%branch%/
summary: Provide the use cases for the Linux applications on secure boot, integrity and encryption
description:
  This layer consists of  the following sub-layers: meta-efi-secure-boot, meta-integrity, meta-encrypted-storage, meta-signing-key, meta-tpm and meta-tpm2.


up_date: 2022-04-10 18:04:57
name: meta-nexell
vcs_url: http://git.nexell.co.kr:8080/nexell/yocto/krogoth/meta-nexell
summary: Yocto BSP layer for Nexell s5pxx18 boards
vcs_web_url:
  http://git.nexell.co.kr:8080/gitweb?p=nexell/yocto/krogoth/meta-nexell.git;a=shortlog;h=refs/heads/pyro

vcs_web_tree_base_url:
  http://git.nexell.co.kr:8081/gerrit/gitweb?p=nexell/yocto/meta-nexell.git;f=meta-nexell-distro/README.md;h=490469e651183d3b524c2e3539d330f77e14827b;hb=refs/heads/pyro;a=tree;f=%path%;hb=refs/heads/%branch%

vcs_web_file_base_url:
  http://git.nexell.co.kr:8081/gerrit/gitweb?p=nexell/yocto/meta-nexell.git;f=meta-nexell-distro/README.md;h=490469e651183d3b524c2e3539d330f77e14827b;hb=refs/heads/pyro;a=blob;f=%path%;hb=refs/heads/%branch%

description:
  Yocto BSP meta layer for Nexell based devices.

  s5p4418, s5p6818 boards and variation products.

  Support image types are qt5, tiny, sato and ubuntu

  homepage : http://www.nexell.co.kr/


up_date: 2019-09-30 22:09:53
name: meta-jupyter
vcs_url: https://github.com/Xilinx/meta-jupyter
vcs_web_url: http://github.com/Xilinx/meta-jupyter
vcs_web_tree_base_url: http://github.com/Xilinx/meta-jupyter/tree/%branch%/
vcs_web_file_base_url: http://github.com/Xilinx/meta-jupyter/blob/%branch%/
summary: Jupyter notebooks support layer
description:
  This layer provides recipes to build jupyter notebook and its requirements on openembedded-based systems


up_date: 2023-01-09 10:01:06
name: meta-meson
vcs_url: https://github.com/superna9999/meta-meson
vcs_web_url: http://github.com/superna9999/meta-meson
vcs_web_tree_base_url: http://github.com/superna9999/meta-meson/tree/%branch%/
vcs_web_file_base_url: http://github.com/superna9999/meta-meson/blob/%branch%/
summary: Upstream Linux Amlogic Meson Yocto/OpenEmbedded Layer
description:
  Upstream Linux Amlogic Meson Yocto/Openembedded Layer

  Amlogic SoCs have now Mainline Linux support, this layer helps building images for these platforms.


up_date: 2019-06-10 19:06:24
name: meta-timesys
vcs_url: https://github.com/TimesysGit/meta-timesys.git
vcs_web_url: http://github.com/TimesysGit/meta-timesys
vcs_web_tree_base_url: http://github.com/TimesysGit/meta-timesys/tree/%branch%/
vcs_web_file_base_url: http://github.com/TimesysGit/meta-timesys/blob/%branch%/
summary: Timesys layer for Vigiles Yocto CVE monitoring
description:
  Timesys layer for Vigiles Yocto CVE monitoring, security notifications, and image manifest generation. 

  About Vigiles:  https://www.timesys.com/security/vigiles/
  For meta-timesys and Vigiles questions:  vigiles@timesys.com


up_date: 2018-09-27 00:09:16
name: meta-intel-realsense
vcs_url: https://github.com/IntelRealSense/meta-intel-realsense
vcs_web_url: http://github.com/IntelRealSense/meta-intel-realsense
vcs_web_tree_base_url: http://github.com/IntelRealSense/meta-intel-realsense/tree/%branch%/
vcs_web_file_base_url: http://github.com/IntelRealSense/meta-intel-realsense/blob/%branch%/
summary: Support for Intel® RealSense™ cameras
description:
  This layer adds the packages necessary for adding support for Intel® RealSense™ cameras via librealsense to your Yocto distribution.


up_date: 2022-04-10 18:04:02
name: meta-refkit-core
vcs_url: https://github.com/intel/intel-iot-refkit
vcs_web_url: http://github.com/intel/intel-iot-refkit
vcs_web_tree_base_url: http://github.com/intel/intel-iot-refkit/tree/%branch%/
vcs_web_file_base_url: http://github.com/intel/intel-iot-refkit/blob/%branch%/
summary: Core layer for the IoT Reference OS Kit for Intel(r) Architecture
description:
  Core layer for the IoT Reference OS Kit for Intel(r) Architecture, containing common utility classes and miscellaneous recipes which are not profile-specific.


up_date: 2022-04-10 18:04:53
name: meta-refkit-extra
vcs_url: https://github.com/intel/intel-iot-refkit
vcs_web_url: http://github.com/intel/intel-iot-refkit
vcs_web_tree_base_url: http://github.com/intel/intel-iot-refkit/tree/%branch%/
vcs_web_file_base_url: http://github.com/intel/intel-iot-refkit/blob/%branch%/
summary: IoT Reference OS Kit for Intel(r) Architecture demo layer
description:
  A layer for demos and other things which are built on top of
  IoT Reference OS Kit for Intel(r) Architecture.


up_date: 2022-04-10 18:04:41
name: meta-refkit-computervision
vcs_url: https://github.com/intel/intel-iot-refkit
vcs_web_url: http://github.com/intel/intel-iot-refkit
vcs_web_tree_base_url: http://github.com/intel/intel-iot-refkit/tree/%branch%/
vcs_web_file_base_url: http://github.com/intel/intel-iot-refkit/blob/%branch%/
summary: IoT Reference OS Kit for Intel(r) Architecture profile for computer vision use cases
description:
  A profile for the IoT Reference OS Kit for Intel(r) Architecture with tools and configuration for computer vision use cases.


up_date: 2022-04-10 18:04:33
name: meta-refkit-industrial
vcs_url: https://github.com/intel/intel-iot-refkit
vcs_web_url: http://github.com/intel/intel-iot-refkit
vcs_web_tree_base_url: http://github.com/intel/intel-iot-refkit/tree/%branch%/
vcs_web_file_base_url: http://github.com/intel/intel-iot-refkit/blob/%branch%/
summary: IoT Reference OS Kit for Intel(r) Architecture profile for industrial use cases
description:
  A profile for the IoT Reference OS Kit for Intel(r) Architecture with tools for industrial use cases, i.e. ROS Industrial packages intended to be used in industrial robotics applications.


up_date: 2023-09-29 01:09:24
name: meta-mender-toradex-nxp
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: Mender over-the-air (OTA) updater toradex-nsp support
description:
  Community support for Toradex NXP devices in the Mender OTA updater client. See the documentation for how to use this layer: https://docs.mender.io/Artifacts/Building-Mender-Yocto-image.


up_date: 2018-09-27 00:09:16
name: meta-intel-clear-containers
vcs_url: git://git.yoctoproject.org/meta-intel-clear-containers
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-clear-containers
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-clear-containers/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-clear-containers/tree/%path%?h=%branch%
summary: Layer enabling Intel® Clear Containers
description:
  Intel® Clear Containers is a collection of tools, configurations, and techniques anchored on an implementation that leverages Intel® Architecture to optimize container launching and execution workflow. These optimizations improve speed, size, and efficiency while offering a number of benefits that can be derived only from hardware-backed virtual machines (hardware-enforced isolation and security, for example) on Intel® VT technology.


up_date: 2018-10-01 02:10:54
name: meta-fnordpipe
vcs_url: https://gitlab.com/fnordpipe/operatingsystems/meta-fnordpipe.git
vcs_web_url: http://gitlab.com/fnordpipe/operatingsystems/meta-fnordpipe
vcs_web_tree_base_url: http://gitlab.com/fnordpipe/operatingsystems/meta-fnordpipe/tree/%branch%/
vcs_web_file_base_url: http://gitlab.com/fnordpipe/operatingsystems/meta-fnordpipe/blob/%branch%/
summary: layer for xen and lxc host images
description:
  this layer provides images for xen and lxc hosts.
  It aims to ship as read-only rootfs and a very small footprint.


up_date: 2018-09-27 00:09:16
name: meta-hdl
vcs_url: https://github.com/nathanrossi/meta-hdl
vcs_web_url: http://github.com/nathanrossi/meta-hdl
vcs_web_tree_base_url: http://github.com/nathanrossi/meta-hdl/tree/%branch%/
vcs_web_file_base_url: http://github.com/nathanrossi/meta-hdl/blob/%branch%/
summary: HDL tools layer for OpenEmbedded
description:
  This layer contains recipes for Hardware Description Languages (HDL) tools, which includes tools for simulation, synthesis, etc.


up_date: 2018-09-27 00:09:16
name: meta-lora-net
vcs_url: https://github.com/sigysmund/meta-lora-net.git
vcs_web_url: http://github.com/sigysmund/meta-lora-net
vcs_web_tree_base_url: http://github.com/sigysmund/meta-lora-net/tree/%branch%/
vcs_web_file_base_url: http://github.com/sigysmund/meta-lora-net/blob/%branch%/
summary: Adds support for lora_gateway and package_forwarder tools from Lora-net
description:
  Some of the today's IoT gateways will be employing LoRa radio, and for such projects this is first need to use SX1301 chip with some GPS. lora_gateway library is actually a driver for SX1301 using SPI interface, no kernel module is needed, only usual SPI device from BSP should be active and a connected concentrator board. package_forwarder is a software which uplinks/downlinks RF messages though UDP connections. 

  This layer was tested on raspberry pi3 with iC880A-SPI concentrator from iMST.

  More information about built software is found on: https://github.com/lora-net


up_date: 2023-09-29 02:09:16
name: meta-xperia
vcs_url: https://github.com/esno/meta-xperia.git
vcs_web_url: http://github.com/esno/meta-xperia
vcs_web_tree_base_url: http://github.com/esno/meta-xperia/tree/%branch%/
vcs_web_file_base_url: http://github.com/esno/meta-xperia/blob/%branch%/
summary: Layer for Sony open devices e.g. xperia xz1 compact
description:
  This layer provides BSPs for open xperia devices like the xperia xz1 compact (yoshino platform).

  Moved to GitLab but no longer maintained? https://gitlab.com/tricorder/meta-xperia


up_date: 2018-09-27 00:09:16
name: meta-ptx
vcs_url: https://github.com/pengutronix/meta-ptx.git
vcs_web_url: http://github.com/pengutronix/meta-ptx
vcs_web_tree_base_url: http://github.com/pengutronix/meta-ptx/tree/%branch%/
vcs_web_file_base_url: http://github.com/pengutronix/meta-ptx/blob/%branch%/
summary: Yocto layer for Pengutronix-related tools and distro
description:
  This layer contains for example a recipe for the 'barebox' bootloader, a class for creating bootspec-based rootfs images and full support for the 'genimage' image creation tool.


up_date: 2018-09-27 00:09:16
name: meta-anaconda
vcs_url: git://git.yoctoproject.org/meta-anaconda
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-anaconda
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-anaconda/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-anaconda/tree/%path%?h=%branch%
summary: This layer provides an installation program `anaconda' for yocto project
description:
  This layer provides an installation program based on
  OE platform. The installation program is anaconda from
  fedora, which is the installer of distribution Fedora,
  RedHat and Centos.

  The version of anaconda in meta-installer is 26.21.11
  which is based on Fedora 26.


up_date: 2018-09-27 00:09:16
name: meta-qemuarma9
vcs_url: https://github.com/OverC/meta-qemuarma9
vcs_web_url: http://github.com/OverC/meta-qemuarma9
vcs_web_tree_base_url: http://github.com/OverC/meta-qemuarma9/tree/%branch%/
vcs_web_file_base_url: http://github.com/OverC/meta-qemuarma9/blob/%branch%/
summary: qemuarma9 support (using linux-yocto)
description:
  core/base support for qemuarma9 leveraging linux-yocto and oe-core's runqemu support to provide a functional a9 platform for userspace testing.


up_date: 2022-04-10 18:04:11
name: meta-ecs-unofficial-liva-bsp
vcs_url: https://github.com/cshoredaniel/meta-ecs-unofficial-liva-bsp.git
vcs_web_url: http://github.com/cshoredaniel/meta-ecs-unofficial-liva-bsp
vcs_web_tree_base_url: http://github.com/cshoredaniel/meta-ecs-unofficial-liva-bsp/tree/%branch%/
vcs_web_file_base_url: http://github.com/cshoredaniel/meta-ecs-unofficial-liva-bsp/blob/%branch%/
summary:
  Yocto/OpenEmbedded Board Support Package for the original Elite Computer Systems Liva NUC-based PC (Unofficial)

description:
  Very loosely based on Raspberry Pi meta layer but mostly just defines the the config to build the wifi kernel module for the mini-PCIe wireless that comes with this model.


up_date: 2018-09-27 00:09:16
name: meta-udoo
vcs_url: https://github.com/graugans/meta-udoo
vcs_web_url: http://github.com/graugans/meta-udoo
vcs_web_tree_base_url: http://github.com/graugans/meta-udoo/tree/%branch%/
vcs_web_file_base_url: http://github.com/graugans/meta-udoo/blob/%branch%/
summary: UDOO i.mx6 family based platform support
description:
  This layer provides support for UDOO i.mx6 family based platforms for use with OpenEmbedded and/or Yocto Freescale's BSP layers.


up_date: 2018-09-27 00:09:16
name: meta-device-cloud
vcs_url: https://github.com/Wind-River/meta-device-cloud
vcs_web_url: http://github.com/Wind-River/meta-device-cloud
vcs_web_tree_base_url: http://github.com/Wind-River/meta-device-cloud/tree/%branch%/
vcs_web_file_base_url: http://github.com/Wind-River/meta-device-cloud/blob/%branch%/
summary: Meta data for the device cloud SDK
description:
  Device Cloud (DC) is a cloud/device platform that accelerates
  device to cloud and cloud to cloud interaction.  This meta layer integrates
  a Python implementation that is designed to be run on the device side and can be
  used for device actuation, management, sending telemetry, remote
  console etc.

  The Python agent for DC is designed for quick deployment on any
  platform that supports Python.  The continuous deployment model uses
  "pip" to install and update the latest modules.  Any application that
  wants to use DC cloud services can import the "device_cloud" module and
  begin using the DC APIs.


up_date: 2018-09-27 00:09:16
name: meta-license-tools
vcs_url: https://gitlab.com/toganlabs/meta-license-tools.git
vcs_web_url: https://gitlab.com/toganlabs/meta-license-tools
vcs_web_tree_base_url: https://gitlab.com/toganlabs/meta-license-tools/tree/%branch%/%path%
vcs_web_file_base_url: https://gitlab.com/toganlabs/meta-license-tools/blob/%branch%/%path%
summary: A Layer that contains classes to interact with 3rd party license tools.
description:
  This layer currently contains a single bbclass to upload source archives to a Fossology server for analysis. Eventually, additional license tools will be added to this layer.


up_date: 2018-09-27 00:09:16
name: meta-cryptocurrency
vcs_url: https://github.com/wouterlucas/meta-cryptocurrency.git
vcs_web_url: http://github.com/wouterlucas/meta-cryptocurrency
vcs_web_tree_base_url: http://github.com/wouterlucas/meta-cryptocurrency/tree/%branch%/
vcs_web_file_base_url: http://github.com/wouterlucas/meta-cryptocurrency/blob/%branch%/
summary: Build an image to control cryptocurrency miners and wallets such as Bitcoin, Ethereum, etc
description:
  This is a Yocto/OpenEmbedded meta-layer for cryptocurrency related packages. Such as cgminer, cpuminer and more! This creates an all in one crypto Yocto distro for any device.


up_date: 2018-09-27 00:09:16
name: meta-lorawan-rak831
vcs_url: https://github.com/bear-metal/meta-lorawan-rak831.git
vcs_web_url: http://github.com/bear-metal/meta-lorawan-rak831
vcs_web_tree_base_url: http://github.com/bear-metal/meta-lorawan-rak831/tree/%branch%/
vcs_web_file_base_url: http://github.com/bear-metal/meta-lorawan-rak831/blob/%branch%/
summary: image for the RAK831 LoRaWan gateway
description:
  iImage for the RAK831 LoRaWan gateway.
  * read-only rootfs
  * ssh public key authenticated login
  * mender.io compatible
  * zeroconf discoverable


up_date: 2018-09-27 00:09:16
name: meta-ossystems-base
vcs_url: https://code.ossystems.com.br/meta-ossystems-base.git
vcs_web_url: https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git
summary: O.S. Systems Embedded Linux base OpenEmbedded/Yocto BSP layer
vcs_web_tree_base_url:
  https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git;a=tree;f=%path%;hb=refs/heads/%branch%

vcs_web_file_base_url:
  https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git;a=blob;f=%path%;hb=refs/heads/%branch%

description:
  This layer provides the base for the O.S. Systems Embedded Linux.  It
  provides the "oel" distribution and a set of helpers used for multiple
  products being developed with OpenEmbedded and/or Yocto Project.


up_date: 2025-04-01 10:04:47
name: meta-webosose
vcs_url: https://www.github.com/webosose/meta-webosose
vcs_web_url: https://github.com/webosose/meta-webosose
vcs_web_tree_base_url: https://github.com/webosose/meta-webosose/tree/%branch%/
vcs_web_file_base_url: https://github.com/webosose/meta-webosose/blob/%branch%/
summary: webOS OSE (Open Source Edition) distribution (official)
description:
  webOS Open Source Edition (OSE) offers a strong development environment that enables easy collaboration with other platform developers, as well as distinctive built-in user features.


up_date: 2024-08-19 00:08:00
name: meta-l1calo
vcs_url: https://github.com/kratsg/meta-l1calo/
vcs_web_url: http://github.com/kratsg/meta-l1calo
vcs_web_tree_base_url: http://github.com/kratsg/meta-l1calo/tree/%branch%/
vcs_web_file_base_url: http://github.com/kratsg/meta-l1calo/blob/%branch%/
summary: Layer for Level-1 Calorimeter Hardware in ATLAS at CERN
description:
  While this layer contains some BSPs specific to non-public hardware being used, there are still other recipes that are useful for the FOSS community.


up_date: 2018-09-27 00:09:16
name: meta-bistro
vcs_url: https://github.com/Pelagicore/meta-bistro.git
vcs_web_url: http://github.com/Pelagicore/meta-bistro
vcs_web_tree_base_url: http://github.com/Pelagicore/meta-bistro/tree/%branch%/
vcs_web_file_base_url: http://github.com/Pelagicore/meta-bistro/blob/%branch%/
summary: Yocto layer providing In-Vehicle Infotainment related functionality and adaptations
description:
  A Yocto/OpenEmbedded layer that provides in-vehicle infotainment (IVI) 
  related functionality in an OpenEmbedded Linux system.

  This layer aggregates original IVI related software recipes for software
  components developed by Pelagicore. In addition, the layer contains
  appendments to other open source Yocto/OpenEmbedded layer recipes
  that are relevant for the aforementioned functionality


up_date: 2018-09-27 00:09:16
name: meta-pelux
vcs_url: https://github.com/pelagicore/meta-pelux
vcs_web_url: http://github.com/pelagicore/meta-pelux
vcs_web_tree_base_url: http://github.com/pelagicore/meta-pelux/tree/%branch%/
vcs_web_file_base_url: http://github.com/pelagicore/meta-pelux/blob/%branch%/
summary:
  PELUX is an open source, GENIVI compliant development platform that supports the Qt Automotive Suite

description:
  A Yocto/OpenEmbedded layer providing PELUX images. PELUX is a Linux based platform used for developing automotive infotainment projects.

  The layer provides the PELUX distro that is derived from poky. Furthermore, this layer provides core-image-pelux recipes, along with necessary additions to software components to enable a functional In-Vehicle Infotainment (IVI) base image. The software component additions and appendments found in this layer are specific for the PELUX image but can be used outside of this context.


up_date: 2018-09-27 00:09:16
name: meta-lts-kernel
vcs_url: https://github.com/iwamatsu/meta-lts-kernel.git
vcs_web_url: http://github.com/iwamatsu/meta-lts-kernel
vcs_web_tree_base_url: http://github.com/iwamatsu/meta-lts-kernel/tree/%branch%/
vcs_web_file_base_url: http://github.com/iwamatsu/meta-lts-kernel/blob/%branch%/
summary: This provides a recipe using the LTS kernel
description:
  This provides a recipe using the LTS kernel.
  The following kernels are available:

   - v4.1.y
   - v4.4.y
   - v4.9.y
   - v4.14.y


up_date: 2024-02-05 20:02:08
name: meta-updatehub
vcs_url: https://github.com/UpdateHub/meta-updatehub
vcs_web_url: http://github.com/UpdateHub/meta-updatehub
vcs_web_tree_base_url: http://github.com/UpdateHub/meta-updatehub/tree/%branch%/
vcs_web_file_base_url: http://github.com/UpdateHub/meta-updatehub/blob/%branch%/
summary: OpenEmbedded/Yocto Project support layer for UpdateHub
description:
  updatehub provides a generic and safe Firmware Over-The-Air agent for
  Embedded and Industrial Linux-based devices.


up_date: 2018-09-27 00:09:16
name: meta-updatehub-freescale
vcs_url: https://github.com/UpdateHub/meta-updatehub-freescale
vcs_web_url: http://github.com/UpdateHub/meta-updatehub-freescale
vcs_web_tree_base_url: http://github.com/UpdateHub/meta-updatehub-freescale/tree/%branch%/
vcs_web_file_base_url: http://github.com/UpdateHub/meta-updatehub-freescale/blob/%branch%/
summary: Freescale OpenEmbedded/Yocto Project BSP support layer for UpdateHub
description:
  UpdateHub provides a generic and safe Firmware Over-The-Air agent for
  Embedded and Industrial Linux-based devices.


up_date: 2018-09-27 00:09:16
name: meta-docker
vcs_url: https://github.com/L4B-Software/meta-docker
vcs_web_url: http://github.com/L4B-Software/meta-docker
vcs_web_tree_base_url: http://github.com/L4B-Software/meta-docker/tree/%branch%/
vcs_web_file_base_url: http://github.com/L4B-Software/meta-docker/blob/%branch%/
summary: meta-docker allows to build docker images in yocto
description:
  A yocto-layer adding an imagetype which enables the user to create docker container images from yocto.


up_date: 2022-04-10 18:04:18
name: meta-xvisor
vcs_url: https://github.com/cshoredaniel/meta-xvisor.git
vcs_web_url: http://github.com/cshoredaniel/meta-xvisor
vcs_web_tree_base_url: http://github.com/cshoredaniel/meta-xvisor/tree/%branch%/
vcs_web_file_base_url: http://github.com/cshoredaniel/meta-xvisor/blob/%branch%/
summary: Build images with XVisor monolithic Type-1 Hypervisor
description:
  XVisor (eXtensible Versatile hyperVISOR) from https://xhypervisor.org is a monolithic Type-1 (bare-metal) hypervisor for x86-64 and arm (so far; more ports should be possible). This layer builds and OE cross-compilation toolchain (eSDk is planned) to allow building XVisor and HD images with XVisor, as well as for testing in QEMU.


up_date: 2018-09-27 00:09:16
name: meta-xenomai
vcs_url: https://bitbucket.org/pficheux/meta-xenomai
vcs_web_url: http://bitbucket.org/pficheux/meta-xenomai
vcs_web_tree_base_url: http://bitbucket.org/pficheux/meta-xenomai/src/%branch%/%path%?at=%branch%
vcs_web_file_base_url: http://bitbucket.org/pficheux/meta-xenomai/src/%branch%/%path%?at=%branch%
summary: Support for Xenomai framework
description:
  Current version supports Raspberry Pi 3 ("raspberrypi3" target from meta-raspberrypi) tested
  on Morty (2.2), Pyro (2.3), Rocko (2.4).


up_date: 2018-09-27 00:09:16
name: meta-ostree
vcs_url: https://github.com/sidebranch/meta-ostree.git
vcs_web_url: http://github.com/sidebranch/meta-ostree
vcs_web_tree_base_url: http://github.com/sidebranch/meta-ostree/tree/%branch%/
vcs_web_file_base_url: http://github.com/sidebranch/meta-ostree/blob/%branch%/
summary: OSTree support
description:
  BitBake meta data layer for Yocto / OpenEmbedded Core, adding update functionality using libostree (OSTree). OSTree features a update mechanism based on GIT concepts. Only changed files can be upgraded on devices in the field, optionally using delta differences. This minimizes data usage, saving cost on metered or otherwise costly connections, such as over-the-air firmware updates.


up_date: 2018-11-14 04:11:15
name: meta-intel-edison-distro
vcs_url: https://github.com/edison-fw/meta-intel-edison.git
vcs_web_url: http://github.com/edison-fw/meta-intel-edison
vcs_web_tree_base_url: http://github.com/edison-fw/meta-intel-edison/tree/%branch%/
vcs_web_file_base_url: http://github.com/edison-fw/meta-intel-edison/blob/%branch%/
summary: Unofficial continuation of the distribution layer for Intel Edison-Arduino
description:
  This layer tries to provide similar or better functionality as the factory supplied version, but with up-to-date versions of U-Boot, Linux kernel and Poky.


up_date: 2018-10-24 20:10:27
name: meta-mortsgna
vcs_url: https://github.com/schnitzeltony/meta-mortsgna.git
vcs_web_url: http://github.com/schnitzeltony/meta-mortsgna
vcs_web_tree_base_url: http://github.com/schnitzeltony/meta-mortsgna/tree/%branch%/
vcs_web_file_base_url: http://github.com/schnitzeltony/meta-mortsgna/blob/%branch%/
summary: Distribution with useful defaults, pre-configured images and daily helpers
description:
  This distribution is based on Ångström. Target is to build images with same experience as expected from a desktop distribution.

  * align console defaults (shortcuts/color)
  * pre-configured images for console/KDE/LXQT/KDE
  * replace some busybox tools which are missing important functions
  * ship an unprivileged user that inherits defaults

  This layer also supports users at frequent tasks:
  * Easy to extend script-framework to write images to sdcard.
  * Class to enable instant remote debugging

  Check README for more details


up_date: 2018-11-11 21:11:24
name: meta-chip-legacy
vcs_url: https://github.com/myfreescalewebpage/meta-chip
vcs_web_url: http://github.com/myfreescalewebpage/meta-chip
vcs_web_tree_base_url: http://github.com/myfreescalewebpage/meta-chip/tree/%branch%/
vcs_web_file_base_url: http://github.com/myfreescalewebpage/meta-chip/blob/%branch%/
summary: NextThingCo C.H.I.P. Yocto meta layer
description:
  C.H.I.P. and C.H.I.P. PRO are two boards created by NextThingCo. This layer add support to both boards with kernel, u-boot and the wifi drivers.

  This layer has been updated with new repositories following the end of NextThingCo ans is currently the only one which is up to date to build the images for both boards.

  Some examples are also available on the github of the same author.


up_date: 2025-02-26 19:02:15
name: meta-acme
vcs_url: https://github.com/myfreescalewebpage/meta-acme
vcs_web_url: http://github.com/myfreescalewebpage/meta-acme
vcs_web_tree_base_url: http://github.com/myfreescalewebpage/meta-acme/tree/%branch%/
vcs_web_file_base_url: http://github.com/myfreescalewebpage/meta-acme/blob/%branch%/
summary: Acme Systems Yocto meta layer
description:
  This layer add support to Acme Systems boards (https://www.acmesystems.it/).

  Some examples are also available on the github of the same author.


up_date: 2018-11-29 21:11:41
name: meta-yoe
vcs_url: https://github.com/YoeDistro/meta-yoe
vcs_web_url: http://github.com/YoeDistro/meta-yoe
vcs_web_tree_base_url: http://github.com/YoeDistro/meta-yoe/tree/%branch%/
vcs_web_file_base_url: http://github.com/YoeDistro/meta-yoe/blob/%branch%/
summary: Yoe Embedded Linux Distribution layer
description:
  Yoe is an Embedded Linux Distribution optimized for product development. It is built on Yocto and OpenEmbedded with a focus on simplicity. This distribution does not end at demo images but rather begins there.


up_date: 2018-11-29 21:11:54
name: meta-riscv
vcs_url: https://github.com/riscv/meta-riscv
vcs_web_url: http://github.com/riscv/meta-riscv
vcs_web_tree_base_url: http://github.com/riscv/meta-riscv/tree/%branch%/
vcs_web_file_base_url: http://github.com/riscv/meta-riscv/blob/%branch%/
summary: RISC-V Architecture Layer for OpenEmbedded/Yocto
description:
  This is the general hardware specific BSP overlay for the RISC-V based devices.

  More information can be found at: https://riscv.org/ (Official Site)


up_date: 2018-12-06 23:12:36
name: meta-allwinner-hx
vcs_url: https://gitlab.com/dimtass/meta-allwinner-hx
vcs_web_url: http://gitlab.com/dimtass/meta-allwinner-hx
vcs_web_tree_base_url: http://gitlab.com/dimtass/meta-allwinner-hx/tree/%branch%/
vcs_web_file_base_url: http://gitlab.com/dimtass/meta-allwinner-hx/blob/%branch%/
summary: Meta layer for all allwinner H2/H3/H5 boards
description:
  This meta layer is mainly a mix of meta-sunxi and armbian.
  This meta layer supports only boards with the allwinner H2, H3 and H5 cpus.
  The boards that are supported are the same ones that supported in
  armbian. The current supported list is
  the following ones:

  nanopi-duo
  nanopi-k1-plus
  nanopi-m1
  nanopi-m1-plus
  nanopi-neo
  nanopi-neo2
  nanopi-neo-air
  nanopi-neo-core2
  nanopi-neo-plus2
  orange-pi-one
  orange-pi-pc
  orange-pi-pc-plus
  orange-pi-prime
  orange-pi-win
  orange-pi-zero
  orange-pi-zero-plus
  orange-pi-zero-plus2


up_date: 2019-01-30 01:01:51
name: meta-neural-network
vcs_url: https://github.com/nnsuite/meta-nerual-network
vcs_web_url: http://github.com/nnsuite/meta-nerual-network
vcs_web_tree_base_url: http://github.com/nnsuite/meta-nerual-network/tree/%branch%/
vcs_web_file_base_url: http://github.com/nnsuite/meta-nerual-network/blob/%branch%/
summary: Software Pacakges for Neural Networks
description:
  Neural Network Streaming Tool for On-Device AI, "NNStreamer", and its utilities (including Tensorflow, Tensorflow-Lite).

  Caffe2, PyTorch, and others will be added later.


up_date: 2019-01-30 20:01:54
name: meta-microservicebus-node
vcs_url: https://github.com/axians/meta-microservicebus.git
vcs_web_url: http://github.com/axians/meta-microservicebus
vcs_web_tree_base_url: http://github.com/axians/meta-microservicebus/tree/%branch%/
vcs_web_file_base_url: http://github.com/axians/meta-microservicebus/blob/%branch%/
summary: Yocto layer for microServiceBus-node, a device agent used for microServiceBus.com
description:
  microServiceBus.com is an integration platform for IoT and enterprise applications.
  This platform lets you expose microservices from small devices and large systems using a remote hosting infrastructure.
  These nodes can run on both Linux and Windows using components built either natively (ARM) or using node.js.


up_date: 2019-03-01 10:03:38
name: meta-sca
vcs_url: https://github.com/priv-kweihmann/meta-sca.git
vcs_web_url: http://github.com/priv-kweihmann/meta-sca
vcs_web_tree_base_url: http://github.com/priv-kweihmann/meta-sca/tree/%branch%/
vcs_web_file_base_url: http://github.com/priv-kweihmann/meta-sca/blob/%branch%/
summary: Static code analysis layer
description:
  A layer providing static code analysis tools for at least C,C++,Python & shell.
  Easy to setup on large projects.

  Results are stored in checkstyle-format, which could be easily used in e.g. Jenkins.


up_date: 2019-02-08 02:02:41
name: meta-rte
vcs_url: https://github.com/3mdeb/meta-rte
vcs_web_url: http://github.com/3mdeb/meta-rte
vcs_web_tree_base_url: http://github.com/3mdeb/meta-rte/tree/%branch%/
vcs_web_file_base_url: http://github.com/3mdeb/meta-rte/blob/%branch%/
summary: Yocto meta layer for the open hardware RTE https://3mdeb.com/rte/ board
description:
  Remote testing environment is a hat designed for Orange Pi Zero board which runs specially crafted Linux distribution using the Yocto Project.


up_date: 2019-02-19 19:02:11
name: meta-buildutils
vcs_url: https://github.com/priv-kweihmann/meta-buildutils.git
vcs_web_url: http://github.com/priv-kweihmann/meta-buildutils
vcs_web_tree_base_url: http://github.com/priv-kweihmann/meta-buildutils/tree/%branch%/
vcs_web_file_base_url: http://github.com/priv-kweihmann/meta-buildutils/blob/%branch%/
summary: A collection of build utils
description:
  Collection of supporting classes targeting things like 
  - flexible inherit
  - safer configuration for KBuild-systems
  - python speed enhancements
  - python packaging helper

  The layer itself will not add any new/changed software, it's just some tool to be used for more convenient building


up_date: 2024-02-05 23:02:02
name: meta-tensorflow
vcs_url: git://git.yoctoproject.org/meta-tensorflow
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-tensorflow
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-tensorflow/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-tensorflow/tree/%path%?h=%branch%
summary: This layer integrates TensorFlow to OE/Yocto platform
description:
  TensorFlow is an open source software library for high performance numerical
  computation primarily used in machine learning. Its flexible architecture
  allows easy deployment of computation across a variety of types of platforms
  (CPUs, GPUs, TPUs), and a range of systems from single desktops to clusters
  of servers to mobile and edge devices.
  (https://www.tensorflow.org/)

  The build system of TensorFlow is Bazel (https://bazel.build/).

  This layer integrates TensorFlow to OE/Yocto platform
  - Integrate Google's bazel to Yocto
  - Add Yocto toolchain for bazel to support cross compiling.
  - Replace python package system(pip/wheel) with Yocto package system(rpm/deb/ipk).


up_date: 2019-03-15 21:03:58
name: meta-calaos
vcs_url: https://github.com/calaos/meta-calaos
vcs_web_url: http://github.com/calaos/meta-calaos
vcs_web_tree_base_url: http://github.com/calaos/meta-calaos/tree/%branch%/
vcs_web_file_base_url: http://github.com/calaos/meta-calaos/blob/%branch%/
summary: Calaos OS
description:
  Calaos is a home automation system. Calaos-OS is the openembedded based distro containing all calaos softwares preconfigured


up_date: 2019-03-31 19:03:53
name: meta-nanopi-neo4
vcs_url: https://gitlab.com/dimtass/meta-nanopi-neo4
vcs_web_url: http://gitlab.com/dimtass/meta-nanopi-neo4
vcs_web_tree_base_url: http://gitlab.com/dimtass/meta-nanopi-neo4/tree/%branch%/
vcs_web_file_base_url: http://gitlab.com/dimtass/meta-nanopi-neo4/blob/%branch%/
summary: Meta layer for the NanoPi-Neo4
description:
  This meta layer expands the meta-rockchip layer and adds the armbian BSP patches for the NanoPi-neo4. The layer features:

  * updated uboot & kernel from the Armbian distro
  * libmali support for 3D acceleration
  * Images for Xorg, Wayland & Qt5 (only wayland tested properly)
  * Recipe to overclock all the cores

  Read the repo README for all the info.


up_date: 2019-05-22 15:05:43
name: de-ensc-bpi-router
vcs_url: https://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router
vcs_web_url: http://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router
vcs_web_tree_base_url: http://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router/tree/%branch%/%path%
vcs_web_file_base_url: http://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router/blob/%branch%/%path%
summary: router + telephony bsp
description:
  Base layer of a BSP which provides router and voip telephony (asterisk) functionality. It is secured by SELinux


up_date: 2023-03-29 14:03:27
name: meta-inango-crossreference
vcs_url: https://github.com/InangoSystems/meta-inango-crossreference.git
vcs_web_url: https://github.com/InangoSystems/meta-inango-crossreference
vcs_web_tree_base_url: https://github.com/InangoSystems/meta-inango-crossreference/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/InangoSystems/meta-inango-crossreference/blob/%branch%/%path%
summary: Generates cross reference indexes (ctags, cscope) for all build packages
description:
  Inango cross reference meta layer allows to generate cross reference indexes for all build packages.

  Currently supported cross reference tools are next:

  - ctags       (by default)
  - cscope

  Generated indexes may used by you favourite browser to jump easily to the declaration of any global identifier referenced in source code. Quick access to function declarations, data (type) definitions and preprocessor macros makes code browsing more convenient.


up_date: 2019-05-13 17:05:51
name: meta-webstuff
vcs_url: https://github.com/kernelconcepts/meta-webstuff
vcs_web_url: http://github.com/kernelconcepts/meta-webstuff
vcs_web_tree_base_url: http://github.com/kernelconcepts/meta-webstuff/tree/%branch%/
vcs_web_file_base_url: http://github.com/kernelconcepts/meta-webstuff/blob/%branch%/
summary: Random embedded web browser and server bits
description:
  Some random useful bits for web related bits in the embedded world such as sessions starting browsers, some web related server applications and demo images.


up_date: 2025-05-02 02:05:29
name: meta-acrn
vcs_url: https://github.com/intel/meta-acrn
vcs_web_url: http://github.com/intel/meta-acrn
vcs_web_tree_base_url: http://github.com/intel/meta-acrn/tree/%branch%/
vcs_web_file_base_url: http://github.com/intel/meta-acrn/blob/%branch%/
summary: ACRN hypervisor integration
description:
  Layer to integrate the ACRN hypervisor with OpenEmbedded: build your Service OS or Guest OS with Yocto Project.


up_date: 2019-06-30 20:06:24
name: meta-buildkite
vcs_url: https://github.com/EmbeddedAndroid/meta-buildkite
vcs_web_url: http://github.com/EmbeddedAndroid/meta-buildkite
vcs_web_tree_base_url: http://github.com/EmbeddedAndroid/meta-buildkite/tree/%branch%/
vcs_web_file_base_url: http://github.com/EmbeddedAndroid/meta-buildkite/blob/%branch%/
summary: OpenEmbedded/Yocto Project layer for the Buildkite Agent
description:
  The Buildkite Agent is an open-source toolkit written in Golang for securely running build jobs on any device or network.

  For more information see https://buildkite.com


up_date: 2024-01-31 02:01:30
name: meta-tangle
vcs_url: https://github.com/iotaledger/meta-iota
vcs_web_url: https://github.com/iotaledger/meta-iota
vcs_web_tree_base_url: http://github.com/iotaledger/meta-iota/
vcs_web_file_base_url: http://github.com/iotaledger/meta-iota
summary: OpenEmbedded layer for IOTA Distributed Ledger Technology (Tangle)
description:
  IOTA is an open-source distributed ledger and cryptocurrency designed for the Internet of things. It uses a directed acyclic graph to store transactions on its ledger, motivated by a potentially higher scalability over blockchain based distributed ledgers.

  The meta-iota OpenEmbedded Layer aims to provide recipes for IOTA related programs, tools and libraries in order to support the IOTA Tangle Ledger on a large variety of embedded devices.


up_date: 2019-08-07 17:08:03
name: meta-rust-bin
vcs_url: https://github.com/rust-embedded/meta-rust-bin
vcs_web_url: http://github.com/rust-embedded/meta-rust-bin
vcs_web_tree_base_url: http://github.com/rust-embedded/meta-rust-bin/tree/%branch%/
vcs_web_file_base_url: http://github.com/rust-embedded/meta-rust-bin/blob/%branch%/
summary: Support for Rust/Cargo Using Prebuilt Compiler/Std Packages from Core Project
description:
  The meta-rust-bin layer provides support for building rust/cargo projects using the toolchains distributed by the core rust project rather than using a custom-built compiler/std as is done by meta-rust.  This allows for the layer to track upstream compiler versions more closely at the loss of some amount of potential customization/control.

  This layer is maintained by the Rust Embedded Working Group Embedded Linux Team: https://github.com/rust-embedded/wg#the-embedded-linux-team


up_date: 2019-09-17 01:09:22
name: meta-openssl102
vcs_url: git://git.yoctoproject.org/meta-openssl102
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102/tree/%path%?h=%branch%
summary: OpenSSL 1.0.2 support
description:
  This layer provides the older OpenSSL 1.0.2.  This alternative version 
  can be used as the default OpenSSL if the older version is required for 
  some reason.


up_date: 2019-09-17 01:09:34
name: meta-openssl102-fips
vcs_url: git://git.yoctoproject.org/meta-openssl102-fips
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/tree/%path%?h=%branch%
summary: FIPS Object Module support for OpenSSL 1.0.2
description:
  This layer provides a reference implementation of OpenSSL FIPS Object Module for OpenSSL 1.0.2.  The user is responsible for precompiling the necessary
  openssl-fips binary objects.

   See:

      https://www.openssl.org/docs/fips/SecurityPolicy-2.0.16.pdf
      https://www.openssl.org/docs/fips/UserGuide-2.0.pdf


up_date: 2020-09-17 03:09:58
name: meta-licscan
vcs_url: https://github.com/vaisala-oss/meta-licscan.git
vcs_web_url: https://github.com/vaisala-oss/meta-licscan
summary: Source code license analysis for Yocto based OS distributions
description:
  This meta layer is a complementary facility for disambiguating software license compliance standing of devices that contain software artifacts built from source code with Yocto framework. It facilitates generation of .json files containing both source code license analysis results (on a per-file basis) as well as relevant parts of Yocto metadata related to prementioned software artifacts.

  A command line utility for studying image-wide and package-specific license analysis results from prementioned .json files is also provided.


up_date: 2022-04-10 05:04:59
name: meta-coral
vcs_url: https://github.com/mirzak/meta-coral
vcs_web_url: http://github.com/mirzak/meta-coral
vcs_web_tree_base_url: https://github.com/mirzak/meta-coral/tree/%branch%/
vcs_web_file_base_url: https://github.com/mirzak/meta-coral/blob/%branch%/
summary: OpenEmbedded/Yocto BSP layer for Google Coral Dev Board
description:
  OpenEmbedded/Yocto BSP layer for Google Coral Dev Board

       https://coral.withgoogle.com/products/dev-board/

  The components of this BSP are based on Mendel OS, the custom Debian distribution that is officially supported on the Google Coral Dev Board.


up_date: 2019-10-06 22:10:15
name: meta-cloonix
vcs_url: https://github.com/joaohf/meta-cloonix
vcs_web_url: http://github.com/joaohf/meta-cloonix
vcs_web_tree_base_url: http://github.com/joaohf/meta-cloonix/tree/%branch%/
vcs_web_file_base_url: http://github.com/joaohf/meta-cloonix/blob/%branch%/
summary: Creates a distro suitable to use with cloonix network simulator
description:
  This layer allows creating images that can be used as kvm images to run cloonix network simulations.

  See more details about cloonix project here: https://clownix.net

  In a long-term roadmap, this layer will provide all tools needed to build and use cloonix.


up_date: 2023-04-28 05:04:57
name: meta-direwolf
vcs_url: https://github.com/ew1abz/meta-direwolf.git
vcs_web_url: http://github.com/ew1abz/meta-direwolf
vcs_web_tree_base_url: http://github.com/ew1abz/meta-direwolf/tree/%branch%/
vcs_web_file_base_url: http://github.com/ew1abz/meta-direwolf/blob/%branch%/
summary: Software layer providing recipes for Direwolf (Soundcard based AX.25 TNC)
description:
  Software layer providing recipes for Direwolf (Soundcard based AX.25 TNC).

  Dire Wolf is a modern software replacement for the old 1980's style TNC built with special hardware.

  Dependency: alsa-lib, gpsd


up_date: 2024-02-10 15:02:09
name: meta-opendds
vcs_url: https://github.com/OpenDDS/meta-opendds.git
vcs_web_url: https://github.com/OpenDDS/meta-opendds
vcs_web_tree_base_url: https://github.com/OpenDDS/meta-opendds/tree/%branch%/
vcs_web_file_base_url: https://github.com/OpenDDS/meta-opendds/blob/%branch%/
summary: Recipes for building OpenDDS
description:
  The layer contains two recipes for OpenDDS: one versioned, one not.

  The unversioned recipe  is provided to allow clients, via a bbappend, to
  build - for example - the HEAD of the master branch or some other version.

  To use this unversioned recipe, add the following to your local.conf or
  distro configuration file.

      PREFERRED_VERSION_opendds="1.0+git%"

  Note that simply providing a different branch and SRCREV may be insufficient.
  If your desired commit is significantly newer than that used for the versioned
  recipe, then the generic build instructions may be insufficient or incorrect.


up_date: 2019-10-29 03:10:17
name: meta-mender-commercial
vcs_url: https://github.com/mendersoftware/meta-mender
vcs_web_url: http://github.com/mendersoftware/meta-mender
vcs_web_tree_base_url: http://github.com/mendersoftware/meta-mender/tree/%branch%/
vcs_web_file_base_url: http://github.com/mendersoftware/meta-mender/blob/%branch%/
summary: A layer containing commercial Mender features and software
description:
  This layer contains the commercial mender-binary-delta Update Module, for use with the Mender client in the meta-mender-core layer. The Update Module performs binary delta updates, which are block based updates which only contain the difference between the old and new image, and hence are much smaller than a typical full update.


up_date: 2022-04-10 19:04:22
name: meta-microservicebus-raspberrypi
vcs_url: https://github.com/axians/meta-microservicebus.git
vcs_web_url: https://github.com/axians/meta-microservicebus
vcs_web_tree_base_url: http://github.com/axians/meta-microservicebus/tree/%branch%/
vcs_web_file_base_url: http://github.com/axians/meta-microservicebus/blob/%branch%/
summary: microServiceBus-node example integration for Raspberry Pi with RAUC and U-Boot
description:
  microServiceBus.com is an integration platform for IoT and enterprise applications.
  This platform lets you expose microservices from small devices and large systems using a remote hosting infrastructure.
  These nodes can run on both Linux and Windows using components built either natively (ARM) or using node.js.
  This layer is an example integration for Raspberry Pi with firmware update with RAUC and dual boot by U-Boot.


up_date: 2019-11-24 19:11:18
name: meta-homebridge
vcs_url: https://github.com/leon-anavi/meta-homebridge.git
vcs_web_url: http://github.com/leon-anavi/meta-homebridge
vcs_web_tree_base_url: http://github.com/leon-anavi/meta-homebridge/tree/%branch%/
vcs_web_file_base_url: http://github.com/leon-anavi/meta-homebridge/blob/%branch%/
summary: Layer for Homebridge
description:
  This layer provides Homebridge, a lightweight NodeJS server that emulates the iOS HomeKit API, several plugins and supplementary recipes useful for home automation.


up_date: 2019-12-03 20:12:28
name: meta-python2
vcs_url: git://git.openembedded.org/meta-python2
vcs_web_url: http://cgit.openembedded.org/meta-python2
vcs_web_tree_base_url: http://cgit.openembedded.org/meta-python2/tree/%path%?h=%branch%
vcs_web_file_base_url: http://cgit.openembedded.org/meta-python2/tree/%path%?h=%branch%
summary: Layer enabling legacy python2 support after EOL
description:
  This is the home for your python2 recipes. Python3 recipes will continue to be supported via the original meta-python layer.

  Python 2 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.

  If your organization has legacy python2 code or depends upon upstream python2-only code, the time has come for you to move on. Porting from python2 to python3 is well documented.

  Continuing to depend upon python2-only code will increasingly open you up to security issues, vulnerabilities and breakage.


up_date: 2019-12-05 09:12:36
name: meta-sancloud
vcs_url: https://github.com/SanCloudLtd/meta-sancloud.git
vcs_web_url: https://github.com/SanCloudLtd/meta-sancloud
vcs_web_tree_base_url: https://github.com/SanCloudLtd/meta-sancloud/tree/
vcs_web_file_base_url: https://github.com/SanCloudLtd/meta-sancloud/blob/
summary: BSP Layer for the Sancloud BeagleBone Enhanced (BBE)
description:
  This is the Yocto Project Board Support Package (BSP) layer for SanCloud devices.

  Currently supported hardware with corresponding Yocto Project MACHINE names:

  * bbe: Sancloud BeagleBone Enhanced (BBE)

  This BSP is layer is tested in two primary configurations:

  * Automotive Grade Linux (AGL)
  * Arago Distribution

  Additionally, this BSP layer should work with the distro-less configuration included in openembedded-core as well as the Poky distribution.


up_date: 2025-11-03 19:11:29
name: meta-arm
vcs_url: git://git.yoctoproject.org/meta-arm
vcs_web_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm
vcs_web_tree_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/%path%?h=%branch%
vcs_web_file_base_url: http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/%path%?h=%branch%
summary: General layer for Arm recipes
description:
  This layer provides support for general recipes for the Arm architecture.  Anything that's not needed explicitly for BSPs, the IOTA distribution, or destined to be upstreamed belongs here.


up_date: 2020-02-02 20:02:41
name: meta-noto
vcs_url: https://github.com/ssfivy/meta-noto.git
vcs_web_url: http://github.com/ssfivy/meta-noto
vcs_web_tree_base_url: http://github.com/ssfivy/meta-noto/tree/%branch%/
vcs_web_file_base_url: http://github.com/ssfivy/meta-noto/blob/%branch%/
summary: Yocto / OpenEmbedded Layer for Google Noto fonts.
description:
  This is a layer for installing fonts from Google's Noto fonts collections. 

  This layer aims to allow installing only specific font styles, since you may not want to install all available fonts due to disk space requirements.


up_date: 2020-02-03 09:02:15
name: meta-influx
vcs_url: https://github.com/alihanyalcin/meta-influx.git
vcs_web_url: http://github.com/alihanyalcin/meta-influx
vcs_web_tree_base_url: http://github.com/alihanyalcin/meta-influx/tree/%branch%/
vcs_web_file_base_url: http://github.com/alihanyalcin/meta-influx/blob/%branch%/
summary: Yocto Project meta layer for the TICK (Telegraf, InfluxDB, Chronograf, Kapacitor) Stack
description:
  This Yocto meta layer contains all the recipes needed to build the TICK Stack (Telegraf, InfluxDB, Chronograf, Kapacitor) into a Yocto image for ARM architecture.


up_date: 2025-10-21 14:10:11
name: meta-aws
vcs_url: https://github.com/aws4embeddedlinux/meta-aws
vcs_web_url: https://github.com/aws4embeddedlinux/meta-aws
vcs_web_tree_base_url: http://github.com/aws4embeddedlinux/meta-aws/tree/%branch%/
vcs_web_file_base_url: http://github.com/aws4embeddedlinux/meta-aws/blob/%branch%/
summary: The standard layer for Amazon Web Services off-cloud software.
description:
  The meta-aws layer provides mechanisms for building and installing off-cloud software to make it easier for you to build solutions for AWS on embedded hardware that you own and operate for yourself or your customers.


up_date: 2023-03-09 17:03:36
name: meta-flutter
vcs_url: https://github.com/meta-flutter/meta-flutter
vcs_web_url: https://github.com/meta-flutter/meta-flutter
vcs_web_tree_base_url: https://github.com/meta-flutter/meta-flutter/tree/%branch%/
vcs_web_file_base_url: https://github.com/meta-flutter/meta-flutter/blob/%branch%/
summary: Google's UI toolkit
description:
  Flutter is Google's UI toolkit for crafting beautiful, natively compiled applications for mobile, web, and desktop from a single codebase.


up_date: 2020-05-04 18:05:01
name: meta-edgex
vcs_url: https://github.com/alihanyalcin/meta-edgex.git
vcs_web_url: http://github.com/alihanyalcin/meta-edgex
vcs_web_tree_base_url: http://github.com/alihanyalcin/meta-edgex/tree/%branch%/
vcs_web_file_base_url: http://github.com/alihanyalcin/meta-edgex/blob/%branch%/
summary: Yocto Project meta layer for EdgeX Foundry Services
description:
  This Yocto meta layer contains the recipes needed to build EdgeX Foundry Services that is open-source IoT edge computing solution.


up_date: 2020-05-14 17:05:05
name: meta-microcontroller
vcs_url: https://github.com/schnitzeltony/meta-microcontroller.git
vcs_web_url: http://github.com/schnitzeltony/meta-microcontroller
vcs_web_tree_base_url: http://github.com/schnitzeltony/meta-microcontroller/tree/%branch%/
vcs_web_file_base_url: http://github.com/schnitzeltony/meta-microcontroller/blob/%branch%/
summary: Toolchain and development tools for AVR MCUs
description:
  This layer was created to build development tools for microcontrollers. Since building of native toolchain is necessary it is possible to ship binaries compiled from source into images.


up_date: 2023-12-24 13:12:12
name: meta-linux-mainline
vcs_url: https://github.com/betafive/meta-linux-mainline.git
vcs_web_url: https://github.com/betafive/meta-linux-mainline
vcs_web_tree_base_url: https://github.com/betafive/meta-linux-mainline/tree/%branch%/
vcs_web_file_base_url: https://github.com/betafive/meta-linux-mainline/blob/%branch%/
summary: A collection of Yocto Project recipes for the Linux kernel and related tools
description:
  A collection of Yocto Project recipes for the mainline and stable Linux
  kernel releases from kernel.org.


up_date: 2020-06-04 18:06:42
name: meta-updatefactory
vcs_url: https://github.com/Kynetics/meta-updatefactory
vcs_web_url: http://github.com/Kynetics/meta-updatefactory
vcs_web_tree_base_url: http://github.com/Kynetics/meta-updatefactory/tree/%branch%/
vcs_web_file_base_url: http://github.com/Kynetics/meta-updatefactory/blob/%branch%/
summary: Yocto support on the device side for Update Factory platform
description:
  Update Factory is an artifact content and software update delivery IoT Platform supporting single and double copy updates for connected Android and Linux devices. Update Factory is based on Eclipse hawkBit, and it is compatible with the same clients and APIs.
  The meta-updatefactory layer provides the integration of single copy updates for the Openembedded / Yocto buildsystem, to build embedded Linux distribution that can connect and install updates from Update Factory or hawkBit servers. The layers supports both SysV and systemd init systems and integrates on top of meta-swupdate.


up_date: 2021-04-12 09:04:52
name: meta-intelfpga
vcs_url: https://github.com/robseb/meta-intelfpga
vcs_web_url: http://github.com/robseb/meta-intelfpga
vcs_web_tree_base_url: http://github.com/robseb/meta-intelfpga/tree/%branch%/
vcs_web_file_base_url: http://github.com/robseb/meta-intelfpga/blob/%branch%/
summary: Intel (ALTERA) SoC-FPGA (SoCFPGA) BSP layer compatible with Intel SoC EDS
description:
  With this layer the board support package (BSP) for ARM based Intel (ALTERA) SoC-FPGAs (SoCFPGA) is added to the Yocto Project.
  It can bring with the rstools useful tools to interact with the FPGA fabric (e.g. Changing the FPGA configuration or accessing all ARM AXI Bride interfaces).
  In addition, is the ARM Development Studio (DS-5) Streamline Server gator included.

  Usually the Yocto Project can generate all required components (rootfs, device tree, bootloaders,...) to boot up a final embedded Linux. But this is not compatible with Intel's Boot flow. This Bootflow uses the Intel Embedded Design Suite (SoC EDS) to build the Linux Device Tree and all necessary bootloaders.

  For that reason, I designed a version that is compatible with Intel's development tools.
  This includes the board specific u-boot- and device tree-generation and the support for only the .tar.gz-file type for the rootfs.

  I used this layer to build rsyocto, an open source embedded Linux Distribution for Intel SoC-FPGAs, by myself. The flexibility of my own rsyocto build system allows you to use it for your own projects with your custom embedded Linux.

  I designed a Python script that can automate the boot image desgin with a specifiable partition table. It can generate a bootable image file with Kernel-,bootloader- and user-files. With the flexibility of this script it is compatible with Intel SoC-EDS build flow for example it can pre-install FPGA configuration files.

  You can find step-by-step instructions for using this BSP layer on Github.


up_date: 2020-06-12 18:06:10
name: meta-microblx
vcs_url: https://github.com/kmarkus/meta-microblx
vcs_web_url: http://github.com/kmarkus/meta-microblx
vcs_web_tree_base_url: http://github.com/kmarkus/meta-microblx/tree/%branch%/
vcs_web_file_base_url: http://github.com/kmarkus/meta-microblx/blob/%branch%/
summary: microblx function blocks and extensions
description:
  microblx is a lightweight and hard real-time safe function block framework for embedded control and signal processing. meta-microblx contains recipes to build core microblx and additional microblx based function blocks.


up_date: 2020-06-24 17:06:22
name: meta-libretro
vcs_url: https://github.com/dev-0x7C6/meta-retro
vcs_web_url: http://github.com/dev-0x7C6/meta-retro
vcs_web_tree_base_url: http://github.com/dev-0x7C6/meta-retro/tree/%branch%/
vcs_web_file_base_url: http://github.com/dev-0x7C6/meta-retro/blob/%branch%/
summary: OpenEmbedded / Yocto software layer for RetroArch and libretro cores
description:
  This layer provides RetroArch front-end and libretro cores emulators recipes for use with OpenEmbedded and/or Yocto.


up_date: 2021-07-01 21:07:36
name: meta-cloud-hypervisor
vcs_url: https://github.com/cloud-hypervisor/meta-cloud-hypervisor.git
vcs_web_url: https://github.com/cloud-hypervisor/meta-cloud-hypervisor
vcs_web_tree_base_url: https://github.com/cloud-hypervisor/meta-cloud-hypervisor/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/cloud-hypervisor/meta-cloud-hypervisor/blob/%branch%/%path%
summary: Meta layer providing Cloud Hypervisor and accompanying tools
description:
  Cloud Hypervisor is an open source Virtual Machine Monitor (VMM) that runs on top of KVM. This layer provides recipes for Cloud Hypervisor and accompanying tools.


up_date: 2020-08-26 20:08:43
name: meta-nanopi-rockchip64
vcs_url: https://gitlab.com/dimtass/meta-nanopi-rockchip64.git
vcs_web_url: https://gitlab.com/dimtass/meta-nanopi-rockchip64/
vcs_web_tree_base_url: https://gitlab.com/dimtass/meta-nanopi-rockchip64/tree/%branch%/%path%
vcs_web_file_base_url: https://gitlab.com/dimtass/meta-nanopi-rockchip64/blob/%branch%/%path%
summary: A BSP layer for nanopi SBCs based on the rockchip64 SoCs
description:
  This layer is meant to support some of the FriendlyArm nanopi boards which are based on Rochchip64 SoCs. Currently only RK3328 boards are supported.

  Have in mind that there's already another layer for the nanopi-neo4 which is based on the RK3399, but this might merged here in the future.


up_date: 2020-08-27 18:08:45
name: meta-shellhub
vcs_url: https://github.com/shellhub-io/meta-shellhub
vcs_web_url: https://github.com/shellhub-io/meta-shellhub
vcs_web_tree_base_url: https://github.com/shellhub-io/meta-shellhub/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/shellhub-io/meta-shellhub/blob/%branch%/%path%
summary:
  ShellHub is a modern SSH server for remotely accessing Linux devices via command line (using any SSH client) or web-based user interface

description:
  ShellHub is a modern SSH server for remotely accessing Linux devices via command line (using any SSH client) or web-based user interface. It is intended to be used instead of sshd.

  Typically, if you want to SSH a Linux device on a local network, you just need to know its IP address. However, in order to access a Linux device from outside the local network, you will have to go through a few inconveniences, such as getting its public IP address and configuring the router. Changing the VPN/firewall configuration can be cumbersome if the device is behind a corporate firewall that does not allow SSH connections.

  ShellHub provides a way to avoid all these hassles, helping you easily and seamlessly access any Linux device behind firewall and NAT.


up_date: 2022-01-14 04:01:44
name: meta-elastic-beats
vcs_url: https://gitlab.com/dimtass/meta-elastic-beats.git/
vcs_web_url: http://gitlab.com/dimtass/meta-elastic-beats
vcs_web_tree_base_url: http://gitlab.com/dimtass/meta-elastic-beats/tree/%branch%/
vcs_web_file_base_url: http://gitlab.com/dimtass/meta-elastic-beats/blob/%branch%/
summary: A software layer for Elastic Stack beats
description:
  This is a recipe meta layer for Yocto that builds the official elastic beats
  found  in here: https://www.elastic.co/beats/


up_date: 2020-10-11 21:10:55
name: meta-openamp
vcs_url: https://github.com/Xilinx/meta-openamp
vcs_web_url: http://github.com/Xilinx/meta-openamp
vcs_web_tree_base_url: http://github.com/Xilinx/meta-openamp/tree/%branch%/
vcs_web_file_base_url: http://github.com/Xilinx/meta-openamp/blob/%branch%/
summary: Provides support for building libmetal and OpenAMP libraries
description:
  The OpenAMP framework provides software components that enable development of software applications for Asymmetric Multiprocessing (AMP) systems. The framework provides the following key capabilities.

  - Provides Life Cycle Management, and Inter Processor Communication capabilities for management of remote compute resources and their associated software contexts.

  - Provides a stand alone library usable with RTOS and Baremetal software environments

  - Compatibility with upstream Linux remoteproc and rpmsg components

  - Following AMP configurations supported a. Linux master/Generic(Baremetal) remote b. Generic(Baremetal) master/Linux remote

  - Proxy infrastructure and supplied demos showcase ability of proxy on master to handle printf, scanf, open, close, read, write calls from Bare metal based remote contexts.


up_date: 2025-03-31 14:03:06
name: meta-ros-webos
vcs_url: https://github.com/ros/meta-ros-webos.git
vcs_web_url: http://github.com/ros/meta-ros-webos
vcs_web_tree_base_url: http://github.com/ros/meta-ros-webos/tree/%branch%/
vcs_web_file_base_url: http://github.com/ros/meta-ros-webos/blob/%branch%/
summary: ROS (Robot Operating System) integration layer for webOS OSE support
description:
  ROS (Robot Operating System) support layer

  makes webOS OSE DISTRO compatible with meta-ros layers.


up_date: 2020-10-11 21:10:19
name: meta-topic
vcs_url: https://github.com/topic-embedded-products/meta-topic
vcs_web_url: https://github.com/topic-embedded-products/meta-topic
vcs_web_tree_base_url: https://github.com/topic-embedded-products/meta-topic?a=tree;f=%path%;hb=refs/heads/%branch%
vcs_web_file_base_url: https://github.com/topic-embedded-products/meta-topic?a=blob;f=%path%;hb=refs/heads/%branch%
summary: BSP for TOPIC boards
description:
  Provides kernel, bootloader and other support for the TOPIC Miami family of system-on-modules and carriers


up_date: 2024-01-31 22:01:19
name: meta-ros-python2
vcs_url: https://github.com/ros/meta-ros.git
vcs_web_url: http://github.com/ros/meta-ros
vcs_web_tree_base_url: http://github.com/ros/meta-ros/tree/%branch%/
vcs_web_file_base_url: http://github.com/ros/meta-ros/blob/%branch%/
summary: ROS (Robot Operating System) support layer - extra recipes for python2 support
description:
  ROS (Robot Operating System) support layer

  Few extra recipes needed for ROS distributions still using python2 (currently only ROS1 Melodic)


up_date: 2021-01-08 04:01:10
name: meta-chaos
vcs_url: https://github.com/mkilivan/meta-chaos
vcs_web_url: http://github.com/mkilivan/meta-chaos
vcs_web_tree_base_url: http://github.com/mkilivan/meta-chaos/tree/%branch%/
vcs_web_file_base_url: http://github.com/mkilivan/meta-chaos/blob/%branch%/
summary: Set of recipes for home automation projects.
description:
  meta-chaos is a set of recipes for the poky build system, which enables cross-building GNU/Linux images for home automation projects. By enabling meta-chaos, you can cross-build some of the popular projects, such as Homebridge and wifi-connect.


up_date: 2021-01-08 04:01:43
name: meta-dca
vcs_url: https://github.com/priv-kweihmann/meta-dca
vcs_web_url: http://github.com/priv-kweihmann/meta-dca
vcs_web_tree_base_url: http://github.com/priv-kweihmann/meta-dca/tree/%branch%/
vcs_web_file_base_url: http://github.com/priv-kweihmann/meta-dca/blob/%branch%/
summary: Layer for dynamic code analysis and security hardening
description:
  This layer is an addition to meta-sca. It enables dynamic code analysis, such as
  - checking capabilties
  - memleak checking
  - files/path checking
  These checks are suppose to be done on the build host only (using qemu/testimage support)


up_date: 2021-01-28 20:01:43
name: meta-kde
vcs_url: https://invent.kde.org/packaging/yocto-meta-kde
vcs_web_url: https://invent.kde.org/packaging/yocto-meta-kde
vcs_web_tree_base_url: https://invent.kde.org/packaging/yocto-meta-kde/tree/%branch%/%path%
vcs_web_file_base_url: https://invent.kde.org/packaging/yocto-meta-kde/blob/%branch%/%path%
summary: Yocto packaging metadata for KDE projects
description:
  This layer contains recipes for workspace and application products of the KDE
  community. For KDE Frameworks recipes see meta-kf5.


up_date: 2021-03-15 00:03:41
name: meta-amateurradio
vcs_url: https://github.com/adrians/meta-amateurradio
vcs_web_url: http://github.com/adrians/meta-amateurradio
vcs_web_tree_base_url: http://github.com/adrians/meta-amateurradio/tree/%branch%/
vcs_web_file_base_url: http://github.com/adrians/meta-amateurradio/blob/%branch%/
summary: Recipes for SDR packages, digital modes and other ham radio software
description:
  This layer is intended to add recipes for SDR packages, digital modes and other software intended for amateur radio operators.


up_date: 2021-03-23 23:03:20
name: meta-tanowrt
vcs_url: https://github.com/tano-systems/meta-tanowrt.git
vcs_web_url: https://github.com/tano-systems/meta-tanowrt
vcs_web_tree_base_url: https://github.com/tano-systems/meta-tanowrt/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/tano-systems/meta-tanowrt/blob/%branch%/%path%
summary: TanoWrt Distribution
description:
  TanoWrt is an operating system distribution based on the Linux kernel and focused on running in embedded systems, including real-time systems.

  This layer provides OpenEmbedded metadata for TanoWrt Linux distribution by Tano Systems. TanoWrt distribution is based on packages and fixes (patches) from the official OpenWrt distribution.


up_date: 2021-04-21 01:04:58
name: meta-tanowrt-hsl-ti
vcs_url: https://github.com/tano-systems/meta-tanowrt.git
vcs_web_url: https://github.com/tano-systems/meta-tanowrt
vcs_web_tree_base_url: https://github.com/tano-systems/meta-tanowrt/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/tano-systems/meta-tanowrt/blob/%branch%/%path%
summary: TanoWrt hardware support layer for the Texas Instruments (TI) SoC based boards
description:
  Hardware support layer for the Texas Instruments (TI) SoC based boards for TanoWrt Linux distribution. This layer contains demonstration support for a few boards based on Texas Instruments SoC's.


up_date: 2021-04-21 01:04:37
name: meta-tanowrt-hsl-nxp
vcs_url: https://github.com/tano-systems/meta-tanowrt.git
vcs_web_url: https://github.com/tano-systems/meta-tanowrt
vcs_web_tree_base_url: https://github.com/tano-systems/meta-tanowrt/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/tano-systems/meta-tanowrt/blob/%branch%/%path%
summary: TanoWrt hardware support layer for the NXP (Freescale) boards
description:
  Hardware support layer for the NXP (Freescale) SoC based boards for TanoWrt Linux distribution. This layer contains demonstration support for a few boards based on NXP SoC's.


up_date: 2021-04-21 02:04:37
name: meta-tanowrt-hsl-atmel
vcs_url: https://github.com/tano-systems/meta-tanowrt.git
vcs_web_url: https://github.com/tano-systems/meta-tanowrt
vcs_web_tree_base_url: https://github.com/tano-systems/meta-tanowrt/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/tano-systems/meta-tanowrt/blob/%branch%/%path%
summary: TanoWrt hardware support layer for the Microchip (Atmel) boards
description:
  Hardware support layer for the Microchip (Atmel) SoC based boards for TanoWrt Linux distribution. This layer contains demonstration support for a few boards based on Atmel SoC's.


up_date: 2022-04-10 16:04:51
name: meta-ethereum
vcs_url: https://github.com/oe-eth/meta-ethereum
vcs_web_url: http://github.com/oe-eth/meta-ethereum
vcs_web_tree_base_url: http://github.com/oe-eth/meta-ethereum/tree/%branch%/
vcs_web_file_base_url: http://github.com/oe-eth/meta-ethereum/blob/%branch%/
summary: OpenEmbedded Layer for Ethereum nodes, validators and staking pools.
description:
  The upcoming wave of blockchain-enabled IoT devices is creating a rising demand for embedded support of the Ethereum protocol

  The meta-ethereum OpenEmbedded Layer aims to provide recipes for Ethereum related programs, tools and libraries in order to support the Ethereum blockchain on a large variety of embedded devices.


up_date: 2021-06-09 13:06:36
name: meta-iris-thirdparty
vcs_url: https://github.com/iris-GmbH/meta-iris-thirdparty.git
vcs_web_url: http://github.com/iris-GmbH/meta-iris-thirdparty
vcs_web_tree_base_url: http://github.com/iris-GmbH/meta-iris-thirdparty/tree/%branch%/
vcs_web_file_base_url: http://github.com/iris-GmbH/meta-iris-thirdparty/blob/%branch%/
summary: This layer contains recipes for various software used within our IRIS IRMA SIX product.
description:
  This repository contains recipes for various software used within our IRIS IRMA SIX product. We try to keep the recipes as generic as possible in order to cover common use-cases. Feel free to integrate this layer into your own Yocto builds. Contributions are welcome!


up_date: 2024-08-21 16:08:31
name: meta-wayland
vcs_url: https://codeberg.org/flk/meta-wayland
vcs_web_url: https://codeberg.org/flk/meta-wayland
vcs_web_tree_base_url: https://codeberg.org/flk/meta-wayland/src/branch/%branch%/%path%
vcs_web_file_base_url: https://codeberg.org/flk/meta-wayland/src/branch/%branch%/%path%
summary: Recipes to create wayland/wlroots based compositors
description:
  This layer adds recipes to build wlroots based compositors under wayland.
  It contains wlroots, sway, wayfire and some additional recipes that might come useful.


up_date: 2023-05-12 01:05:28
name: meta-orangepi-r1plus
vcs_url: https://github.com/Blink-Project/meta-orangepi-r1plus-bsp
vcs_web_url: https://github.com/Blink-Project/meta-orangepi-r1plus-bsp
vcs_web_tree_base_url: https://github.com/Blink-Project/meta-orangepi-r1plus-bsp/tree/%branch%/
vcs_web_file_base_url: https://github.com/Blink-Project/meta-orangepi-r1plus-bsp/blob/%branch%/
summary: BSP layer for Orangepi R1+ boards
description:
  Contains machine definition, kernel configuration, u-boot configuration and image setup for Orange Pi R1+ Boards.


up_date: 2021-09-09 19:09:53
name: meta-octoprint
vcs_url: https://github.com/dev-0x7C6/meta-octoprint.git
vcs_web_tree_base_url: http://github.com/dev-0x7C6/meta-octoprint/tree/%branch%/
vcs_web_file_base_url: http://github.com/dev-0x7C6/meta-octoprint/blob/%branch%/
summary: OpenEmbedded / Yocto software layer for Octoprint software.
description:
  This layer provides Octoprint front-end and 3d-printing tools recipes for use with OpenEmbedded and/or Yocto.


up_date: 2021-09-20 15:09:57
name: meta-rauc-raspberrypi
vcs_url: https://github.com/rauc/meta-rauc-community.git
vcs_web_url: https://github.com/rauc/meta-rauc-community
vcs_web_tree_base_url: https://github.com/rauc/meta-rauc-community/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/rauc/meta-rauc-community/blob/%branch%/%path%
summary: RAUC Update Framework - Raspberry PI Support (Examples)
description:
  The layer contains the integration steps required to set up exemplary redundant boot scenarios with RAUC on the Raspberry PI platform.


up_date: 2022-03-29 11:03:15
name: meta-python-mixin
vcs_url: https://gitlab.eclipse.org/eclipse/oniro-core/meta-python-mixin
vcs_web_url: https://gitlab.eclipse.org/eclipse/oniro-core/meta-python-mixin
vcs_web_tree_base_url: https://gitlab.eclipse.org/eclipse/oniro-core/meta-python-mixin/tree/%branch%/%path%
vcs_web_file_base_url: https://gitlab.eclipse.org/eclipse/oniro-core/meta-python-mixin/blob/%branch%/%path%
summary:
  "Mixin" layer on top of meta-python for additional modules, versions or various other backported functionality.

description:
  This layer extends meta-python (stable/LTS branches) by providing and maintaining more support for packages and functionalities. For example, maintaining older/newer versions of various python modules.


up_date: 2021-10-19 19:10:00
name: meta-luarocks
vcs_url: https://github.com/chris2511/meta-luarocks
summary: Many LUA recipes built with luarocks
description:
  This layer imports a lot of lua packages and builds them with the luarocks package manager with an adopted config file to use the Yocto toolchain compiler


up_date: 2021-11-18 12:11:49
name: meta-tanowrt-hsl-baikal
vcs_url: https://github.com/tano-systems/meta-tanowrt.git
vcs_web_url: https://github.com/tano-systems/meta-tanowrt
vcs_web_tree_base_url: https://github.com/tano-systems/meta-tanowrt/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/tano-systems/meta-tanowrt/blob/%branch%/%path%
summary:
  TanoWrt hardware support layer for the hardware support layer for the Baikal Electronics SoC boards.

description:
  Hardware support layer for the Baikal Electronics SoC based boards for TanoWrt Linux distribution. This layer contains demonstration support for a few boards based on Baikal Electronics SoC's.


up_date: 2021-12-05 21:12:39
name: meta-patito
vcs_url: https://github.com/jloaiza/meta-patito
vcs_web_url: http://github.com/jloaiza/meta-patito
vcs_web_tree_base_url: http://github.com/jloaiza/meta-patito/tree/%branch%/
vcs_web_file_base_url: http://github.com/jloaiza/meta-patito/blob/%branch%/
summary: This layer contains packages that their sole use is to troll or have fun.
description:
  This layer contains the packages:
  - sl
  - cowsay

  And an image that includes them called: useless-core-image


up_date: 2022-04-10 03:04:34
name: meta-lat
vcs_url: https://github.com/Wind-River/meta-lat.git
vcs_web_url: https://github.com/Wind-River/meta-lat
summary:
  The LAT (Linux Assembly Tool) is a tool that assembles various types of images using binary package feeds

description:
  This layer provides LAT (Linux Assembly Tool).

  Use this tool to perform a number of tasks to help manage your images,
  such as building and publishing RPM packages, generating images from
  package feeds for specific hardware, generating an updated SDK, and
  verifying the sanity of the SDK build. In addition, you can add or
  remove packages, and specify any pre- and post-build (do_build)
  instructions for the build, which lets you customize your image to
  meet your needs.

  This tool uses *.yaml input files to define many aspects of the build,
  packages and package-related configuration for a variety of uses.
  It provides validation for the *.yaml input files that define your intended
  project output to help identify any incorrect or misspelled options.

  With the exampleyamls positional argument, you can generate a list
  of different sample *.yaml files, which you can use as a basis for
  customizing your builds. These reusable files provide a data reference
  for all your image customizations.

  LAT is a tool that assembles various types of images using binary package feeds. Currently it supports three types of package feeds.

      rpm: Yocto RPM feeds
      deb: Yocto DEB feeds
      external-debian: Debian package feeds


up_date: 2022-02-03 11:02:02
name: meta-rauc-qemux86
vcs_url: https://github.com/rauc/meta-rauc-community.git
vcs_web_url: https://github.com/rauc/meta-rauc-community
vcs_web_tree_base_url: https://github.com/rauc/meta-rauc-community/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/rauc/meta-rauc-community/blob/%branch%/%path%
summary: RAUC Update Framework - QEMU x86-64 Support (Examples)
description:
  The layer contains the integration steps required to set up exemplary redundant boot scenarios with RAUC on a QEMU x86-64 platform.


up_date: 2022-03-19 19:03:35
name: meta-ffmpeg4
vcs_url: https://github.com/schnitzeltony/meta-ffmpeg4.git
vcs_web_url: https://github.com/schnitzeltony/meta-ffmpeg4
summary: ffmpeg4 recipe
description:
  Supply a recipe of ffmpeg V4 to build projects that are not yet ported to ffmpeg V5 or are reluctant to port.


up_date: 2022-05-10 17:05:07
name: meta-openrc
vcs_url: https://github.com/jsbronder/meta-openrc.git
vcs_web_url: https://github.com/jsbronder/meta-openrc
summary: Support for the OpenRC init system
description:
  This layer adds support for using OpenRC as the init system when "openrc" is added to DISTRO_FEATURES


up_date: 2022-07-26 07:07:47
name: meta-shift
vcs_url: https://github.com/shift-left-test/meta-shift.git
vcs_web_url: https://github.com/shift-left-test/meta-shift
vcs_web_tree_base_url: https://github.com/shift-left-test/meta-shift/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/shift-left-test/meta-shift/blob/%branch%/%path%
summary: Support host-based unit test and static analysis tools for C/C++ projects
description:
  The meta-shift layer is a set of recipes and classes for the Bitbake build system, which allows developers to test or examine their C/C++ software modules in the host build environment.


up_date: 2022-07-19 02:07:30
name: meta-ktf
vcs_url: https://github.com/dchvs/meta-ktf.git
vcs_web_url: https://github.com/dchvs/meta-ktf.git
vcs_web_tree_base_url: https://github.com/dchvs/meta-ktf/tree/warrior
summary: Kernel Test Framework (KTF) support
description:
  This layer contains the support to build the Kernel Test Framework (KTF). 

  The framework provides a Google Test-like environment for writing C unit tests for Kernel code.


up_date: 2022-12-20 19:12:01
name: meta-synwall
vcs_url: https://github.com/SYNwall/meta-synwall
vcs_web_url: https://github.com/SYNwall/meta-synwall
summary: A zero config (IoT) firewall
description:
  SYNwall is a project built (for the time being) as a Linux Kernel Module, to implement a transparent and no-config/no-maintenance firewall.

  Usually IoT devices are out of a central control, with low profile hardware, tough environmental conditions and...we have no time to dedicate to maintain the security. So, may be we can not patch our IoT infrastructure and it will be very hard to maintain a "firewall-like" access control.

  The idea is to create a de-centralized one-way OneTimePassword code to enable the NETWORK access to the device. All the traffic not containing the OTP will be discarded. No prior knowledge about who need to access is required, we just need a Pre-Shared Key to deploy. The protection will be completely transparent to the application level, because implemented at network protocol level (TCP and UDP).


up_date: 2022-12-21 00:12:56
name: meta-dts
vcs_url: https://github.com/Dasharo/meta-dts.git
vcs_web_url: https://github.com/Dasharo/meta-dts
vcs_web_tree_base_url: https://github.com/Dasharo/meta-dts/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/Dasharo/meta-dts/blob/%branch%/%path%
summary:
  Dasharo Tools Suite (DTS) is a set of tools running in a minimal Linux environment, with a goal of deploying, updating and maintaining firmware on Dasharo supported devices.

description:
  Dasharo Tools Suite (DTS) is a set of tools running in a minimal Linux environment, with a goal of deploying, updating and maintaining firmware on Dasharo supported devices. For example, it can be used to update the firmware on a device or run initial deployment, even when no OS is currently installed.


up_date: 2022-11-27 10:11:01
name: meta-chimeratk
vcs_url: https://github.com/ChimeraTK/meta-chimeratk
vcs_web_url: https://github.com/ChimeraTK/meta-chimeratk
vcs_web_tree_base_url: https://github.com/ChimeraTK/meta-chimeratk/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/ChimeraTK/meta-chimeratk/blob/%branch%/%path%
summary: ChimeraTK, control system and hardware agnostic software stack
description:
  Control system and Hardware Interface with Mapped and Extensible Register-based device Abstraction Tool Kit

  Enables you to talk to different hardware (PCIe, Modbus, ...) and control system softwares (Tango, DOOCS, OPCUA, EPICS) in a consistent and uniform way


up_date: 2022-12-16 21:12:27
name: meta-dart
vcs_url: https://github.com/r3flow/meta-dart.git
vcs_web_url: https://github.com/r3flow/meta-dart
summary: Yocto Layer for Google Dart CLI/Service projects.
description:
  Cross compiling Dart projects and/or able to package the Dart SDK itself to raspberrypi (or any aarch64 target).


up_date: 2023-03-09 12:03:53
name: meta-uvw
vcs_url: https://github.com/stefanofiorentino/meta-uvw.git
vcs_web_url: https://github.com/stefanofiorentino/meta-uvw
summary: A libuv wrapper in modern C++
description:
  Header-only, event based, tiny and easy to use libuv wrapper in modern C++ - now available as also shared/static library!


up_date: 2023-10-03 08:10:04
name: meta-morello
vcs_url: https://git.morello-project.org/morello/meta-morello
summary: Layer for the Arm Morello board.
description:
  meta-morello provides the layer required to build the firmware and a Linux kernel for the Morello System Development Platform.


up_date: 2023-02-24 14:02:14
name: meta-binutils
vcs_url: https://github.com/emagii/meta-binutils.git
vcs_web_url: https://github.com/emagii/meta-binutils
vcs_web_tree_base_url: https://github.com/emagii/meta-binutils?a=tree;f=%path%;hb=refs/heads/%branch%
vcs_web_file_base_url: https://github.com/emagii/meta-binutils?a=blob;f=%path%;hb=refs/heads/%branch%
summary: Extends GNU linker for embedded control
description:
  This layer has bbappends for binutils in 'kirkstone' to extend the ld linker.
  The functions are there to allow adding a header in the linker.

  It adds the following commands.
  ASCII  (size) <string>
  ASCIZ <string>
  CRC32 CRC32
  CRC32 POLY (POLYNOME)(START,END)
  CRC32 POLYI (POLYNOME)(START,END)
  CRC32 TABLE
  CRC64 ECMA
  CRC64 ISO
  CRC64 POLY (POLYNOME)(START,END)
  CRC64 POLYI (POLYNOME)(START,END)
  CRC64 TABLE
  TIMESTAMP
  DEBUG ON
  DEBUG OFF


up_date: 2023-02-20 14:02:52
name: meta-map-sheriffco
vcs_url: https://github.com/emagii/meta-map-sheriffco.git
vcs_web_url: https://github.com/emagii/meta-map-sheriffco
summary: Various small functionality addons to Yocto
description:
  release-notes.bbclass - generate LaTex fragments for generating the PDF
  bbclasses allow creation of different versions of packages.
  * debug version
  * development version
  * release version
  * production version
  Example how to use this.

  license-####.bbclass.
  Simplify adding license info to recipe through
  inherit license-mit
  for MIT license etc.

  component.bbclass.
  Support bulding from a subdirectory of the component directory where your source code resides.

  macaddr: simple utility to retrieve the MAC address.


up_date: 2023-02-27 12:02:44
name: meta-kf6
vcs_url: https://invent.kde.org/packaging/yocto-meta-kf6.git
vcs_web_url: https://invent.kde.org/packaging/yocto-meta-kf6/
vcs_web_tree_base_url: https://invent.kde.org/packaging/yocto-meta-kf6/tree/%branch%/%path%
vcs_web_file_base_url: https://invent.kde.org/packaging/yocto-meta-kf6/blob/%branch%/%path%
summary: KDE Frameworks 6
description:
  The KDE Frameworks 6 consist of a set of Qt add-on modules extending and improving Qt. Developed by and for the KDE project, but in no way tied to the KDE Plasma desktop.


up_date: 2023-02-28 16:02:35
name: meta-doom
vcs_url: https://github.com/JPEWdev/meta-doom.git
vcs_web_url: https://github.com/JPEWdev/meta-doom
vcs_web_tree_base_url: https://github.com/JPEWdev/meta-doom/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/JPEWdev/meta-doom/blob/%branch%/%path%
summary: Run Doom based games
description:
  Provides recipes to build zdoom (https://zdoom.org/) as well as recipes to provided .wad files for some doom games


up_date: 2023-03-09 17:03:01
name: meta-conan
vcs_url: https://github.com/conan-io/meta-conan
vcs_web_url: https://github.com/conan-io/meta-conan
vcs_web_tree_base_url: https://github.com/conan-io/meta-conan/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/conan-io/meta-conan/blob/%branch%/%path%
summary: Conan Package Manager client
description:
  This layer collects recipes required to use the Conan Package Manager client in the Yocto builds. With this layer you can write simple Bitbake recipes to retrieve and deploy Conan packages from an Artifactory repository.


up_date: 2023-06-15 09:06:28
name: meta-loongarch
vcs_url: https://github.com/loongarch64/meta-loongarch.git
vcs_web_url: https://github.com/loongarch64/meta-loongarch
vcs_web_file_base_url: https://github.com/loongarch64/meta-loongarch.
summary: This a BSP layer for loongarch machine
description:
  meta-loongarch is a Yocto BSP layer or the LoongArch architecture. Although there is partial upstream support for the LoongArch architecture in the OE (OpenEmbedded) project, but there are still some packages that do not natively support LoongArch.Use this layer, we can build an operating system for the LoongArch architecture that can be run on qemu-loongarch64 machines, as well as the corresponding software development kit (SDK).


up_date: 2023-06-28 14:06:28
name: meta-slint
vcs_url: https://github.com/slint-ui/meta-slint
vcs_web_url: https://github.com/slint-ui/meta-slint
summary: Recipes for the Slint UI Toolkit
description:
  Slint is a declarative GUI toolkit to build native user interfaces for applications that are written in Rust, C++, or JavaScript.

  The meta-slint layer provides recipes for building Slint's C++ library, as well as Slint's demos for use in Yocto based images. If you want to use Slint with Rust, you can use the slint crate from crates.io directly.

  On Linux, Slint uses Wayland or X11.


up_date: 2023-06-29 09:06:26
name: meta-raspberrypi-baremetal
vcs_url: https://github.com/ahcbb6/meta-raspberrypi-baremetal.git
vcs_web_url: https://github.com/ahcbb6/meta-raspberrypi-baremetal
summary:
  Yocto Project/OpenEmbedded compatible layer to build Baremetal applications for the Raspberry Pi Pico boards.

description:
  This layer provides the functionality to OpenEmbedded of building your own newlib toolchain for ARM Cortex M0+ processors and use it to create applications compatible with the Raspberry Pi Pico boards (RP2040 microcontroller).


up_date: 2023-07-09 08:07:53
name: meta-zbd
vcs_url: https://gitlab.com/sudipm/meta-zbd.git
vcs_web_url: https://gitlab.com/sudipm/meta-zbd
vcs_web_tree_base_url: https://gitlab.com/sudipm/meta-zbd/tree/%branch%/%path%
vcs_web_file_base_url: https://gitlab.com/sudipm/meta-zbd/blob/%branch%/%path%
summary: Library to manipulate zoned block devices
description:
  libzbd uses the kernel provided zoned block device interface based on the
  ioctl() system call. It provides functions for discovering and managing the
  state of zones of zoned block devices. Read and write accesses to the devices
  can be done using standard standard I/O system calls.


up_date: 2023-08-05 19:08:14
name: meta-lmp-base
vcs_url: https://github.com/foundriesio/meta-lmp
vcs_web_url: https://github.com/foundriesio/meta-lmp
summary: Linux microPlatform OpenEmbedded/Yocto Project base distribution
description:
  The Foundries.io Linux microPlatform is an extensible software and hardware platform that makes it easier to develop, secure, and maintain Internet-connected Linux-based embedded devices.

  The Linux microPlatform is based on OpenEmbedded / Yocto Project, and adds a select set of board support package layers to enable popular development boards.

  This meta layer contains the base distribution definition and core recipes.


up_date: 2023-09-11 07:09:37
name: meta-pocketbeagle
vcs_url: https://github.com/twoerner/meta-pocketbeagle
summary: OpenEmbedded BSP layer for the Beagleboard.org's PocketBeagle
description:
  OpenEmbedded BSP layer for the Beagleboard.org's PocketBeagle by Querty Embedded Design (http://www.qwertyembedded.com/).


up_date: 2023-09-29 02:09:26
name: meta-firefox
vcs_url: https://github.com/OSSystems/meta-browser
vcs_web_url: https://github.com/OSSystems/meta-browser
vcs_web_tree_base_url: https://github.com/OSSystems/meta-browser/tree/master/meta-firefox
vcs_web_file_base_url: https://github.com/OSSystems/meta-browser/tree/master/meta-firefox
summary: OpenEmbedded/Yocto layer for Firefox Browser
description:
  This layer provides web gecko based browser e.g. firefox recipes for use with OpenEmbedded and/or Yocto.


up_date: 2023-09-29 09:09:52
name: meta-morello-toolchain
vcs_url: https://git.morello-project.org/morello/meta-morello
summary: Layer for the Arm Morello board.
description:
  This layer contains recipes for compilers (Morello LLVM and GCC) but also the C libraries required for the Morello System Development Platform.


up_date: 2023-09-30 20:09:12
name: meta-argo
vcs_url: https://github.com/dozylynx/meta-argo
vcs_web_url: https://github.com/dozylynx/meta-argo
summary: Hypervisor-Mediated data eXchange: Argo interdomain communication
description:
  This layer enables Argo interdomain communication software.

  Components for this are currently in the Xen hypervisor, the Linux kernel, Linux userspace software and the Xen Test Framework.

  For references on Argo, please see:
  * https://static.sched.com/hosted_files/xensummit19/92/Argo%20and%20HMX%20-%20OpenXT%20-%20Christopher%20Clark%20-%20Xen%20Summit%202019.pdf
  * https://xenbits.xen.org/docs/4.17-testing/designs/argo.html
  * https://openxt.atlassian.net/wiki/spaces/DC/pages/1770422298/HMX+Hypervisor-Mediated+data+eXchange
  * https://wiki.xenproject.org/wiki/Argo:_Hypervisor-Mediated_Exchange_(HMX)_for_Xen
  * https://www.youtube.com/watch?v=cnC0Tg3jqJQ


up_date: 2023-10-04 08:10:29
name: meta-qbee
vcs_url: https://github.com/qbee-io/meta-qbee
vcs_web_url: https://github.com/qbee-io/meta-qbee
summary: Qbee IoT device management agent
description:
  qbee.io is a device management platform for which the qbee-agent is the workhorse. Its small resource footprint makes it suitable for IoT devices and it runs on any Linux providing configuration management, system metrics and inventory, remote access and more.

  This meta layer integrates the qbee-agent with Yocto builds and enables automatic registration with the qbee.io cloud based backend.

  For more information on the qbee.io platform, please refer to the following website https://qbee.io


up_date: 2023-10-13 16:10:51
name: meta-xilinx-core
vcs_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
summary: Enables AMD Xilinx hardware devices
description:
  This layer enables AMD Xilinx hardware devices metadata such as tune files,
  generic and soc variant machine configurations, boot firmware components, kernel,
  multimedia, graphics, xrt etc.


up_date: 2023-10-13 16:10:33
name: meta-xilinx-bsp
vcs_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
summary: Enables AMD Xilinx MicroBlaze, Zynq, ZynqMP and Versal device evaluation boards
description:
  This layer enables AMD Xilinx MicroBlaze, Zynq, ZynqMP and Versal device
  evaluation boards and provides related metadata.


up_date: 2023-10-13 16:10:37
name: meta-xilinx-vendor
vcs_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
summary: Enables third party vendor boards
description:
  This layer enables third party vendor boards for AMD Xilinx MicroBlaze, Zynq,
  ZynqMP and Versal devices and provides related metadata.


up_date: 2023-10-13 17:10:17
name: meta-xilinx-contrib
vcs_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_url: https://git.yoctoproject.org/meta-xilinx
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-xilinx/tree/%path%?h=%branch%
summary: 3rd party/Open Source BSP contribution layer
description:
  This layer is a contribution layer enables AMD Xilinx MicroBlaze, Zynq, ZynqMP
  and Versal devices and provides related metadata.
  Any patches from open source contributors for vendor board can be added here.


up_date: 2023-10-20 17:10:32
name: meta-netboot
vcs_url: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
vcs_web_url: https://git.automotivelinux.org/AGL/meta-agl/
summary:
  This layer contains some recipes and configuration adjustments to allow network boot through NBD (network boot device).

description:
  This layer creates a new supplementary initrd image which can be downloaded through TFTP with the kernel.
  At boot time, the init script will try to mount the rootfs based on the following kernel command line parameters:

  * nbd.server: IP address to reach the NBD server
  * nbd.dev: nbd device to use (default: /dev/nbd0)
  * nbd.debug: activate debug mode (init script is then interruptible)

  For nbd v2:

  * nbd.port: TCP port on which server is listening (default: 10809)

  For nbd v3:

  * nbd.namev3: The name of the image served by nbd-server.


  The layer meta-netboot contains recipes for the following components:
  * busybox: activate the built-in NBD client
  * initramfs-netboot: contains the init script started by the kernel: basically, this script mounts the real root filesystem, then pivot_root on it and finally exec systemd.
  * initramfs-netboot-image: image to specify for building the initrd

  To enable the build of the netboot initrd and ext4 rootfs, add the following line in conf/local.conf:

  INHERIT += "netboot"


up_date: 2025-02-19 10:02:18
name: meta-toradex-ti
vcs_url: https://git.toradex.com/meta-toradex-ti.git
vcs_web_url: https://git.toradex.com/cgit/meta-toradex-ti.git/
vcs_web_tree_base_url: https://git.toradex.com/cgit/meta-toradex-ti.git/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.toradex.com/cgit/meta-toradex-ti.git/tree/%path%?h=%branch%
summary: BSP for Toradex Computer on Modules based on Ti SoCs
description:
  This layer provides support for ARM based Toradex computer on modules (COM) featuring TI AM62 SoC for use with OpenEmbedded and/or Yocto.


up_date: 2023-11-14 10:11:16
name: meta-toradex-distro
vcs_url: https://git.toradex.com/meta-toradex-distro.git
vcs_web_url: https://git.toradex.com/cgit/meta-toradex-distro.git/
vcs_web_tree_base_url: https://git.toradex.com/cgit/meta-toradex-distro.git/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.toradex.com/cgit/meta-toradex-distro.git/tree/%path%?h=%branch%
summary: Distribution layer providing support for Toradex System on Modules
description:
  The layer provides various distros targeting Toradex System on Modules.
  The distros chooses if kernel and bootfw is based on SoC vendor provided downstream code bases or on upstream mainline/stable code bases and if X11 or wayland is used.


up_date: 2023-12-12 17:12:46
name: meta-arago-test
vcs_url: https://git.yoctoproject.org/meta-arago
vcs_web_url: https://git.yoctoproject.org/meta-arago/
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-arago/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-arago/tree/%path%?h=%branch%
summary: Package group for ti-test
description:
  This is layer provides a package group named ti-test and all of the additional test recipes that it requires.


up_date: 2023-12-20 20:12:45
name: meta-amd-bsp
vcs_url: https://git.yoctoproject.org/meta-amd
vcs_web_url: https://git.yoctoproject.org/meta-amd
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-amd/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-amd/tree/%path%?h=%branch%
summary: Support for AMD-based platforms (x86)
description:
  This layer contains metadata that is appropriate for all the supported
  AMD-based platforms.

  Including AMD EPYC and AMD Ryzen, see README.


up_date: 2024-01-17 13:01:17
name: meta-parallel-php
vcs_url: https://github.com/zboszor/meta-parallel-php.git
vcs_web_url: https://github.com/zboszor/meta-parallel-php
vcs_web_tree_base_url: https://github.com/zboszor/meta-parallel-php/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/zboszor/meta-parallel-php/blob/%branch%/%path%
summary: Parallel installable PHP versions and modules
description:
  Parallel installable PHP versions and modules

  This layer attempts to follow https://rpms.remirepo.net

  Branches main, nanbield, mickledore, langdale and kirkstone support PHP 7.4 and up.

  The honister branch supports PHP 7.0 and up.


up_date: 2024-02-19 13:02:18
name: meta-adacore
vcs_url: https://github.com/under-view/meta-adacore
vcs_web_url: https://github.com/under-view/meta-adacore
vcs_web_tree_base_url: https://github.com/under-view/meta-adacore?a=tree;f=%path%;hb=refs/heads/%branch%
vcs_web_file_base_url: https://github.com/under-view/meta-adacore?a=blob;f=%path%;hb=refs/heads/%branch%
summary: Layer to support building ada code
description:
  Pulls in open source GPL licensed gnat compiler to build a gnat compiler suitable for cross compilation.


up_date: 2024-03-01 14:03:59
name: meta-snapd
vcs_url: https://github.com/snapcore/meta-snapd
vcs_web_url: https://github.com/snapcore/meta-snapd
vcs_web_tree_base_url: https://github.com/snapcore/meta-snapd/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/snapcore/meta-snapd/blob/%branch%/%path%
summary: Yocto meta-layer for snapd, use snaps in Yocto
description:
  The meta-snapd layer allows building snapd into a Yocto distribution which facilitates maintaining and using applications from the snap ecosystem as the application layer of an IoT system.


up_date: 2024-03-07 22:03:31
name: meta-efibootguard
vcs_url: https://github.com/siemens/meta-efibootguard
summary: A meta-layer for integration of efibootguard into a yocto project.
description:
  A bootloader based on UEFI.

  Provides the following functionality:

  Arm a hardware watchdog prior to loading an OS
  Provides a simple update mechanism with fail-safe algorithm
  In addition, this project provides a UEFI stub and generator tool to create unified kernel images consisting of kernel, command line and, optionally, initrd and device trees.


up_date: 2024-04-13 15:04:42
name: meta-python-ai
vcs_url: https://github.com/zboszor/meta-python-ai.git
vcs_web_url: https://github.com/zboszor/meta-python-ai
summary: AI related python modules
description:
  This Yocto layer contains artificial intelligence / machine learning related Python module recipes.

  This Yocto layer is also the continuation and extension of the recently archived/discontinued meta-scipy and meta-scikit-learn layers.

  It supports Yocto 4.2 Mickledore and newer releases.


up_date: 2024-08-22 23:08:18
name: meta-toradex-torizon
vcs_url: https://github.com/torizon/meta-toradex-torizon.git
vcs_web_url: https://github.com/torizon/meta-toradex-torizon
summary: Distribution layer providing the Torizon OS
description:
  This layer provides the Torizon OS distribution. It is meant for users of the Torizon IoT platform, and also for standalone use.

  Among the features, a container engine, a secure OTA client, and device monitoring are included by default.


up_date: 2024-08-18 22:08:12
name: meta-complementary
vcs_url: https://github.com/andrerclaudio/yocto-digest
summary: Tools to better understand your board.
description:
  This meta layer is intended to bring widely used tools in the x86 context to the world of Linux boards.


up_date: 2024-08-18 22:08:30
name: meta-clang-revival
vcs_url: https://github.com/zboszor/meta-clang-revival
vcs_web_url: https://github.com/zboszor/meta-clang-revival
summary: Bring older CLANG versions back to life for Yocto
description:
  This Yocto layer contains some older CLANG versions revived from meta-clang.

  meta-clang only maintains a single version of CLANG, which is always the latest version matching the LLVM version in openembedded-core.

  The problem with only keeping a single LLVM or CLANG version is that crucial projects are slow to update their LLVM version support. This layer allows building such projects.


up_date: 2024-08-18 22:08:11
name: meta-toradex-security
vcs_url: https://github.com/toradex/meta-toradex-security.git
vcs_web_url: https://github.com/toradex/meta-toradex-security
vcs_web_tree_base_url: https://github.com/toradex/meta-toradex-security/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/toradex/meta-toradex-security/blob/%branch%/%path%
summary: Layer to enable security features on Toradex SoMs
description:
  This layer contains metadata to enable security features when building a Linux system for Toradex SoMs. Supported features include secure boot, data-at-rest encryption and OP-TEE.


up_date: 2024-08-28 02:08:40
name: lts-u-boot-mixin
vcs_url: https://git.yoctoproject.org/meta-lts-mixins
vcs_web_url: https://git.yoctoproject.org/meta-lts-mixins/log/?h=scarthgap/u-boot
summary: "Mixin" layer for adding current u-boot into the Yocto Project LTS.
description:
  At the time Scarthgap was released in April 2024 it included u-boot 2024.01,
  and officially Scarthgap supports only that. This thin special-purpose
  mixin layer is meant to provide a current u-boot for Scarthgap
  by extending or backporting the appropriate recipes from the master branch of
  openembedded-core.


up_date: 2024-09-19 19:09:40
name: meta-quantum-safe
vcs_url: https://github.com/DynamicDevices/meta-quantum-safe
summary: A Yocto layer to start exploring the world of quantum safe cryptography
description:
  We currently have support for the Open Quantum Safe project library implementation

  The intent is to next add OpenSSL and MQTT support in the near future to enable simple examples for testing quantum-safe algorithms end-to-end across the internet.

  libOQS builds and runs on our Jaguar i.MX8M Mini based board and some performance statistics can be seen from the tool speed_sig.

  It should also build and run on other target boards supported by Yocto. If you use this layer please do feed back your results to us in order to add supported platforms to this README and hopefully generate some comparative performance figures.


up_date: 2024-09-27 16:09:46
name: meta-fwup
vcs_url: https://github.com/fwup-home/meta-fwup/
vcs_web_url: https://github.com/fwup-home/meta-fwup
vcs_web_tree_base_url: https://github.com/fwup-home/meta-fwup/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/fwup-home/meta-fwup/blob/%branch%/%path%
summary: Yocto meta layer for using fwup
description:
  This is a Yocto meta layer for building fwup into Yocto projects. fwup is a configurable image-based software update utility for embedded Linux-based systems. It primarily supports software upgrade strategies that update entire root filesystem images at once.


up_date: 2024-11-20 21:11:44
name: meta-rz-bsp
vcs_url: https://github.com/renesas-rz/rz-community-bsp.git
vcs_web_url: https://github.com/renesas-rz/rz-community-bsp
vcs_web_tree_base_url: https://github.com/renesas-rz/rz-community-bsp/tree/%branch%/
vcs_web_file_base_url: https://github.com/renesas-rz/rz-community-bsp/blob/%branch%/
summary: Simple BSP for Renesas RZ reference platforms
description:
  This repository provides a basic BSP that will build a simple, usable images for Renesas RZ reference platforms, following the best practices described by the Yocto project.

  It is designed to allow users to use the latest upstream open source projects and is provided as-is with no official support from Renesas.


up_date: 2025-01-16 14:01:31
name: meta-qemu-bsp
vcs_url: https://github.com/meta-erlang/meta-qemu-bsp
vcs_web_url: https://github.com/meta-erlang/meta-qemu-bsp
vcs_web_tree_base_url: https://github.com/meta-erlang/meta-qemu-bsp
vcs_web_file_base_url: https://github.com/meta-erlang/meta-qemu-bsp
summary: Yocto layer with additional QEMU machines
description:
  This Yocto layer provides additional qemu machines in additional to the default QEMU machines provided by the Yocto Project. The main idea is to add machines based on QEMU with additional support like using u-boot/grub as bootloader.


up_date: 2025-01-08 15:01:54
name: meta-chirpstack
vcs_url: https://github.com/FreseEnzo/meta-chirpstack
vcs_web_url: https://github.com/FreseEnzo/meta-chirpstack
vcs_web_tree_base_url: https://github.com/FreseEnzo/meta-chirpstack/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/FreseEnzo/meta-chirpstack/blob/%branch%/%path%
summary: OpenEmbedded/Yocto layer for Chirpstack 4.9.0 + Chirpstack-Bridge 4.0.9+ Posgresql
description:
  Meta-ChirpStack is a Yocto layer designed to seamlessly incorporate the ChirpStack LoRaWAN Network Server and Gateway Bridge into Yocto-based embedded projects. This layer provides prebuilt binaries, systemd service configurations, and PostgreSQL initialization scripts, simplifying the deployment and management of ChirpStack components. By leveraging Meta-ChirpStack, developers can effortlessly establish robust and scalable LoRaWAN networks, ensuring efficient communication between IoT devices and network infrastructure. The layer adheres to Yocto Project standards, promoting compatibility and ease of integration within diverse build environments.


up_date: 2025-01-08 15:01:22
name: meta-pqc
vcs_url: https://github.com/embetrix/meta-pqc
vcs_web_url: https://github.com/embetrix/meta-pqc
vcs_web_tree_base_url: https://github.com/embetrix/meta-pqc/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/embetrix/meta-pqc/blob/%branch%/%path%
summary: Post-Quantum Cryptography
description:
  OpenEmbedded/Yocto layer dedicated to Post-Quantum Cryptography, providing integration and testing of quantum-safe cryptographic algorithms for embedded systems.


up_date: 2025-04-16 06:04:28
name: lts-rust-mixin
vcs_url: https://git.yoctoproject.org/meta-lts-mixins
vcs_web_url: https://git.yoctoproject.org/meta-lts-mixins
vcs_web_tree_base_url: https://git.yoctoproject.org/meta-lts-mixins/tree/%path%?h=%branch%
vcs_web_file_base_url: https://git.yoctoproject.org/meta-lts-mixins/tree/%path%?h=%branch%
summary: Rust mixin layer for Yocto Project kirkstone LTS release
description:
  A "mixin" layer for adding current Rust toolchain into the Yocto Project LTS.
  At the time Kirkstone was released in May 2022 it included Rust 1.59.0, and
  officially Kirkstone supports only that. This thin special-purpose mixin
  layer is meant to provide a current Rust toolchain for Kirkstone by
  backporting the appropriate recipes from the master branch of
  openembedded-core.


up_date: 2025-04-23 12:04:26
name: meta-8dev
vcs_url: https://github.com/8devices/meta-8dev.git
vcs_web_url: https://github.com/8devices/meta-8dev
vcs_web_tree_base_url: https://github.com/8devices/meta-8dev/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/8devices/meta-8dev/blob/%branch%/%path%
summary: 8devices board support
description:
  The official OpenEmbedded/Yocto BSP layer for 8devices products. This layer provides machine configuration and packages extensions to enable software build for 8devices modules and boards.

  For more information about the 8devices modules see:
  https://www.8devices.com/products


up_date: 2025-06-18 14:06:38
name: meta-galapagos
vcs_url: https://github.com/The-Good-Penguin/tgp-meta-galapagos.git
vcs_web_url: https://github.com/The-Good-Penguin/tgp-meta-galapagos
vcs_web_tree_base_url: https://github.com/The-Good-Penguin/tgp-meta-galapagos/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/The-Good-Penguin/tgp-meta-galapagos/blob/%branch%/%path%
summary: A layer providing access to The Good Penguin's Galapagos CVE scanning service
description:
  Galapagos is a CVE analysis service provided by The Good Penguin. Artifacts from a Yocto build such as data from Yocto's cve-scan can be uploaded to the service, in return the service will analyse the data and email a report with recommended mitigation steps.


up_date: 2025-07-08 15:07:51
name: meta-freescale-distro
vcs_url: https://github.com/Freescale/meta-freescale-distro.git
vcs_web_url: https://github.com/Freescale/meta-freescale-distro
vcs_web_tree_base_url: https://github.com/Freescale/meta-freescale-distro/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/Freescale/meta-freescale-distro/blob/%branch%/%path%
summary: OpenEmbedded/Yocto layer for NXP's Distribution images
description:
  This layer provides support for NXP's Demonstration images for
  use with OpenEmbedded and/or Yocto NXP's BSP layer.


up_date: 2025-07-17 16:07:53
name: meta-rwt-oxygen
vcs_url: https://github.com/redwiretechnologies/meta-rwt-oxygen
vcs_web_url: https://github.com/redwiretechnologies/meta-rwt-oxygen/
vcs_web_tree_base_url: https://github.com/redwiretechnologies/meta-rwt-oxygen/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/redwiretechnologies/meta-rwt-oxygen/blob/%branch%/%path%
summary: BSP layer for Red Wire Technologies, Oxygen SDR
description:
  BSP layer for support for Red Wire Technologies' embedded Oxygen SDR.  This is is reference BSP with initiations to follow LTS releases.


up_date: 2025-08-25 12:08:55
name: meta-dynamicdevices
vcs_url: https://github.com/DynamicDevices/meta-dynamicdevices.git
vcs_web_url: https://github.com/DynamicDevices/meta-dynamicdevices
vcs_web_tree_base_url: https://github.com/DynamicDevices/meta-dynamicdevices/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/DynamicDevices/meta-dynamicdevices/blob/%branch%/%path%
summary:
  Professional BSP layer for Dynamic Devices Edge Computing platforms with i.MX8MM/i.MX93 support, AI audio processing, E-Ink displays, and power management

description:
  Overview

  A comprehensive Board Support Package (BSP) layer providing hardware support for Dynamic Devices Edge Computing platform family. 

  This layer delivers production-ready support for advanced embedded systems featuring NXP i.MX8M Mini and NXP i.MX93 processors.

  Hardware Platforms Supported

  • Edge AI Board (imx8mm-jaguar-sentai) - AI audio processing with TAS2563 codec
  • Edge EInk Board (imx93-jaguar-eink) - Low-power E-Ink display systems  
  • Edge EV Board (imx8mm-jaguar-inst) - Environmental sensing and monitoring
  • Edge Gateway (imx8mm-jaguar-phasora) - Wireless connectivity hub
  • Edge Mobile (imx8mm-jaguar-handheld) - Portable computing platform

  Key Features

  • Complete device tree support for all board variants
  • Advanced audio processing with DSP firmware integration
  • Power management for battery-operated devices
  • Wireless connectivity (WiFi, Bluetooth, cellular)
  • Environmental sensors and radar presence detection
  • E-Ink display drivers and power optimization
  • USB Power Delivery (STUSB4500) integration
  • Secure boot and OTA update support via Foundries.io LMP

  Software Integration

  • Native Foundries.io Linux microPlatform (LMP) integration
  • Container-ready with Docker support
  • Professional CI/CD pipeline with automated testing
  • Comprehensive security features and CVE monitoring
  • SBOM generation for supply chain transparency

  Target Applications

  Industrial IoT, edge AI processing, environmental monitoring, smart displays, wireless gateways, and battery-powered embedded systems requiring professional-grade reliability and security.

  Compliance & Quality

  • Yocto Project Compatible layer design (to be validated)
  • Comprehensive QA validation and automated testing
  • Professional maintenance and support by Dynamic Devices Ltd
  • Open source with commercial licensing options available


up_date: 2025-09-12 09:09:06
name: meta-vpp
vcs_url: https://github.com/skbuff-ru/meta-vpp.git
vcs_web_url: https://github.com/skbuff-ru/meta-vpp/
vcs_web_tree_base_url: https://github.com/skbuff-ru/meta-vpp/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/skbuff-ru/meta-vpp/blob/%branch%/%path%
summary: Yocto layer for building Vector Packet Processing (VPP) and its Python API
description:
  This layer provides recipes to build VPP (FD.io) with DPDK support, including the vppctl CLI, plugins, and Python bindings. Designed for high-performance networking applications in embedded and NFV environments.


up_date: 2025-10-14 14:10:34
name: meta-openjdk-temurin
vcs_url: https://github.com/lucimber/meta-openjdk-temurin.git
vcs_web_url: https://github.com/lucimber/meta-openjdk-temurin
vcs_web_tree_base_url: https://github.com/lucimber/meta-openjdk-temurin/tree/%branch%/%path%
vcs_web_file_base_url: https://github.com/lucimber/meta-openjdk-temurin/blob/%branch%/%path%
summary: Eclipse Temurin Java JVM Support
description:
  This is a software layer for Java VMs, for use with OpenEmbedded and Yocto Project build systems. The binaries are provided by the Eclipse Temurin Project.
  (from Github project page)


