mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-04-17 22:48:28 +00:00
272f2083d4
Layer priority is the ultimate decider of what recipe is used: if layer A has recipe foo_1 and layer B has recipe foo_2, if layer A's priority is higher than B then foo_1 will be used, even though the version in B is higher, and even if PREFERRED_VERSION_foo is set to 2. This complicates recipes moving between layers, for example when a newer version of a recipe (say, python3-wheel) is taken from a layer with a higher priority (say, meta-python) and moved to a layer with a lower priority (say, oe-core) then it has to be removed before it is added: there is no way to have it in both layers and work correctly. Higher priorities are useful in distribution layers where you may want to override specific recipes without any other fuss. However as all of the layers in meta-oe simply add more recipes in defined areas, there's no need to have a higher layer priority. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
This README file contains information on the contents of the
filesystems layer.
Please see the corresponding sections below for details.
Dependencies
============
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: master
URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe
branch: master
Patches
=======
Please submit any patches against the filesystems layer to the
OpenEmbedded development mailing list (openembedded-devel@lists.openembedded.org)
with '[meta-filesystems]' in the subject.
Layer maintainer: Khem Raj <raj.khem@gmail.com>
When sending single patches, please use something like:
git send-email -1 -M \
--to openembedded-devel@lists.openembedded.org \
--subject-prefix='meta-filesystems][PATCH'
Table of Contents
=================
I. Adding the filesystems layer to your build
II. Misc
I. Adding the filesystems layer to your build
=================================================
In order to use this layer, you need to make the build system aware of
it.
Assuming the filesystems layer exists at the top-level of your
yocto build tree, you can add it to the build system by adding the
location of the filesystems layer to bblayers.conf, along with any
other layers needed. e.g.:
BBLAYERS ?= " \
/path/to/yocto/meta \
/path/to/yocto/meta-oe \
/path/to/yocto/meta-filesystems \
"
II. Misc
========
--- physfs ---
A library to provide abstract access to various archives
--- fuse ---
Filesystem in Userspace (FUSE) is a simple interface for userspace programs
to export a virtual filesystem to the Linux kernel.
--- ifuse ---
A fuse filesystem to access the contents of an iPhone or iPod Touch
--- sshfs-fuse ---
A filesystem client based on the SSH File Transfer Protocol
--- owfs ---
An easy way to use the 1-Wire file system
--- ntfs-3g-ntfsprogs ---
The ntfs-3g is a freely available read/write NTFS driver for Linux and
ntfsprogs includes utilities for doing all required tasks to NTFS partitions.
--- cramfs ---
Builds cramfs filesystems for embedded systems
--- smbnetfs ---
SMBNetFS is a Linux/FreeBSD filesystem that allow you to use samba/microsoft
network in the same manner as the network neighborhood in Microsoft Windows.
--- fuse-exfat ---
A read and write exFAT driver for FUSE
--- exfat-utils ---
Utilities to create, check, label and dump exFAT filesystem
--- f2fs-tools ---
Tools needed for creating and managing f2fs partitions
--- xfsprogs ---
It provides XFS filesystem utilities.