Manifests are provided to build under various versions of OpenEmbedded. The host system should meet the requirements for the corresponding OpenEmbedded release. The recommended manifest oe40.xml builds under OE 4.0 ("kirkstone"), for which the host system requirements are documented in the Yocto Project Reference Manual.
sudo apt-get -y install build-essential chrpath cpio debianutils diffstat file \
gawk gcc git iputils-ping libacl1 liblz4-tool locales python3 python3-git \
python3-jinja2 python3-pexpect python3-pip python3-subunit socat texinfo \
unzip wget xz-utils zstd
sudo locale-gen en_US.UTF-8The host should have the Google "repo" tool installed. The older repo-1 branch is currently recommended.
curl https://storage.googleapis.com/git-repo-downloads/repo-1 > ~/bin/repo
chmod a+x ~/bin/repoEach manifest contains its own specific setup and build instructions. For example, to build using OE 4.0 see the instructions in the comments at the end of the oe40.xml manifest:
repo init --repo-branch=repo-1 -u https://github.com/lgirdk/manifests-ofw.git -b ofw-2509.5 -m oe40.xml
repo sync --no-clone-bundle --current-branch
MACHINE="exm-qemuarm" source ./meta-mng/setup-environment
bitbake ofwEach manifest also has -open variant (e.g. oe40-open.xml) which fetches only open source components and so can be used without access to any private repos. Builds created with the -open manifests will not include closed source components such as the WebUI.