%poky; ] > Welcome to the Yocto Project Reference Manual! This manual provides reference information for the current release of the Yocto Project, and is most effectively used after you have an understanding of the basics of the Yocto Project. The manual is neither meant to be read as a starting point to the Yocto Project, nor read from start to finish. Rather, use this manual to find variable definitions, class descriptions, and so forth as needed during the course of using the Yocto Project. For introductory information on the Yocto Project, see the Yocto Project Website and the "Yocto Project Development Environment" chapter in the Yocto Project Overview and Concepts Manual. If you want to use the Yocto Project to quickly build an image without having to understand concepts, work through the Yocto Project Quick Build document. You can find "how-to" information in the Yocto Project Development Tasks Manual. You can find Yocto Project overview and conceptual information in the Yocto Project Overview and Concepts Manual. For more information about the Yocto Project Documentation set, see the "Links and Related Documentation" section.

Currently, the Yocto Project is supported on the following distributions: Yocto Project releases are tested against the stable Linux distributions in the following list. The Yocto Project should work on other distributions but validation is not performed against them. In particular, the Yocto Project does not support and currently has no plans to support rolling-releases or development distributions due to their constantly changing nature. We welcome patches and bug reports, but keep in mind that our priority is on the supported platforms listed below. You may use Windows Subsystem For Linux v2 to set up a build host using Windows 10, but validation is not performed against build hosts using WSLv2. The Yocto Project is not compatible with WSLv1, it is compatible but not officially supported nor validated with WSLv2, if you still decide to use WSL please upgrade to WSLv2. If you encounter problems, please go to Yocto Project Bugzilla and submit a bug. We are interested in hearing about your experience. For information on how to submit a bug, see the Yocto Project Bugzilla wiki page and the "Submitting a Defect Against the Yocto Project" section in the Yocto Project Development Tasks Manual. Ubuntu 16.04 (LTS) Ubuntu 18.04 (LTS) Ubuntu 19.04 Fedora 28 Fedora 29 Fedora 30 CentOS 7.x Debian GNU/Linux 8.x (Jessie) Debian GNU/Linux 9.x (Stretch) Debian GNU/Linux 10.x (Buster) OpenSUSE Leap 15.1 While the Yocto Project Team attempts to ensure all Yocto Project releases are one hundred percent compatible with each officially supported Linux distribution, instances might exist where you encounter a problem while using the Yocto Project on a specific distribution.

The list of packages you need on the host development system can be large when covering all build scenarios using the Yocto Project. This section describes required packages according to Linux distribution and function.

The following list shows the required packages by function given a supported Ubuntu or Debian Linux distribution: If your build system has the oss4-dev package installed, you might experience QEMU build failures due to the package installing its own custom /usr/include/linux/soundcard.h on the Debian system. If you run into this situation, either of the following solutions exist: $ sudo apt-get build-dep qemu $ sudo apt-get remove oss4-dev For Debian-8, python3-git and pylint3 are no longer available via apt-get. $ sudo pip3 install GitPython pylint==1.9.5 Essentials: Packages needed to build an image on a headless system: $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo apt-get install make xsltproc docbook-utils fop dblatex xmlto

The following list shows the required packages by function given a supported Fedora Linux distribution: Essentials: Packages needed to build an image for a headless system: $ sudo dnf install &FEDORA_HOST_PACKAGES_ESSENTIAL; Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo dnf install docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt dblatex xmlto

The following list shows the required packages by function given a supported openSUSE Linux distribution: Essentials: Packages needed to build an image for a headless system: $ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL; Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo zypper install dblatex xmlto

The following list shows the required packages by function given a supported CentOS-7 Linux distribution: Essentials: Packages needed to build an image for a headless system: $ sudo yum install &CENTOS7_HOST_PACKAGES_ESSENTIAL; Extra Packages for Enterprise Linux (i.e. epel-release) is a collection of packages from Fedora built on RHEL/CentOS for easy installation of packages not included in enterprise Linux by default. You need to install these packages separately. The makecache command consumes additional Metadata from epel-release. Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo yum install docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt dblatex xmlto

The following list shows the required packages by function given a supported CentOS-8 Linux distribution: Essentials: Packages needed to build an image for a headless system: $ sudo dnf install &CENTOS8_HOST_PACKAGES_ESSENTIAL; Extra Packages for Enterprise Linux (i.e. epel-release) is a collection of packages from Fedora built on RHEL/CentOS for easy installation of packages not included in enterprise Linux by default. You need to install these packages separately. The PowerTools repo provides additional packages such as rpcgen and texinfo. The makecache command consumes additional Metadata from epel-release. Documentation: Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo dnf install docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt dblatex xmlto

In order to use the build system, your host development system must meet the following version requirements for Git, tar, and Python: Git 1.8.3.1 or greater tar 1.28 or greater Python 3.5.0 or greater If your host development system does not meet all these requirements, you can resolve this by installing a buildtools tarball that contains these tools. You can get the tarball one of two ways: download a pre-built tarball or use BitBake to build the tarball. In addition, your host development system must meet the following version requirement for gcc: gcc 5.0 or greater If your host development system does not meet this requirement, you can resolve this by installing a buildtools-extended tarball that contains additional tools, the equivalent of buildtools-essential.

The install-buildtools script is the easiest of the three methods by which you can get these tools. It downloads a pre-built buildtools installer and automatically installs the tools for you: Execute the install-buildtools script. Here is an example: $ cd poky $ script/install-buildtools --without-extended-buildtools \ --base-url &YOCTO_DL_URL;/releases/yocto \ --release yocto-&DISTRO; \ --installer-version &DISTRO; During execution, the buildtools tarball will be downloaded, the checksum of the download will be verified, the installer will be run for you, and some basic checks will be run to to make sure the installation is functional. To avoid the need of sudo privileges, the install-buildtools script will by default tell the installer to install in: /path/to/poky/buildtools If your host development system needs the additional tools provided in the buildtools-extended tarball, you can instead execute the install-buildtools script with the default parameters: $ cd poky $ script/install-buildtools Source the tools environment setup script by using a command like the following: $ source /path/to/poky/buildtools/environment-setup-x86_64-pokysdk-linux Of course, you need to supply your installation directory and be sure to use the right file (i.e. i586 or x86_64). After you have sourced the setup script, the tools are added to PATH and any other environment variables required to run the tools are initialized. The results are working versions versions of Git, tar, Python and chrpath. And in the case of the buildtools-extended tarball, additional working versions of tools including gcc, make and the other tools included in packagegroup-core-buildessential.

Downloading and running a pre-built buildtools installer is the easiest of the two methods by which you can get these tools: Locate and download the *.sh at . Execute the installation script. Here is an example for the traditional installer: $ sh ~/Downloads/x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh Here is an example for the extended installer: $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh During execution, a prompt appears that allows you to choose the installation directory. For example, you could choose the following: /home/your-username/buildtools Source the tools environment setup script by using a command like the following: $ source /home/your_username/buildtools/environment-setup-i586-poky-linux Of course, you need to supply your installation directory and be sure to use the right file (i.e. i585 or x86-64). After you have sourced the setup script, the tools are added to PATH and any other environment variables required to run the tools are initialized. The results are working versions versions of Git, tar, Python and chrpath. And in the case of the buildtools-extended tarball, additional working versions of tools including gcc, make and the other tools included in packagegroup-core-buildessential.

Building and running your own buildtools installer applies only when you have a build host that can already run BitBake. In this case, you use that machine to build the .sh file and then take steps to transfer and run it on a machine that does not meet the minimal Git, tar, and Python (or gcc) requirements. Here are the steps to take to build and run your own buildtools installer: On the machine that is able to run BitBake, be sure you have set up your build environment with the setup script (&OE_INIT_FILE;). Run the BitBake command to build the tarball: $ bitbake buildtools-tarball or run the BitBake command to build the extended tarball: $ bitbake buildtools-extended-tarball The SDKMACHINE variable in your local.conf file determines whether you build tools for a 32-bit or 64-bit system. Once the build completes, you can find the .sh file that installs the tools in the tmp/deploy/sdk subdirectory of the Build Directory. The installer file has the string "buildtools" (or "buildtools-extended") in the name. Transfer the .sh file from the build host to the machine that does not meet the Git, tar, or Python (or gcc) requirements. On the machine that does not meet the requirements, run the .sh file to install the tools. Here is an example for the traditional installer: $ sh ~/Downloads/x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh Here is an example for the extended installer: $ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh During execution, a prompt appears that allows you to choose the installation directory. For example, you could choose the following: /home/your_username/buildtools Source the tools environment setup script by using a command like the following: $ source /home/your_username/buildtools/environment-setup-x86_64-poky-linux Of course, you need to supply your installation directory and be sure to use the right file (i.e. i586 or x86_64). After you have sourced the setup script, the tools are added to PATH and any other environment variables required to run the tools are initialized. The results are working versions versions of Git, tar, Python and chrpath. And in the case of the buildtools-extended tarball, additional working versions of tools including gcc, make and the other tools included in packagegroup-core-buildessential.