From 73ffb8298b545a1a1fb96bc5952b7365c4c43bfd Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 7 Dec 2012 17:29:51 -0600 Subject: Documentation: poky-ref-manual - Removed all trailing whitespace. (From yocto-docs rev: 564a28c2501034ea7e2eb16afc43dfaf931b6f6f) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/faq.xml | 181 ++- documentation/poky-ref-manual/introduction.xml | 100 +- documentation/poky-ref-manual/migration.xml | 148 +-- documentation/poky-ref-manual/poky-ref-manual.xml | 18 +- documentation/poky-ref-manual/ref-bitbake.xml | 272 ++--- documentation/poky-ref-manual/ref-classes.xml | 346 +++--- documentation/poky-ref-manual/ref-features.xml | 124 +- documentation/poky-ref-manual/ref-images.xml | 66 +- documentation/poky-ref-manual/ref-structure.xml | 260 ++-- documentation/poky-ref-manual/ref-variables.xml | 1292 ++++++++++---------- documentation/poky-ref-manual/ref-varlocality.xml | 8 +- documentation/poky-ref-manual/resources.xml | 18 +- .../poky-ref-manual/technical-details.xml | 434 +++---- documentation/poky-ref-manual/usingpoky.xml | 264 ++-- 14 files changed, 1765 insertions(+), 1766 deletions(-) diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml index 945c7f19af..176573de28 100644 --- a/documentation/poky-ref-manual/faq.xml +++ b/documentation/poky-ref-manual/faq.xml @@ -19,11 +19,11 @@ and BitBake. Thus, the generic term used here for the build system is the "OpenEmbedded build system." - Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with + Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with changes always being merged to OE-Core or BitBake first before being pulled back into Poky. This practice benefits both projects immediately. - For a fuller description of the term "Poky", see the + For a fuller description of the term "Poky", see the poky term in the Yocto Project Development Manual. @@ -47,9 +47,9 @@ - These tarballs are self-contained with all required libraries and should work - on most Linux systems. - To use the tarballs extract them into the root + These tarballs are self-contained with all required libraries and should work + on most Linux systems. + To use the tarballs extract them into the root directory and run the appropriate command: $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH @@ -72,12 +72,12 @@ There are three areas that help with stability; - The Yocto Project team keeps + The Yocto Project team keeps OE-Core small and focused, containing around 830 recipes as opposed to the thousands available in other OpenEmbedded community layers. Keeping it small makes it easy to test and maintain. - The Yocto Project team runs manual and automated tests + The Yocto Project team runs manual and automated tests using a small, fixed set of reference hardware as well as emulated targets. The Yocto Project uses an an autobuilder, @@ -100,7 +100,7 @@ Yocto Project Board Support Package (BSP) Developer's Guide. - Usually, if the board is not completely exotic, adding support in + Usually, if the board is not completely exotic, adding support in the Yocto Project is fairly straightforward. @@ -115,10 +115,10 @@ The software running on the Vernier LabQuest - is built using the OpenEmbedded build system. + is built using the OpenEmbedded build system. See the Vernier LabQuest website for more information. - There are a number of pre-production devices using the OpenEmbedded build system + There are a number of pre-production devices using the OpenEmbedded build system and the Yocto Project team announces them as soon as they are released. @@ -133,8 +133,8 @@ - Because the same set of recipes can be used to create output of various formats, the - output of an OpenEmbedded build depends on how it was started. + Because the same set of recipes can be used to create output of various formats, the + output of an OpenEmbedded build depends on how it was started. Usually, the output is a flashable image ready for the target device. @@ -150,7 +150,7 @@ To add a package, you need to create a BitBake recipe. For information on how to add a package, see the section - "Adding a Package" + "Adding a Package" in the Yocto Project Development Manual. @@ -159,16 +159,16 @@ - Do I have to reflash my entire board with a new Yocto Project image when recompiling + Do I have to reflash my entire board with a new Yocto Project image when recompiling a package? The OpenEmbedded build system can build packages in various formats such as - ipk for opkg, - Debian package (.deb), or RPM. - The packages can then be upgraded using the package tools on the device, much like + ipk for opkg, + Debian package (.deb), or RPM. + The packages can then be upgraded using the package tools on the device, much like on a desktop distribution such as Ubuntu or Fedora. @@ -182,11 +182,11 @@ - GNOME Mobile is a subset of the GNOME - platform targeted at mobile and embedded devices. - The the main difference between GNOME Mobile and standard GNOME is that - desktop-orientated libraries have been removed, along with deprecated libraries, - creating a much smaller footprint. + GNOME Mobile is a subset of the GNOME + platform targeted at mobile and embedded devices. + The the main difference between GNOME Mobile and standard GNOME is that + desktop-orientated libraries have been removed, along with deprecated libraries, + creating a much smaller footprint. @@ -200,7 +200,7 @@ - You are probably running the build on an NTFS filesystem. + You are probably running the build on an NTFS filesystem. Use ext2, ext3, or ext4 instead. @@ -214,8 +214,8 @@ - To get the Yocto Project working under RHEL/CentOS 5.1 you need to first - install some required packages. + To get the Yocto Project working under RHEL/CentOS 5.1 you need to first + install some required packages. The standard CentOS packages needed are: "Development tools" (selected during installation) @@ -224,19 +224,19 @@ On top of these, you need the following external packages: - python-sqlite2 from + python-sqlite2 from DAG repository - help2man from + help2man from Karan repository - Once these packages are installed, the OpenEmbedded build system will be able + Once these packages are installed, the OpenEmbedded build system will be able to build standard images. - However, there might be a problem with the QEMU emulator segfaulting. - You can either disable the generation of binary locales by setting + However, there might be a problem with the QEMU emulator segfaulting. + You can either disable the generation of binary locales by setting ENABLE_BINARY_LOCALE_GENERATION to "0" or by removing the linux-2.6-execshield.patch from the kernel and rebuilding it since that is the patch that causes the problems with QEMU. @@ -247,22 +247,22 @@ - I see lots of 404 responses for files on + I see lots of 404 responses for files on http://www.yoctoproject.org/sources/*. Is something wrong? Nothing is wrong. - The OpenEmbedded build system checks any configured source mirrors before downloading - from the upstream sources. - The build system does this searching for both source archives and - pre-checked out versions of SCM managed software. - These checks help in large installations because it can reduce load on the SCM servers - themselves. - The address above is one of the default mirrors configured into the + The OpenEmbedded build system checks any configured source mirrors before downloading + from the upstream sources. + The build system does this searching for both source archives and + pre-checked out versions of SCM managed software. + These checks help in large installations because it can reduce load on the SCM servers + themselves. + The address above is one of the default mirrors configured into the build system. - Consequently, if an upstream source disappears, the team + Consequently, if an upstream source disappears, the team can place sources there so builds continue to work. @@ -271,16 +271,16 @@ - I have machine-specific data in a package for one machine only but the package is + I have machine-specific data in a package for one machine only but the package is being marked as machine-specific in all cases, how do I prevent this? Set SRC_URI_OVERRIDES_PACKAGE_ARCH - = "0" in the .bb file but make sure the package is - manually marked as - machine-specific in the case that needs it. + = "0" in the .bb file but make sure the package is + manually marked as + machine-specific in the case that needs it. The code that handles SRC_URI_OVERRIDES_PACKAGE_ARCH is in base.bbclass. @@ -295,9 +295,9 @@ Most source fetching by the OpenEmbedded build system is done by wget - and you therefore need to specify the proxy settings in a - .wgetrc file in your home directory. - Example settings in that file would be + and you therefore need to specify the proxy settings in a + .wgetrc file in your home directory. + Example settings in that file would be http_proxy = http://proxy.yoyodyne.com:18023/ ftp_proxy = http://proxy.yoyodyne.com:18023/ @@ -317,10 +317,10 @@ - The *-native targets are designed to run on the system + The *-native targets are designed to run on the system being used for the build. - These are usually tools that are needed to assist the build in some way such as - quilt-native, which is used to apply patches. + These are usually tools that are needed to assist the build in some way such as + quilt-native, which is used to apply patches. The non-native version is the one that runs on the target device. @@ -335,11 +335,11 @@ If the same build is failing in totally different and random ways, - the most likely explanation is that either the hardware you're running the - build on has some problem, or, if you are running the build under virtualisation, - the virtualisation probably has bugs. - The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and - CPU activity and is sensitive to even single bit failures in any of these areas. + the most likely explanation is that either the hardware you're running the + build on has some problem, or, if you are running the build under virtualisation, + the virtualisation probably has bugs. + The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and + CPU activity and is sensitive to even single bit failures in any of these areas. True random failures have always been traced back to hardware or virtualisation issues. @@ -356,8 +356,8 @@ This is a difficult question and you need to consult your lawyer for the answer for your specific case. It is worth bearing in mind that for GPL compliance there needs to be enough - information shipped to allow someone else to rebuild the same end result - you are shipping. + information shipped to allow someone else to rebuild the same end result + you are shipping. This means sharing the source code, any patches applied to it, and also any configuration information about how that package was configured and built. @@ -390,9 +390,9 @@ - The default interfaces file provided by the netbase recipe does not - automatically bring up network interfaces. - Therefore, you will need to add a BSP-specific netbase that includes an interfaces + The default interfaces file provided by the netbase recipe does not + automatically bring up network interfaces. + Therefore, you will need to add a BSP-specific netbase that includes an interfaces file. See the "Miscellaneous Recipe Files" section for information on creating these types of miscellaneous recipe files. @@ -415,11 +415,11 @@ - Images are created to be 1.2 times the size of the populated root filesystem. - To modify this ratio so that there is more free space available, you need to - set the configuration value IMAGE_OVERHEAD_FACTOR. - For example, setting IMAGE_OVERHEAD_FACTOR to 1.5 sets - the image size ratio to one and a half times the size of the populated + Images are created to be 1.2 times the size of the populated root filesystem. + To modify this ratio so that there is more free space available, you need to + set the configuration value IMAGE_OVERHEAD_FACTOR. + For example, setting IMAGE_OVERHEAD_FACTOR to 1.5 sets + the image size ratio to one and a half times the size of the populated root filesystem. IMAGE_OVERHEAD_FACTOR = "1.5" @@ -436,9 +436,9 @@ - The Yocto Project team has tried to do this before but too many of the tools - the OpenEmbedded build system depends on such as autoconf - break when they find spaces in pathnames. + The Yocto Project team has tried to do this before but too many of the tools + the OpenEmbedded build system depends on such as autoconf + break when they find spaces in pathnames. Until that situation changes, the team will not support spaces in pathnames. @@ -453,10 +453,10 @@ The toolchain configuration is very flexible and customizable. - It is primarily controlled with the + It is primarily controlled with the TCMODE variable. - This variable controls which tcmode-*.inc file to include - from the meta/conf/distro/include directory within the + This variable controls which tcmode-*.inc file to include + from the meta/conf/distro/include directory within the source directory. @@ -466,15 +466,15 @@ However, other patterns are accepted. In particular, "external-*" refers to external toolchains of which there are some basic examples included in the OpenEmbedded Core (meta). - You can use your own custom toolchain definition in your own layer - (or as defined in the local.conf file) at the location + You can use your own custom toolchain definition in your own layer + (or as defined in the local.conf file) at the location conf/distro/include/tcmode-*.inc. In addition to the toolchain configuration, you also need a corresponding toolchain recipe file. - This recipe file needs to package up any pre-built objects in the toolchain such as - libgcc, libstdcc++, + This recipe file needs to package up any pre-built objects in the toolchain such as + libgcc, libstdcc++, any locales, and libc. An example is the external-sourcery-toolchain.bb, which is located in meta/recipes-core/meta/ within the source directory. @@ -485,7 +485,7 @@ - How does the OpenEmbedded build system obtain source code and will it work behind my + How does the OpenEmbedded build system obtain source code and will it work behind my firewall or proxy server? @@ -497,13 +497,13 @@ When the build system searches for source code, it first tries the local download directory. - If that location fails, Poky tries PREMIRRORS, the upstream source, + If that location fails, Poky tries PREMIRRORS, the upstream source, and then MIRRORS in that order. - By default, the OpenEmbedded build system uses the Yocto Project source PREMIRRORS - for SCM-based sources, - upstreams for normal tarballs, and then falls back to a number of other mirrors + By default, the OpenEmbedded build system uses the Yocto Project source PREMIRRORS + for SCM-based sources, + upstreams for normal tarballs, and then falls back to a number of other mirrors including the Yocto Project source mirror if those fail. @@ -521,7 +521,7 @@ These changes cause Poky to intercept Git, FTP, HTTP, and HTTPS requests and direct them to the http:// sources mirror. - You can use file:// URLs to point to local directories + You can use file:// URLs to point to local directories or network shares as well. @@ -529,7 +529,7 @@ BB_NO_NETWORK = "1" - This statement tells BitBake to throw an error instead of trying to access the + This statement tells BitBake to throw an error instead of trying to access the Internet. This technique is useful if you want to ensure code builds only from local sources. @@ -559,14 +559,14 @@ ftp://.*/.* http://www.yoctoproject.org/sources/ \n \ http://.*/.* http://www.yoctoproject.org/sources/ \n \ https://.*/.* http://www.yoctoproject.org/sources/ \n" - BB_FETCH_PREMIRRORONLY = "1" + BB_FETCH_PREMIRRORONLY = "1" - These changes would cause Poky to successfully fetch source over HTTP and + These changes would cause Poky to successfully fetch source over HTTP and any network accesses to anything other than the PREMIRROR would fail. - The build system also honors the standard shell environment variables - http_proxy, ftp_proxy, + The build system also honors the standard shell environment variables + http_proxy, ftp_proxy, https_proxy, and all_proxy to redirect requests through proxy servers. @@ -582,16 +582,16 @@ Yes - you can easily do this. - When you use BitBake to build an image, all the build output goes into the + When you use BitBake to build an image, all the build output goes into the directory created when you source the oe-init-build-env setup file. - By default, this build directory + By default, this build directory is named build but can be named anything you want. - Within the build directory is the tmp directory. + Within the build directory is the tmp directory. To remove all the build output yet preserve any source code or downloaded files from previous builds, simply remove the tmp directory. @@ -601,7 +601,6 @@ - - diff --git a/documentation/poky-ref-manual/introduction.xml b/documentation/poky-ref-manual/introduction.xml index ab2e7d0f31..38c58da262 100644 --- a/documentation/poky-ref-manual/introduction.xml +++ b/documentation/poky-ref-manual/introduction.xml @@ -12,14 +12,14 @@ This manual provides reference information for the current release of the Yocto Project. The Yocto Project is an open-source collaboration project focused on embedded Linux developers. - Amongst other things, the Yocto Project uses the OpenEmbedded build system, which + Amongst other things, the Yocto Project uses the OpenEmbedded build system, which is based on the Poky project, to construct complete Linux images. You can find complete introductory and getting started information on the Yocto Project - by reading the + by reading the Yocto Project Quick Start. For task-based information using the Yocto Project, see the Yocto Project Development Manual. - You can also find lots of information on the Yocto Project on the + You can also find lots of information on the Yocto Project on the Yocto Project website. @@ -31,53 +31,53 @@ Using the Yocto Project: This chapter - provides an overview of the components that make up the Yocto Project + provides an overview of the components that make up the Yocto Project followed by information about debugging images created in the Yocto Project. - Technical Details: + Technical Details: This chapter describes fundamental Yocto Project components as well as an explanation behind how the Yocto Project uses shared state (sstate) cache to speed build time. - Directory Structure: - This chapter describes the + Directory Structure: + This chapter describes the source directory created - either by unpacking a released Yocto Project tarball on your host development system, - or by cloning the upstream + either by unpacking a released Yocto Project tarball on your host development system, + or by cloning the upstream Poky Git repository. - BitBake: - This chapter provides an overview of the BitBake tool and its role within + BitBake: + This chapter provides an overview of the BitBake tool and its role within the Yocto Project. - Classes: + Classes: This chapter describes the classes used in the Yocto Project. - Images: + Images: This chapter describes the standard images that the Yocto Project supports. - Features: - This chapter describes mechanisms for creating distribution, machine, and image + Features: + This chapter describes mechanisms for creating distribution, machine, and image features during the build process using the OpenEmbedded build system. - Variables Glossary: + Variables Glossary: This chapter presents most variables used by the OpenEmbedded build system, which using BitBake. Entries describe the function of the variable and how to apply them. - Variable Context: + Variable Context: This chapter provides variable locality or context. - FAQ: + FAQ: This chapter provides answers for commonly asked questions in the Yocto Project development environment. - Contributing to the Yocto Project: - This chapter provides guidance on how you can contribute back to the Yocto + Contributing to the Yocto Project: + This chapter provides guidance on how you can contribute back to the Yocto Project. @@ -88,7 +88,7 @@ System Requirements For general Yocto Project system requirements, see the - "What You Need and How You Get It" section + "What You Need and How You Get It" section in the Yocto Project Quick Start. The remainder of this section provides details on system requirements not covered in the Yocto Project Quick Start. @@ -120,8 +120,8 @@ - For additional information on distributions that support the - Yocto Project, see the + For additional information on distributions that support the + Yocto Project, see the Distribution Support wiki page. @@ -130,9 +130,9 @@ Required Packages for the Host Development System - 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 provides required packages by Linux distribution and + 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 provides required packages by Linux distribution and further categorized by function. @@ -144,7 +144,7 @@ given a supported Ubuntu Linux distribution: Essentials: - Packages needed to build an image on a headless + Packages needed to build an image on a headless system: $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; @@ -155,13 +155,13 @@ $ sudo apt-get install libsdl1.2-dev xterm Documentation: - Packages needed if you are going to build out the + Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo apt-get install make xsltproc docbook-utils fop ADT Installer Extras: - Packages needed if you are going to be using the + Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer: $ sudo apt-get install autoconf automake libtool libglib2.0-dev @@ -178,7 +178,7 @@ given a supported Fedora Linux distribution: Essentials: - Packages needed to build an image for a headless + Packages needed to build an image for a headless system: $ sudo yum install &FEDORA_HOST_PACKAGES_ESSENTIAL; @@ -189,14 +189,14 @@ $ sudo yum install SDL-devel xterm Documentation: - Packages needed if you are going to build out the + Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo yum install make docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt ADT Installer Extras: - Packages needed if you are going to be using the + Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer: $ sudo yum install autoconf automake libtool glib2-devel @@ -213,7 +213,7 @@ given a supported OpenSUSE Linux distribution: Essentials: - Packages needed to build an image for a headless + Packages needed to build an image for a headless system: $ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL; @@ -224,13 +224,13 @@ $ sudo zypper install libSDL-devel xterm Documentation: - Packages needed if you are going to build out the + Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo zypper install make fop xsltproc ADT Installer Extras: - Packages needed if you are going to be using the + Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer: $ sudo zypper install autoconf automake libtool glib2-devel @@ -247,7 +247,7 @@ given a supported CentOS Linux distribution: Essentials: - Packages needed to build an image for a headless + Packages needed to build an image for a headless system: $ sudo yum -y install &CENTOS_HOST_PACKAGES_ESSENTIAL; @@ -258,22 +258,22 @@ $ sudo yum -y install SDL-devel xterm Documentation: - Packages needed if you are going to build out the + Packages needed if you are going to build out the Yocto Project documentation manuals: $ sudo yum -y install make docbook-style-dsssl docbook-style-xsl \ docbook-dtds docbook-utils fop libxslt ADT Installer Extras: - Packages needed if you are going to be using the + Packages needed if you are going to be using the Application Development Toolkit (ADT) Installer: $ sudo yum -y install autoconf automake libtool glib2-devel - Depending on the CentOS version you are using, other requirements - and dependencies might exist. - For details, you should look at the CentOS sections on the + Depending on the CentOS version you are using, other requirements + and dependencies might exist. + For details, you should look at the CentOS sections on the Poky/GettingStarted/Dependencies wiki page. @@ -284,19 +284,19 @@
Obtaining the Yocto Project - The Yocto Project development team makes the Yocto Project available through a number + The Yocto Project development team makes the Yocto Project available through a number of methods: - Releases: Stable, tested releases are available through + Releases: Stable, tested releases are available through . Nightly Builds: These releases are available at - . - These builds include Yocto Project releases, meta-toolchain tarball installation scripts, and + . + These builds include Yocto Project releases, meta-toolchain tarball installation scripts, and experimental builds. Yocto Project Website: You can find releases of the Yocto Project and supported BSPs at the Yocto Project website. - Along with these downloads, you can find lots of other information at this site. + Along with these downloads, you can find lots of other information at this site. @@ -305,13 +305,13 @@
Development Checkouts - Development using the Yocto Project requires a local - Source Directory. - You can set up the source directory by downloading a Yocto Project release tarball and unpacking it, + Development using the Yocto Project requires a local + Source Directory. + You can set up the source directory by downloading a Yocto Project release tarball and unpacking it, or by cloning a copy of the upstream Poky Git repository. For information on both these methods, see the - "Getting Setup" + "Getting Setup" section in the Yocto Project Development Manual.
diff --git a/documentation/poky-ref-manual/migration.xml b/documentation/poky-ref-manual/migration.xml index b311da65c5..40c570f8ca 100644 --- a/documentation/poky-ref-manual/migration.xml +++ b/documentation/poky-ref-manual/migration.xml @@ -6,8 +6,8 @@ Migrating to a Newer Yocto Project Release - This chapter provides information you can use to migrate work to a - newer Yocto Project release. You can find the same information in the + This chapter provides information you can use to migrate work to a + newer Yocto Project release. You can find the same information in the release notes for a given release. @@ -15,7 +15,7 @@ Moving to the Yocto Project 1.3 Release - This section provides migration information for moving to the + This section provides migration information for moving to the Yocto Project 1.3 Release. @@ -23,7 +23,7 @@ Local Configuration - Differences include changes for + Differences include changes for SSTATE_MIRRORS and bblayers.conf. @@ -32,18 +32,18 @@ SSTATE_MIRRORS - The shared state cache (sstate-cache) as pointed to by - SSTATE_DIR by default - now has two-character subdirectories to prevent there being an issue with too + The shared state cache (sstate-cache) as pointed to by + SSTATE_DIR by default + now has two-character subdirectories to prevent there being an issue with too many files in the same directory. - Also, native sstate-cache packages will go into a subdirectory named using - the distro ID string. - If you copy the newly structured sstate-cache to a mirror location - (either local or remote) and then point to it in + Also, native sstate-cache packages will go into a subdirectory named using + the distro ID string. + If you copy the newly structured sstate-cache to a mirror location + (either local or remote) and then point to it in SSTATE_MIRRORS, - you need to append "PATH" to the end of the mirror URL so that - the path used by BitBake before the mirror substitution is - appended to the path used to access the mirror. + you need to append "PATH" to the end of the mirror URL so that + the path used by BitBake before the mirror substitution is + appended to the path used to access the mirror. Here is an example: SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH" @@ -55,14 +55,14 @@ bblayers.conf - The meta-yocto layer has been split into - two parts: meta-yocto and - meta-yocto-bsp, corresponding to the + The meta-yocto layer has been split into + two parts: meta-yocto and + meta-yocto-bsp, corresponding to the Poky reference distro configuration and the reference - hardware Board Support Packages (BSPs), respectively. - When running BitBake or Hob for the first time after upgrading, - your conf/bblayers.conf file will be - updated to handle this change and you will be asked to + hardware Board Support Packages (BSPs), respectively. + When running BitBake or Hob for the first time after upgrading, + your conf/bblayers.conf file will be + updated to handle this change and you will be asked to re-run/restart for the changes to take effect.
@@ -87,16 +87,16 @@ Python Function Whitespace - All Python functions must now use four spaces for indentation. + All Python functions must now use four spaces for indentation. Previously, an inconsistent mix of spaces and tabs existed, - which made extending these functions using + which made extending these functions using _append or _prepend - complicated given that Python treats whitespace as - syntactically significant. + complicated given that Python treats whitespace as + syntactically significant. If you are defining or extending any Python functions (e.g. populate_packages, do_unpack, do_patch and so forth) in custom recipes - or classes, you need to ensure you are using consistent + or classes, you need to ensure you are using consistent four-space indentation. @@ -105,7 +105,7 @@ proto= in SRC_URI - Any use of proto= in + Any use of proto= in SRC_URI needs to be changed to protocol=. In particular, this applies to the following URIs: @@ -125,11 +125,11 @@ The suffix nativesdk is now implemented - as a prefix, which simplifies a lot of the packaging code for - nativesdk recipes. - All custom nativesdk recipes and any - references need to be updated to use - nativesdk-* instead of + as a prefix, which simplifies a lot of the packaging code for + nativesdk recipes. + All custom nativesdk recipes and any + references need to be updated to use + nativesdk-* instead of *-nativesdk. @@ -138,25 +138,25 @@ Task Recipes - "Task" recipes are now known as "Package groups" and have - been renamed from task-*.bb to - packagegroup-*.bb. + "Task" recipes are now known as "Package groups" and have + been renamed from task-*.bb to + packagegroup-*.bb. Existing references to the previous task-* - names should work in most cases as there is an automatic + names should work in most cases as there is an automatic upgrade path for most packages. - However, you should update references in your own recipes and - configurations as they could be removed in future releases. + However, you should update references in your own recipes and + configurations as they could be removed in future releases. You should also rename any custom task-* - recipes to packagegroup-*, and change - them to inherit packagegroup instead of - task, as well as taking the opportunity - to remove anything now handled by + recipes to packagegroup-*, and change + them to inherit packagegroup instead of + task, as well as taking the opportunity + to remove anything now handled by packagegroup.bbclass, such as providing -dev and -dbg - packages, setting - LIC_FILES_CHKSUM, + packages, setting + LIC_FILES_CHKSUM, and so forth. - See the + See the "Package Groups - packagegroup.bbclass" section for further details. @@ -166,13 +166,13 @@ IMAGE_FEATURES - Image recipes that previously included "apps-console-core" + Image recipes that previously included "apps-console-core" in IMAGE_FEATURES - should now include "splash" instead to enable the boot-up + should now include "splash" instead to enable the boot-up splash screen. - Retaining "apps-console-core" will still include the splash + Retaining "apps-console-core" will still include the splash screen generates a warning. - The "apps-x11-core" and "apps-x11-games" + The "apps-x11-core" and "apps-x11-games" IMAGE_FEATURES features have been removed. @@ -181,55 +181,55 @@ Removed Recipes - The following recipes have been removed. - For most of them, it is unlikely that you would have any + The following recipes have been removed. + For most of them, it is unlikely that you would have any references to them in your own metadata. However, you should check your metadata against this list to be sure: - libx11-trim: - Replaced by libx11, which has a negligible + libx11-trim: + Replaced by libx11, which has a negligible size difference with modern Xorg. - xserver-xorg-lite: - Use xserver-xorg, which has a negligible + xserver-xorg-lite: + Use xserver-xorg, which has a negligible size difference when DRI and GLX modules are not installed. - xserver-kdrive: + xserver-kdrive: Effectively unmaintained for many years. - mesa-xlib: + mesa-xlib: No longer serves any purpose. - galago: + galago: Replaced by telepathy. - gail: + gail: Functionality was integrated into GTK+ 2.13. - eggdbus: + eggdbus: No longer needed. - gcc-*-intermediate: - The build has been restructured to avoid the need for + gcc-*-intermediate: + The build has been restructured to avoid the need for this step. - libgsmd: + libgsmd: Unmaintained for many years. - Functionality now provided by + Functionality now provided by ofono instead. - contacts, dates, tasks, eds-tools: + contacts, dates, tasks, eds-tools: Largely unmaintained PIM application suite. It has been moved to meta-gnome in meta-openembedded. - In addition to the previously listed changes, the + In addition to the previously listed changes, the meta-demoapps directory has also been removed - because the recipes in it were not being maintained and many + because the recipes in it were not being maintained and many had become obsolete or broken. Additionally, these recipes were not parsed in the default configuration. - Many of these recipes are already provided in an updated and - maintained form within OpenEmbedded community layers such as + Many of these recipes are already provided in an updated and + maintained form within OpenEmbedded community layers such as meta-oe and meta-gnome. - For the remainder, you can now find them in the - meta-extras repository, which is in the + For the remainder, you can now find them in the + meta-extras repository, which is in the Yocto Project source repositories. - + - diff --git a/documentation/poky-ref-manual/poky-ref-manual.xml b/documentation/poky-ref-manual/poky-ref-manual.xml index 51f5e2d9f4..2fcc68d88c 100644 --- a/documentation/poky-ref-manual/poky-ref-manual.xml +++ b/documentation/poky-ref-manual/poky-ref-manual.xml @@ -2,18 +2,18 @@ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ %poky; ] > - - + - - + @@ -74,7 +74,7 @@ - Permission is granted to copy, distribute and/or modify this document under + Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-Share Alike 2.0 UK: England & Wales as published by Creative Commons. @@ -116,10 +116,10 @@ - diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml index b81f12fb7a..b641d5cff9 100644 --- a/documentation/poky-ref-manual/ref-bitbake.xml +++ b/documentation/poky-ref-manual/ref-bitbake.xml @@ -14,15 +14,15 @@ $ bitbake core-image-sato - + This chapter provides an overview of what happens behind the scenes from BitBake's perspective. - BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships. - As such, it has no real knowledge of what the tasks being executed actually do. - BitBake just considers a list of tasks with dependencies and handles metadata + BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships. + As such, it has no real knowledge of what the tasks being executed actually do. + BitBake just considers a list of tasks with dependencies and handles metadata that consists of variables in a certain format that get passed to the tasks. @@ -30,85 +30,85 @@ Parsing - BitBake parses configuration files, classes, and .bb files. + BitBake parses configuration files, classes, and .bb files. The first thing BitBake does is look for the bitbake.conf file. - This file resides in the + This file resides in the Source Directory within the meta/conf/ directory. - BitBake finds it by examining its - BBPATH environment - variable and looking for the meta/conf/ + BitBake finds it by examining its + BBPATH environment + variable and looking for the meta/conf/ directory. - The bitbake.conf file lists other configuration - files to include from a conf/ - directory below the directories listed in BBPATH. - In general, the most important configuration file from a user's perspective - is local.conf, which contains a user's customized - settings for the OpenEmbedded build environment. - Other notable configuration files are the distribution - configuration file (set by the - DISTRO variable) - and the machine configuration file - (set by the - MACHINE variable). - The DISTRO and MACHINE BitBake environment - variables are both usually set in - the local.conf file. - Valid distribution - configuration files are available in the meta/conf/distro/ directory - and valid machine configuration - files in the meta/conf/machine/ directory. - Within the meta/conf/machine/include/ - directory are various tune-*.inc configuration files that provide common + The bitbake.conf file lists other configuration + files to include from a conf/ + directory below the directories listed in BBPATH. + In general, the most important configuration file from a user's perspective + is local.conf, which contains a user's customized + settings for the OpenEmbedded build environment. + Other notable configuration files are the distribution + configuration file (set by the + DISTRO variable) + and the machine configuration file + (set by the + MACHINE variable). + The DISTRO and MACHINE BitBake environment + variables are both usually set in + the local.conf file. + Valid distribution + configuration files are available in the meta/conf/distro/ directory + and valid machine configuration + files in the meta/conf/machine/ directory. + Within the meta/conf/machine/include/ + directory are various tune-*.inc configuration files that provide common "tuning" settings specific to and shared between particular architectures and machines. - After the parsing of the configuration files, some standard classes are included. + After the parsing of the configuration files, some standard classes are included. The base.bbclass file is always included. - Other classes that are specified in the configuration using the + Other classes that are specified in the configuration using the INHERIT - variable are also included. - Class files are searched for in a classes subdirectory + variable are also included. + Class files are searched for in a classes subdirectory under the paths in BBPATH in the same way as configuration files. - After classes are included, the variable - BBFILES + After classes are included, the variable + BBFILES is set, usually in - local.conf, and defines the list of places to search for - .bb files. - By default, the BBFILES variable specifies the - meta/recipes-*/ directory within Poky. - Adding extra content to BBFILES is best achieved through the use of - BitBake layers as described in the - "Understanding and + local.conf, and defines the list of places to search for + .bb files. + By default, the BBFILES variable specifies the + meta/recipes-*/ directory within Poky. + Adding extra content to BBFILES is best achieved through the use of + BitBake layers as described in the + "Understanding and Creating Layers" section of the Yocto Project Development Manual. - BitBake parses each .bb file in BBFILES and - stores the values of various variables. - In summary, for each .bb - file the configuration plus the base class of variables are set, followed - by the data in the .bb file + BitBake parses each .bb file in BBFILES and + stores the values of various variables. + In summary, for each .bb + file the configuration plus the base class of variables are set, followed + by the data in the .bb file itself, followed by any inherit commands that .bb file might contain. - Because parsing .bb files is a time - consuming process, a cache is kept to speed up subsequent parsing. - This cache is invalid if the timestamp of the .bb - file itself changes, or if the timestamps of any of the include, + Because parsing .bb files is a time + consuming process, a cache is kept to speed up subsequent parsing. + This cache is invalid if the timestamp of the .bb + file itself changes, or if the timestamps of any of the include, configuration or class files the .bb file depends on changes. @@ -118,22 +118,22 @@ Preferences and Providers - Once all the .bb files have been + Once all the .bb files have been parsed, BitBake starts to build the target (core-image-sato in the previous section's example) and looks for providers of that target. - Once a provider is selected, BitBake resolves all the dependencies for - the target. - In the case of core-image-sato, it would lead to - packagegroup-core-x11-sato, - which in turn leads to recipes like matchbox-terminal, + Once a provider is selected, BitBake resolves all the dependencies for + the target. + In the case of core-image-sato, it would lead to + packagegroup-core-x11-sato, + which in turn leads to recipes like matchbox-terminal, pcmanfm and gthumb. These recipes in turn depend on eglibc and the toolchain. Sometimes a target might have multiple providers. - A common example is "virtual/kernel", which is provided by each kernel package. - Each machine often selects the best kernel provider by using a line similar to the + A common example is "virtual/kernel", which is provided by each kernel package. + Each machine often selects the best kernel provider by using a line similar to the following in the machine configuration file: @@ -142,25 +142,25 @@ - The default PREFERRED_PROVIDER + The default PREFERRED_PROVIDER is the provider with the same name as the target. Understanding how providers are chosen is made complicated by the fact - that multiple versions might exist. + that multiple versions might exist. BitBake defaults to the highest version of a provider. - Version comparisons are made using the same method as Debian. + Version comparisons are made using the same method as Debian. You can use the PREFERRED_VERSION variable to specify a particular version (usually in the distro configuration). - You can influence the order by using the - DEFAULT_PREFERENCE - variable. - By default, files have a preference of "0". - Setting the DEFAULT_PREFERENCE to "-1" makes the + You can influence the order by using the + DEFAULT_PREFERENCE + variable. + By default, files have a preference of "0". + Setting the DEFAULT_PREFERENCE to "-1" makes the package unlikely to be used unless it is explicitly referenced. - Setting the DEFAULT_PREFERENCE to "1" makes it likely the package is used. + Setting the DEFAULT_PREFERENCE to "1" makes it likely the package is used. PREFERRED_VERSION overrides any DEFAULT_PREFERENCE setting. DEFAULT_PREFERENCE is often used to mark newer and more experimental package versions until they have undergone sufficient testing to be considered stable. @@ -175,23 +175,23 @@ Dependencies - Each target BitBake builds consists of multiple tasks such as - fetch, unpack, - patch, configure, - and compile. - For best performance on multi-core systems, BitBake considers each task as an independent - entity with its own set of dependencies. + Each target BitBake builds consists of multiple tasks such as + fetch, unpack, + patch, configure, + and compile. + For best performance on multi-core systems, BitBake considers each task as an independent + entity with its own set of dependencies. - + Dependencies are defined through several variables. You can find information about variables BitBake uses in the BitBake documentation, which is found in the bitbake/doc/manual directory within the - Source Directory. - At a basic level, it is sufficient to know that BitBake uses the - DEPENDS and - RDEPENDS variables when - calculating dependencies. + Source Directory. + At a basic level, it is sufficient to know that BitBake uses the + DEPENDS and + RDEPENDS variables when + calculating dependencies. @@ -199,40 +199,40 @@ The Task List - Based on the generated list of providers and the dependency information, - BitBake can now calculate exactly what tasks it needs to run and in what - order it needs to run them. - The build now starts with BitBake forking off threads up to the limit set in the + Based on the generated list of providers and the dependency information, + BitBake can now calculate exactly what tasks it needs to run and in what + order it needs to run them. + The build now starts with BitBake forking off threads up to the limit set in the BB_NUMBER_THREADS variable. BitBake continues to fork threads as long as there are tasks ready to run, - those tasks have all their dependencies met, and the thread threshold has not been + those tasks have all their dependencies met, and the thread threshold has not been exceeded. - It is worth noting that you can greatly speed up the build time by properly setting - the BB_NUMBER_THREADS variable. + It is worth noting that you can greatly speed up the build time by properly setting + the BB_NUMBER_THREADS variable. See the "Building an Image" section in the Yocto Project Quick Start for more information. - As each task completes, a timestamp is written to the directory specified by the + As each task completes, a timestamp is written to the directory specified by the STAMP variable (usually - build/tmp/stamps/*/). + build/tmp/stamps/*/). On subsequent runs, BitBake looks at the /build/tmp/stamps directory and does not rerun - tasks that are already completed unless a timestamp is found to be invalid. - Currently, invalid timestamps are only considered on a per + tasks that are already completed unless a timestamp is found to be invalid. + Currently, invalid timestamps are only considered on a per .bb file basis. - So, for example, if the configure stamp has a timestamp greater than the + So, for example, if the configure stamp has a timestamp greater than the compile timestamp for a given target, then the compile task would rerun. - Running the compile task again, however, has no effect on other providers - that depend on that target. - This behavior could change or become configurable in future versions of BitBake. + Running the compile task again, however, has no effect on other providers + that depend on that target. + This behavior could change or become configurable in future versions of BitBake. - + Some tasks are marked as "nostamp" tasks. No timestamp file is created when these tasks are run. @@ -245,52 +245,52 @@ Tasks can either be a shell task or a Python task. - For shell tasks, BitBake writes a shell script to - ${WORKDIR}/temp/run.do_taskname.pid and then executes the script. - The generated shell script contains all the exported variables, and the shell functions - with all variables expanded. + For shell tasks, BitBake writes a shell script to + ${WORKDIR}/temp/run.do_taskname.pid and then executes the script. + The generated shell script contains all the exported variables, and the shell functions + with all variables expanded. Output from the shell script goes to the file ${WORKDIR}/temp/log.do_taskname.pid. - Looking at the expanded shell functions in the run file and the output in the log files + Looking at the expanded shell functions in the run file and the output in the log files is a useful debugging technique. - For Python tasks, BitBake executes the task internally and logs information to the - controlling terminal. - Future versions of BitBake will write the functions to files similar to the way + For Python tasks, BitBake executes the task internally and logs information to the + controlling terminal. + Future versions of BitBake will write the functions to files similar to the way shell tasks are handled. Logging will be handled in way similar to shell tasks as well. Once all the tasks have been completed BitBake exits. - + - When running a task, BitBake tightly controls the execution environment + When running a task, BitBake tightly controls the execution environment of the build tasks to make sure unwanted contamination from the build machine - cannot influence the build. - Consequently, if you do want something to get passed into the build + cannot influence the build. + Consequently, if you do want something to get passed into the build task's environment, you must take a few steps: Tell BitBake to load what you want from the environment - into the data store. + into the data store. You can do so through the BB_ENV_EXTRAWHITE variable. - For example, assume you want to prevent the build system from + For example, assume you want to prevent the build system from accessing your $HOME/.ccache directory. - The following command tells BitBake to load + The following command tells BitBake to load CCACHE_DIR from the environment into the data store: - export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE CCACHE_DIR" + export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE CCACHE_DIR" - Tell BitBake to export what you have loaded into the + Tell BitBake to export what you have loaded into the environment store to the task environment of every running task. Loading something from the environment into the data store - (previous step) only makes it available in the datastore. + (previous step) only makes it available in the datastore. To export it to the task environment of every running task, - use a command similar to the following in your + use a command similar to the following in your local.conf or distro configuration file: export CCACHE_DIR @@ -301,8 +301,8 @@ A side effect of the previous steps is that BitBake records the variable as a dependency of the build process in things like the shared state - checksums. - If doing so results in unnecessary rebuilds of tasks, you can whitelist the + checksums. + If doing so results in unnecessary rebuilds of tasks, you can whitelist the variable so that the shared state code ignores the dependency when it creates checksums. For information on this process, see the BB_HASHBASE_WHITELIST @@ -383,38 +383,38 @@ Options: Fetchers - BitBake also contains a set of "fetcher" modules that allow - retrieval of source code from various types of sources. - For example, BitBake can get source code from a disk with the metadata, from websites, - from remote shell accounts or from Source Code Management (SCM) systems - like cvs/subversion/git. + BitBake also contains a set of "fetcher" modules that allow + retrieval of source code from various types of sources. + For example, BitBake can get source code from a disk with the metadata, from websites, + from remote shell accounts or from Source Code Management (SCM) systems + like cvs/subversion/git. - Fetchers are usually triggered by entries in - SRC_URI. - You can find information about the options and formats of entries for specific - fetchers in the BitBake manual located in the - bitbake/doc/manual directory of the + Fetchers are usually triggered by entries in + SRC_URI. + You can find information about the options and formats of entries for specific + fetchers in the BitBake manual located in the + bitbake/doc/manual directory of the Source Directory. - One useful feature for certain Source Code Manager (SCM) fetchers is the ability to - "auto-update" when the upstream SCM changes version. + One useful feature for certain Source Code Manager (SCM) fetchers is the ability to + "auto-update" when the upstream SCM changes version. Since this ability requires certain functionality from the SCM, not all systems support it. - Currently Subversion, Bazaar and to a limited extent, Git support the ability to "auto-update". - This feature works using the SRCREV - variable. - See the - "Using an External SCM" section + Currently Subversion, Bazaar and to a limited extent, Git support the ability to "auto-update". + This feature works using the SRCREV + variable. + See the + "Using an External SCM" section in the Yocto Project Development Manual for more information. - diff --git a/documentation/poky-ref-manual/ref-classes.xml b/documentation/poky-ref-manual/ref-classes.xml index 973d065f58..5ba9811853 100644 --- a/documentation/poky-ref-manual/ref-classes.xml +++ b/documentation/poky-ref-manual/ref-classes.xml @@ -6,23 +6,23 @@ Classes - Class files are used to abstract common functionality and share it amongst multiple - .bb files. - Any metadata usually found in a .bb file can also be placed in a class - file. - Class files are identified by the extension .bbclass and are usually placed - in a classes/ directory beneath the - meta*/ directory found in the + Class files are used to abstract common functionality and share it amongst multiple + .bb files. + Any metadata usually found in a .bb file can also be placed in a class + file. + Class files are identified by the extension .bbclass and are usually placed + in a classes/ directory beneath the + meta*/ directory found in the Source Directory. Class files can also be pointed to by BUILDDIR (e.g. build/)in the same way as - .conf files in the conf directory. + .conf files in the conf directory. Class files are searched for in BBPATH using the same method by which .conf files are searched. - In most cases inheriting the class is enough to enable its features, although - for some classes you might need to set variables or override some of the + In most cases inheriting the class is enough to enable its features, although + for some classes you might need to set variables or override some of the default behaviour. @@ -30,14 +30,14 @@ The base class - <filename>base.bbclass</filename> - The base class is special in that every .bb - file inherits it automatically. - This class contains definitions for standard basic - tasks such as fetching, unpacking, configuring (empty by default), compiling - (runs any Makefile present), installing (empty by default) and packaging - (empty by default). - These classes are often overridden or extended by other classes - such as autotools.bbclass or package.bbclass. + The base class is special in that every .bb + file inherits it automatically. + This class contains definitions for standard basic + tasks such as fetching, unpacking, configuring (empty by default), compiling + (runs any Makefile present), installing (empty by default) and packaging + (empty by default). + These classes are often overridden or extended by other classes + such as autotools.bbclass or package.bbclass. The class also contains some commonly used functions such as oe_runmake. @@ -46,14 +46,14 @@ Autotooled Packages - <filename>autotools.bbclass</filename> - Autotools (autoconf, automake, - and libtool) bring standardization. - This class defines a set of tasks (configure, compile etc.) that - work for all Autotooled packages. - It should usually be enough to define a few standard variables + Autotools (autoconf, automake, + and libtool) bring standardization. + This class defines a set of tasks (configure, compile etc.) that + work for all Autotooled packages. + It should usually be enough to define a few standard variables and then simply inherit autotools. This class can also work with software that emulates Autotools. - For more information, see the + For more information, see the "Autotooled Package" section in the Yocto Project Development Manual. @@ -62,19 +62,19 @@ It's useful to have some idea of how the tasks defined by this class work and what they do behind the scenes. - do_configure ‐ regenerates the - configure script (using autoreconf) and then launches it - with a standard set of arguments used during cross-compilation. - You can pass additional parameters to configure through the + do_configure ‐ regenerates the + configure script (using autoreconf) and then launches it + with a standard set of arguments used during cross-compilation. + You can pass additional parameters to configure through the EXTRA_OECONF variable. - do_compile ‐ runs make with - arguments that specify the compiler and linker. - You can pass additional arguments through + do_compile ‐ runs make with + arguments that specify the compiler and linker. + You can pass additional arguments through the EXTRA_OEMAKE variable. - do_install ‐ runs make install - and passes a DESTDIR option, which takes its value from the standard + do_install ‐ runs make install + and passes a DESTDIR option, which takes its value from the standard DESTDIR variable. @@ -85,28 +85,28 @@ Alternatives - <filename>update-alternatives.bbclass</filename> - Several programs can fulfill the same or similar function and be installed with the same name. - For example, the ar command is available from the - busybox, binutils and - elfutils packages. - The update-alternatives.bbclass class handles renaming the - binaries so that multiple packages can be installed without conflicts. + Several programs can fulfill the same or similar function and be installed with the same name. + For example, the ar command is available from the + busybox, binutils and + elfutils packages. + The update-alternatives.bbclass class handles renaming the + binaries so that multiple packages can be installed without conflicts. The ar command still works regardless of which packages are installed - or subsequently removed. - The class renames the conflicting binary in each package and symlinks the highest + or subsequently removed. + The class renames the conflicting binary in each package and symlinks the highest priority binary during installation or removal of packages. Four variables control this class: - ALTERNATIVE_NAME ‐ The name of the + ALTERNATIVE_NAME ‐ The name of the binary that is replaced (ar in this example). - ALTERNATIVE_LINK ‐ The path to + ALTERNATIVE_LINK ‐ The path to the resulting binary (/bin/ar in this example). - ALTERNATIVE_PATH ‐ The path to the + ALTERNATIVE_PATH ‐ The path to the real binary (/usr/bin/ar.binutils in this example). - ALTERNATIVE_PRIORITY ‐ The priority of - the binary. + ALTERNATIVE_PRIORITY ‐ The priority of + the binary. The version with the most features should have the highest priority. @@ -120,12 +120,12 @@ Initscripts - <filename>update-rc.d.bbclass</filename> - This class uses update-rc.d to safely install an - initialization script on behalf of the package. - The OpenEmbedded build system takes care of details such as making sure the script is stopped before - a package is removed and started when the package is installed. - Three variables control this class: - INITSCRIPT_PACKAGES, + This class uses update-rc.d to safely install an + initialization script on behalf of the package. + The OpenEmbedded build system takes care of details such as making sure the script is stopped before + a package is removed and started when the package is installed. + Three variables control this class: + INITSCRIPT_PACKAGES, INITSCRIPT_NAME and INITSCRIPT_PARAMS. See the variable links for details. @@ -137,16 +137,16 @@ Before pkg-config had become widespread, libraries shipped shell - scripts to give information about the libraries and include paths needed + scripts to give information about the libraries and include paths needed to build software (usually named LIBNAME-config). This class assists any recipe using such scripts. During staging, BitBake installs such scripts into the - sysroots/ directory. + sysroots/ directory. BitBake also changes all paths to point into the sysroots/ - directory so all builds that use the script will use the correct + directory so all builds that use the script will use the correct directories for the cross compiling layout. @@ -171,7 +171,7 @@ During staging, BitBake installs pkg-config data into the - sysroots/ directory. + sysroots/ directory. By making use of sysroot functionality within pkg-config, this class no longer has to manipulate the files. @@ -183,14 +183,14 @@ Many software licenses require that source files be provided along with the binaries. To simplify this process, two classes were created: - src_distribute.bbclass and + src_distribute.bbclass and src_distribute_local.bbclass. - The results of these classes are tmp/deploy/source/ - subdirs with sources sorted by - LICENSE field. + The results of these classes are tmp/deploy/source/ + subdirs with sources sorted by + LICENSE field. If recipes list few licenses (or have entries like "Bitstream Vera"), the source archive is placed in each license directory. @@ -198,11 +198,11 @@ This class operates using three modes: - copy: Copies the files to the + copy: Copies the files to the distribute directory. - symlink: Symlinks the files to the + symlink: Symlinks the files to the distribute directory. - move+symlink: Moves the files into + move+symlink: Moves the files into the distribute directory and then symlinks them back. @@ -213,11 +213,11 @@ Recipes for Perl modules are simple. - These recipes usually only need to point to the source's archive and then inherit the + These recipes usually only need to point to the source's archive and then inherit the proper .bbclass file. Building is split into two methods depending on which method the module authors used. - + Modules that use old Makefile.PL-based build system require cpan.bbclass in their recipes. @@ -240,12 +240,12 @@ - Extensions that use an Autotools-based build system require Autotools and + Extensions that use an Autotools-based build system require Autotools and distutils-based .bbclasse files in their recipes. - Extensions that use distutils-based build systems require + Extensions that use distutils-based build systems require distutils.bbclass in their recipes. @@ -254,10 +254,10 @@ Developer Shell - <filename>devshell.bbclass</filename> - This class adds the devshell task. + This class adds the devshell task. Distribution policy dictates whether to include this class. - See the - "Using a Development Shell" section + See the + "Using a Development Shell" section in the Yocto Project Development Manual for more information about using devshell. @@ -266,16 +266,16 @@ Package Groups - <filename>packagegroup.bbclass</filename> - This class sets default values appropriate for package group recipes (such as - PACKAGES, - PACKAGE_ARCH, - ALLOW_EMPTY, - and so forth. + This class sets default values appropriate for package group recipes (such as + PACKAGES, + PACKAGE_ARCH, + ALLOW_EMPTY, + and so forth. It is highly recommended that all package group recipes inherit this class. - For information on how to use this class, see the - "Customizing Images Using Custom Package Tasks" + For information on how to use this class, see the + "Customizing Images Using Custom Package Tasks" section in the Yocto Project Development Manual. @@ -289,41 +289,41 @@ The packaging classes add support for generating packages from a build's - output. + output. The core generic functionality is in package.bbclass. The code specific to particular package types is contained in various sub-classes such as package_deb.bbclass, package_ipk.bbclass, - and package_rpm.bbclass. + and package_rpm.bbclass. Most users will want one or more of these classes. - + - You can control the list of resulting package formats by using the - PACKAGE_CLASSES - variable defined in the local.conf configuration file, - which is located in the conf folder of the - Source Directory. + You can control the list of resulting package formats by using the + PACKAGE_CLASSES + variable defined in the local.conf configuration file, + which is located in the conf folder of the + Source Directory. When defining the variable, you can specify one or more package types. - Since images are generated from packages, a packaging class is + Since images are generated from packages, a packaging class is needed to enable image generation. - The first class listed in this variable is used for image generation. + The first class listed in this variable is used for image generation. The package class you choose can affect build-time performance and has space ramifications. - In general, building a package with RPM takes about thirty percent more time as + In general, building a package with RPM takes about thirty percent more time as compared to using IPK to build the same or similar package. - This comparison takes into account a complete build of the package with all + This comparison takes into account a complete build of the package with all dependencies previously built. - The reason for this discrepancy is because the RPM package manager creates and + The reason for this discrepancy is because the RPM package manager creates and processes more metadata than the IPK package manager. Consequently, you might consider setting PACKAGE_CLASSES to "package_ipk" if you are building smaller systems. - Keep in mind, however, that RPM starts to provide more abilities than IPK due to + Keep in mind, however, that RPM starts to provide more abilities than IPK due to the fact that it processes more metadata. For example, this information includes individual file types, file checksum generation and evaluation on install, sparse file support, conflict detection and resolution @@ -332,12 +332,12 @@ Another consideration for packages built using the RPM package manager is space. - For smaller systems, the extra space used for the Berkley Database and the amount + For smaller systems, the extra space used for the Berkley Database and the amount of metadata can affect your ability to do on-device upgrades. - You can find additional information on the effects of the package class at these + You can find additional information on the effects of the package class at these two Yocto Project mailing list links: @@ -352,24 +352,24 @@ Building kernels - <filename>kernel.bbclass</filename> - This class handles building Linux kernels. - The class contains code to build all kernel trees. + This class handles building Linux kernels. + The class contains code to build all kernel trees. All needed headers are staged into the STAGING_KERNEL_DIR directory to allow out-of-tree module builds using module.bbclass. - This means that each built kernel module is packaged separately and inter-module - dependencies are created by parsing the modinfo output. + This means that each built kernel module is packaged separately and inter-module + dependencies are created by parsing the modinfo output. If all modules are required, then installing the kernel-modules - package installs all packages with modules and various other kernel packages + package installs all packages with modules and various other kernel packages such as kernel-vmlinux. - Various other classes are used by the kernel and module classes internally including - kernel-arch.bbclass, module_strip.bbclass, + Various other classes are used by the kernel and module classes internally including + kernel-arch.bbclass, module_strip.bbclass, module-base.bbclass, and linux-kernel-base.bbclass. @@ -378,9 +378,9 @@ Creating images - <filename>image.bbclass</filename> and <filename>rootfs*.bbclass</filename> - These classes add support for creating images in several formats. + These classes add support for creating images in several formats. First, the root filesystem is created from packages using - one of the rootfs_*.bbclass + one of the rootfs_*.bbclass files (depending on the package format used) and then the image is created. @@ -389,7 +389,7 @@ variable controls the types of images to generate. - + The IMAGE_INSTALL variable controls the list of packages to install into the image. @@ -399,11 +399,11 @@ Host System sanity checks - <filename>sanity.bbclass</filename> - This class checks to see if prerequisite software is present so that - users can be notified of potential problems that might affect their build. - The class also performs basic user configuration checks from + This class checks to see if prerequisite software is present so that + users can be notified of potential problems that might affect their build. + The class also performs basic user configuration checks from the local.conf configuration file to - prevent common mistakes that cause build failures. + prevent common mistakes that cause build failures. Distribution policy usually determines whether to include this class. @@ -420,14 +420,14 @@ - You can configure the sanity checks so that specific test failures either raise a warning or - an error message. + You can configure the sanity checks so that specific test failures either raise a warning or + an error message. Typically, failures for new tests generate a warning. - Subsequent failures for the same test would then generate an error message + Subsequent failures for the same test would then generate an error message once the metadata is in a known and good condition. - You use the WARN_QA variable to specify tests for which you + You use the WARN_QA variable to specify tests for which you want to generate a warning message on failure. - You use the ERROR_QA variable to specify tests for which you + You use the ERROR_QA variable to specify tests for which you want to generate an error message on failure. @@ -436,41 +436,41 @@ and ERROR_QA variables: ldflags: - Ensures that the binaries were linked with the - LDFLAGS options provided by the build system. + Ensures that the binaries were linked with the + LDFLAGS options provided by the build system. If this test fails, check that the LDFLAGS variable is being passed to the linker command. useless-rpaths: - Checks for dynamic library load paths (rpaths) in the binaries that + Checks for dynamic library load paths (rpaths) in the binaries that by default on a standard system are searched by the linker (e.g. - /lib and /usr/lib). - While these paths will not cause any breakage, they do waste space and + /lib and /usr/lib). + While these paths will not cause any breakage, they do waste space and are unnecessary. rpaths: Checks for rpaths in the binaries that contain build system paths such as TMPDIR. - If this test fails, bad -rpath options are being - passed to the linker commands and your binaries have potential security + If this test fails, bad -rpath options are being + passed to the linker commands and your binaries have potential security issues. dev-so: - Checks that the .so symbolic links are in the - -dev package and not in any of the other packages. + Checks that the .so symbolic links are in the + -dev package and not in any of the other packages. In general, these symlinks are only useful for development purposes. Thus, the -dev package is the correct location for - them. - Some very rare cases do exist for dynamically loaded modules where + them. + Some very rare cases do exist for dynamically loaded modules where these symlinks are needed instead in the main package. debug-files: - Checks for .debug directories in anything but the - -dbg package. + Checks for .debug directories in anything but the + -dbg package. The debug files should all be in the -dbg package. Thus, anything packaged elsewhere is incorrect packaging. arch: - Checks the Executable and Linkable Format (ELF) type, bit size and endianness - of any binaries to ensure it matches the target architecture. - This test fails if any binaries don't match the type since there would be an - incompatibility. + Checks the Executable and Linkable Format (ELF) type, bit size and endianness + of any binaries to ensure it matches the target architecture. + This test fails if any binaries don't match the type since there would be an + incompatibility. Sometimes software, like bootloaders, might need to bypass this check. debug-deps: @@ -478,24 +478,24 @@ -dbg packages and not on any other types of packages, which would cause a packaging bug. dev-deps: - Checks that -dev packages only depend on other + Checks that -dev packages only depend on other -dev packages and not on any other types of packages, which would be a packaging bug. pkgconfig: - Checks .pc files for any - TMPDIR/WORKDIR paths. - Any .pc file containing these paths is incorrect - since pkg-config itself adds the correct sysroot prefix + Checks .pc files for any + TMPDIR/WORKDIR paths. + Any .pc file containing these paths is incorrect + since pkg-config itself adds the correct sysroot prefix when the files are accessed. la: Checks .la files for any TMPDIR - paths. - Any .la file continaing these paths is incorrect since - libtool adds the correct sysroot prefix when using the + paths. + Any .la file continaing these paths is incorrect since + libtool adds the correct sysroot prefix when using the files automatically itself. desktop: - Runs the desktop-file-validate program against any - .desktop files to validate their contents against + Runs the desktop-file-validate program against any + .desktop files to validate their contents against the specification for .desktop files. @@ -511,17 +511,17 @@ still make the correct values available. The meta/site directory contains test results sorted into different categories such as architecture, endianness, and - the libc used. - Site information provides a list of files containing data relevant to - the current build in the - CONFIG_SITE variable + the libc used. + Site information provides a list of files containing data relevant to + the current build in the + CONFIG_SITE variable that Autotools automatically picks up. - The class also provides variables like - SITEINFO_ENDIANNESS - and SITEINFO_BITS + The class also provides variables like + SITEINFO_ENDIANNESS + and SITEINFO_BITS that can be used elsewhere in the metadata. @@ -534,14 +534,14 @@ Adding Users - <filename>useradd.bbclass</filename> - If you have packages that install files that are owned by custom users or groups, + If you have packages that install files that are owned by custom users or groups, you can use this class to specify those packages and associate the users and groups with those packages. - The meta-skeleton/recipes-skeleton/useradd/useradd-example.bb + The meta-skeleton/recipes-skeleton/useradd/useradd-example.bb recipe in the Source Directory - provides a simple exmample that shows how to add three + provides a simple exmample that shows how to add three users and groups to two packages. - See the useradd-example.bb for more information on how to + See the useradd-example.bb for more information on how to use this class. @@ -550,33 +550,33 @@ Using External Source - <filename>externalsrc.bbclass</filename> - You can use this class to build software from source code that is external to the - OpenEmbedded build system. + You can use this class to build software from source code that is external to the + OpenEmbedded build system. In other words, your source code resides in an external tree outside of the Yocto Project. - Building software from an external source tree means that the normal fetch, unpack, and + Building software from an external source tree means that the normal fetch, unpack, and patch process is not used. - To use the class, you need to define the - S variable to point to the directory that contains the source files. + To use the class, you need to define the + S variable to point to the directory that contains the source files. You also need to have your recipe inherit the externalsrc.bbclass class. - This class expects the source code to support recipe builds that use the - B variable to point to the directory in + This class expects the source code to support recipe builds that use the + B variable to point to the directory in which the OpenEmbedded build system places the generated objects built from the recipes. - By default, the B directory is set to the following, which is separate from the + By default, the B directory is set to the following, which is separate from the Source Directory (S): ${WORKDIR}/${BPN}-{PV}/ See the glossary entries for the - WORKDIR, - BPN, + WORKDIR, + BPN, PV, - S, and + S, and B for more information. @@ -584,26 +584,26 @@ You can build object files in the external tree by setting the B variable equal to "${S}". However, this practice does not work well if you use the source for more than one variant - (i.e., "natives" such as quilt-native, + (i.e., "natives" such as quilt-native, or "crosses" such as gcc-cross). So, be sure there are no "native", "cross", or "multilib" variants of the recipe. - If you do want to build different variants of a recipe, you can use the - BBCLASSEXTEND variable. - When you do, the B variable must support the + If you do want to build different variants of a recipe, you can use the + BBCLASSEXTEND variable. + When you do, the B variable must support the recipe's ability to build variants in different working directories. Most autotools-based recipes support separating these directories. The OpenEmbedded build system defaults to using separate directories for gcc and some kernel recipes. - Alternatively, you can make sure that separate recipes exist that each + Alternatively, you can make sure that separate recipes exist that each use the BBCLASSEXTEND variable to build each variant. The separate recipes can inherit a single target recipe. - For information on how to use this class, see the + For information on how to use this class, see the "Building Software from an External Source" section in the Yocto Project Development Manual. @@ -613,12 +613,12 @@ Other Classes - Thus far, this chapter has discussed only the most useful and important + Thus far, this chapter has discussed only the most useful and important classes. - However, other classes exist within the meta/classes directory + However, other classes exist within the meta/classes directory in the Source Directory. - You can examine the .bbclass files directly for more - information. + You can examine the .bbclass files directly for more + information. @@ -715,6 +715,6 @@ - diff --git a/documentation/poky-ref-manual/ref-features.xml b/documentation/poky-ref-manual/ref-features.xml index ec70547314..77c31275ae 100644 --- a/documentation/poky-ref-manual/ref-features.xml +++ b/documentation/poky-ref-manual/ref-features.xml @@ -7,7 +7,7 @@ Features provide a mechanism for working out which packages - should be included in the generated images. + should be included in the generated images. Distributions can select which features they want to support through the DISTRO_FEATURES variable, which is set in the poky.conf distribution configuration file. @@ -19,16 +19,16 @@ These two variables combine to work out which kernel modules, - utilities, and other packages to include. + utilities, and other packages to include. A given distribution can support a selected subset of features so some machine features might not be included if the distribution itself does not support them. - One method you can use to determine which recipes are checking to see if a - particular feature is contained or not is to grep through + One method you can use to determine which recipes are checking to see if a + particular feature is contained or not is to grep through the metadata for the feature. - Here is an example that discovers the recipes whose build is potentially + Here is an example that discovers the recipes whose build is potentially changed based on a given feature: $ cd $HOME/poky @@ -38,21 +38,21 @@ This chapter provides a reference of shipped machine and distro features - you can include as part of the image, a reference on image types you can + you can include as part of the image, a reference on image types you can build, and a reference on feature backfilling. - - + +
Distro - The items below are features you can use with + The items below are features you can use with DISTRO_FEATURES. - Features do not have a one-to-one correspondence to packages, and they can - go beyond simply controlling the installation of a package or packages. + Features do not have a one-to-one correspondence to packages, and they can + go beyond simply controlling the installation of a package or packages. Sometimes a feature can influence how certain recipes are built. - For example, a feature might determine whether a particular configure option + For example, a feature might determine whether a particular configure option is specified within do_configure for a particular recipe. @@ -60,7 +60,7 @@ This list only represents features as shipped with the Yocto Project metadata: - alsa: ALSA support will be included (OSS compatibility + alsa: ALSA support will be included (OSS compatibility kernel modules will be installed if available). bluetooth: Include bluetooth support (integrated BT only) @@ -69,7 +69,7 @@ irda: Include Irda support - keyboard: Include keyboard support (e.g. keymaps will be + keyboard: Include keyboard support (e.g. keymaps will be loaded during boot). pci: Include PCI bus support @@ -103,12 +103,12 @@ Machine - The items below are features you can use with + The items below are features you can use with MACHINE_FEATURES. - Features do not have a one-to-one correspondence to packages, and they can - go beyond simply controlling the installation of a package or packages. + Features do not have a one-to-one correspondence to packages, and they can + go beyond simply controlling the installation of a package or packages. Sometimes a feature can influence how certain recipes are built. - For example, a feature might determine whether a particular configure option + For example, a feature might determine whether a particular configure option is specified within do_configure for a particular recipe. @@ -154,7 +154,7 @@ Images - The contents of images generated by the OpenEmbedded build system can be controlled by the + The contents of images generated by the OpenEmbedded build system can be controlled by the IMAGE_FEATURES and EXTRA_IMAGE_FEATURES variables that you typically configure in your image recipes. @@ -164,48 +164,48 @@ - Current list of + Current list of IMAGE_FEATURES contains the following: - splash: Enables showing a splash screen during boot. - By default, this screen is provided by psplash, which does - allow customization. - If you prefer to use an alternative splash screen package, you can do so by + splash: Enables showing a splash screen during boot. + By default, this screen is provided by psplash, which does + allow customization. + If you prefer to use an alternative splash screen package, you can do so by setting the SPLASH variable to a different package name (or names) within the image recipe or at the distro configuration level. - ssh-server-dropbear: Installs the Dropbear minimal + ssh-server-dropbear: Installs the Dropbear minimal SSH server. ssh-server-openssh: Installs the OpenSSH SSH server, - which is more full-featured than Dropbear. + which is more full-featured than Dropbear. Note that if both the OpenSSH SSH server and the Dropbear minimal SSH server are present in IMAGE_FEATURES, then OpenSSH will take precedence and Dropbear will not be installed. x11: Installs the X server - x11-base: Installs the X server with a + x11-base: Installs the X server with a minimal environment. x11-sato: Installs the OpenedHand Sato environment. tools-sdk: Installs a full SDK that runs on the device. - tools-debug: Installs debugging tools such as + tools-debug: Installs debugging tools such as strace and gdb. - tools-profile: Installs profiling tools such as - oprofile, exmap, and + tools-profile: Installs profiling tools such as + oprofile, exmap, and LTTng. tools-testapps: Installs device testing tools (e.g. touchscreen debugging). nfs-server: Installs an NFS server. - dev-pkgs: Installs development packages (headers and + dev-pkgs: Installs development packages (headers and extra library links) for all packages installed in a given image. - staticdev-pkgs: Installs static development - packages (i.e. static libraries containing *.a files) for all + staticdev-pkgs: Installs static development + packages (i.e. static libraries containing *.a files) for all packages installed in a given image. - dbg-pkgs: Installs debug symbol packages for all packages + dbg-pkgs: Installs debug symbol packages for all packages installed in a given image. - doc-pkgs: Installs documentation packages for all packages + doc-pkgs: Installs documentation packages for all packages installed in a given image. @@ -218,30 +218,30 @@ Sometimes it is necessary in the OpenEmbedded build system to extend MACHINE_FEATURES or DISTRO_FEATURES - to control functionality that was previously enabled and not able - to be disabled. + to control functionality that was previously enabled and not able + to be disabled. For these cases, we need to add an - additional feature item to appear in one of these variables, - but we do not want to force developers who have existing values - of the variables in their configuration to add the new feature - in order to retain the same overall level of functionality. + additional feature item to appear in one of these variables, + but we do not want to force developers who have existing values + of the variables in their configuration to add the new feature + in order to retain the same overall level of functionality. Thus, the OpenEmbedded build system has a mechanism to - automatically "backfill" these added features into existing - distro or machine configurations. + automatically "backfill" these added features into existing + distro or machine configurations. You can see the list of features for which this is done by - finding the + finding the DISTRO_FEATURES_BACKFILL and MACHINE_FEATURES_BACKFILL variables in the meta/conf/bitbake.conf file. - Because such features are backfilled by default into all - configurations as described in the previous paragraph, developers - who wish to disable the new features need to be able to selectively + Because such features are backfilled by default into all + configurations as described in the previous paragraph, developers + who wish to disable the new features need to be able to selectively prevent the backfilling from occurring. They can do this by adding the undesired feature or features to the - DISTRO_FEATURES_BACKFILL_CONSIDERED + DISTRO_FEATURES_BACKFILL_CONSIDERED or MACHINE_FEATURES_BACKFILL_CONSIDERED variables for distro features and machine features respectively. @@ -249,46 +249,46 @@ Here are two examples to help illustrate feature backfilling: - The "pulseaudio" distro feature option: - Previously, PulseAudio support was enabled within the Qt and + The "pulseaudio" distro feature option: + Previously, PulseAudio support was enabled within the Qt and GStreamer frameworks. - Because of this, the feature is backfilled and thus - enabled for all distros through the + Because of this, the feature is backfilled and thus + enabled for all distros through the DISTRO_FEATURES_BACKFILL variable in the meta/conf/bitbake.conf file. However, your distro needs to disable the feature. - You can disable the feature without affecting + You can disable the feature without affecting other existing distro configurations that need PulseAudio support by adding "pulseaudio" to DISTRO_FEATURES_BACKFILL_CONSIDERED in your distro's .conf file. Adding the feature to this variable when it also exists in the DISTRO_FEATURES_BACKFILL - variable prevents the build system from adding the feature to + variable prevents the build system from adding the feature to your configuration's DISTRO_FEATURES, effectively disabling the feature for that particular distro. - The "rtc" machine feature option: - Previously, real time clock (RTC) support was enabled for all + The "rtc" machine feature option: + Previously, real time clock (RTC) support was enabled for all target devices. Because of this, the feature is backfilled and thus enabled for all machines through the MACHINE_FEATURES_BACKFILL variable in the meta/conf/bitbake.conf file. However, your target device does not have this capability. - You can disable RTC support for your device without - affecting other machines that need RTC support - by adding the feature to your machine's + You can disable RTC support for your device without + affecting other machines that need RTC support + by adding the feature to your machine's MACHINE_FEATURES_BACKFILL_CONSIDERED list in the machine's .conf file. Adding the feature to this variable when it also exists in the MACHINE_FEATURES_BACKFILL - variable prevents the build system from adding the feature to - your configuration's MACHINE_FEATURES, effectively + variable prevents the build system from adding the feature to + your configuration's MACHINE_FEATURES, effectively disabling RTC support for that particular machine.
- diff --git a/documentation/poky-ref-manual/ref-images.xml b/documentation/poky-ref-manual/ref-images.xml index 79f2409933..0a827ca235 100644 --- a/documentation/poky-ref-manual/ref-images.xml +++ b/documentation/poky-ref-manual/ref-images.xml @@ -6,8 +6,8 @@ Images - The OpenEmbedded build process supports several types of images to satisfy different needs. - When you issue the bitbake command you provide a “top-level” recipe + The OpenEmbedded build process supports several types of images to satisfy different needs. + When you issue the bitbake command you provide a “top-level” recipe that essentially begins the build for the type of image you want. @@ -24,16 +24,16 @@ - From within the poky Git repository, use the following command to list + From within the poky Git repository, use the following command to list the supported images: $ ls meta*/recipes*/images/*.bb These recipes reside in the meta/recipes-core/images, - meta/recipes-extended/images, - meta/recipes-graphics/images, and - meta/recipes-sato/images directories - within the source directory. + meta/recipes-extended/images, + meta/recipes-graphics/images, and + meta/recipes-sato/images directories + within the source directory. Although the recipe names are somewhat explanatory, here is a list that describes them: @@ -45,17 +45,17 @@ core-image-minimal-dev: A core-image-minimal image suitable for development work using the host. - The image includes headers and libraries you can use in a host development + The image includes headers and libraries you can use in a host development environment. core-image-minimal-initramfs: - A core-image-minimal image that has the Minimal RAM-based - Initial Root Filesystem (initramfs) as part of the kernel, + A core-image-minimal image that has the Minimal RAM-based + Initial Root Filesystem (initramfs) as part of the kernel, which allows the system to find the first “init” program more efficiently. core-image-minimal-mtdutils: - A core-image-minimal image that has support - for the Minimal MTD Utilities, which let the user interact with the + A core-image-minimal image that has support + for the Minimal MTD Utilities, which let the user interact with the MTD subsystem in the kernel to perform operations on flash devices. core-image-x11: @@ -69,64 +69,64 @@ core-image-lsb-dev: A core-image-lsb image that is suitable for development work using the host. - The image includes headers and libraries you can use in a host development + The image includes headers and libraries you can use in a host development environment. core-image-lsb-sdk: - A core-image-lsb that includes everything in meta-toolchain + A core-image-lsb that includes everything in meta-toolchain but also includes development headers and libraries to form a complete standalone SDK. This image is suitable for development using the target. core-image-clutter: - An image with support for the Open GL-based toolkit Clutter, which enables development of + An image with support for the Open GL-based toolkit Clutter, which enables development of rich and animated graphical user interfaces. core-image-sato: - An image with Sato support, a mobile environment and visual style that works well + An image with Sato support, a mobile environment and visual style that works well with mobile devices. The image supports X11 with a Sato theme and applications such as a terminal, editor, file manager, media player, and so forth. core-image-sato-dev: - A core-image-sato image suitable for development + A core-image-sato image suitable for development using the host. - The image includes libraries needed to build applications on the device itself, - testing and profiling tools, and debug symbols. + The image includes libraries needed to build applications on the device itself, + testing and profiling tools, and debug symbols. This image was formerly core-image-sdk. core-image-sato-sdk: - A core-image-sato image that includes everything in meta-toolchain. + A core-image-sato image that includes everything in meta-toolchain. The image also includes development headers and libraries to form a complete standalone SDK and is suitable for development using the target. core-image-rt: - A core-image-minimal image plus a real-time test suite and + A core-image-minimal image plus a real-time test suite and tools appropriate for real-time use. core-image-rt-sdk: - A core-image-rt image that includes everything in - meta-toolchain. - The image also includes development headers and libraries to form a complete + A core-image-rt image that includes everything in + meta-toolchain. + The image also includes development headers and libraries to form a complete stand-alone SDK and is suitable for development using the target. core-image-gtk-directfb: - An image that uses gtk+ over directfb - instead of X11. - In order to build, this image requires specific distro configuration that enables + An image that uses gtk+ over directfb + instead of X11. + In order to build, this image requires specific distro configuration that enables gtk over directfb. build-appliance-image: An image you can boot and run using either the VMware Player or VMware Workstation. For more information on this image, see the - Build Appliance page on + Build Appliance page on the Yocto Project website. - From the Yocto Project release 1.1 onwards, -live and + From the Yocto Project release 1.1 onwards, -live and -directdisk images have been replaced by a "live" - option in IMAGE_FSTYPES that will work with any image to produce an + option in IMAGE_FSTYPES that will work with any image to produce an image file that can be - copied directly to a CD or USB device and run as is. + copied directly to a CD or USB device and run as is. To build a live image, simply add "live" to IMAGE_FSTYPES within the local.conf file or wherever appropriate and then build the desired image as normal. - diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml index 166907ceef..673b05a52b 100644 --- a/documentation/poky-ref-manual/ref-structure.xml +++ b/documentation/poky-ref-manual/ref-structure.xml @@ -9,7 +9,7 @@ The Source Directory consists of several components. Understanding them and knowing where they are located is key to using the Yocto Project well. - This chapter describes the Source Directory and gives information about the various + This chapter describes the Source Directory and gives information about the various files and directories. @@ -35,26 +35,26 @@ The Source Directory includes a copy of BitBake for ease of use. - The copy usually matches the current stable BitBake release from the BitBake project. - BitBake, a metadata interpreter, reads the Yocto Project metadata and runs the tasks - defined by that data. + The copy usually matches the current stable BitBake release from the BitBake project. + BitBake, a metadata interpreter, reads the Yocto Project metadata and runs the tasks + defined by that data. Failures are usually from the metadata and not from BitBake itself. Consequently, most users do not need to worry about BitBake. - When you run the bitbake command, the wrapper script in - scripts/ is executed to run the main BitBake executable, + When you run the bitbake command, the wrapper script in + scripts/ is executed to run the main BitBake executable, which resides in the bitbake/bin/ directory. - Sourcing the &OE_INIT_FILE; + Sourcing the &OE_INIT_FILE; script places the scripts and bitbake/bin - directories (in that order) into the shell's PATH environment + directories (in that order) into the shell's PATH environment variable. - For more information on BitBake, see the BitBake documentation - inculded in the bitbake/doc/manual directory of the + For more information on BitBake, see the BitBake documentation + inculded in the bitbake/doc/manual directory of the Source Directory. @@ -63,21 +63,21 @@ <filename>build/</filename> - This directory contains user configuration files and the output - generated by the OpenEmbedded build system in its standard configuration where + This directory contains user configuration files and the output + generated by the OpenEmbedded build system in its standard configuration where the source tree is combined with the output. The Build Directory is created initially when you source the OpenEmbedded build environment setup script &OE_INIT_FILE;. - - It is also possible to place output and configuration - files in a directory separate from the + + It is also possible to place output and configuration + files in a directory separate from the Source Directory by providing a directory name when you source the setup script. - For information on separating output from your local Source Directory files, see &OE_INIT_FILE;. @@ -88,9 +88,9 @@ This directory holds the source for the Yocto Project documentation as well as templates and tools that allow you to generate PDF and HTML - versions of the manuals. - Each manual is contained in a sub-folder. - For example, the files for this manual reside in + versions of the manuals. + Each manual is contained in a sub-folder. + For example, the files for this manual reside in poky-ref-manual. @@ -99,7 +99,7 @@ <filename>meta/</filename> - This directory contains the OpenEmbedded Core metadata. + This directory contains the OpenEmbedded Core metadata. The directory holds recipes, common classes, and machine configuration for emulated targets (qemux86, qemuarm, and so on.) @@ -138,7 +138,7 @@ <filename>meta-skeleton/</filename> - This directory contains template recipes for BSP and kernel development. + This directory contains template recipes for BSP and kernel development. @@ -146,7 +146,7 @@ <filename>scripts/</filename> - This directory contains various integration scripts that implement + This directory contains various integration scripts that implement extra functionality in the Yocto Project environment (e.g. QEMU scripts). The &OE_INIT_FILE; script appends this directory to the shell's PATH environment variable. @@ -154,7 +154,7 @@ The scripts directory has useful scripts that assist contributing - back to the Yocto Project, such as create_pull_request and + back to the Yocto Project, such as create_pull_request and send_pull_request. @@ -163,23 +163,23 @@ <filename>&OE_INIT_FILE;</filename> - This script sets up the OpenEmbedded build environment. + This script sets up the OpenEmbedded build environment. Running this script with the source command in a shell makes changes to PATH and sets other core BitBake variables based on the - current working directory. + current working directory. You need to run this script before running BitBake commands. - The script uses other scripts within the scripts directory to do + The script uses other scripts within the scripts directory to do the bulk of the work. - By default, running this script without a Build Directory argument creates the - build directory. + By default, running this script without a Build Directory argument creates the + build directory. If you provide a Build Directory argument when you source - the script, you direct OpenEmbedded build system to create a + the script, you direct OpenEmbedded build system to create a Build Directory of your choice. - For example, the following command creates a Build Directory named - mybuilds that is outside of the + For example, the following command creates a Build Directory named + mybuilds that is outside of the Source Directory: $ source &OE_INIT_FILE; ~/mybuilds @@ -189,7 +189,7 @@ contain spaces. If you attempt to run the &OE_INIT_FILE; script from a Source Directory that contains spaces in either the filenames - or directory names, the script returns an error indicating no such + or directory names, the script returns an error indicating no such file or directory. Be sure to use a Source Directory free of names containing spaces. @@ -200,7 +200,7 @@ <filename>LICENSE, README, and README.hardware</filename> - These files are standard top-level files. + These files are standard top-level files. @@ -212,8 +212,8 @@ <filename>build/pseudodone</filename> - This tag file indicates that the initial pseudo binary was created. - The file is built the first time BitBake is invoked. + This tag file indicates that the initial pseudo binary was created. + The file is built the first time BitBake is invoked. @@ -221,24 +221,24 @@ <filename>build/conf/local.conf</filename> - This file contains all the local user configuration for your build environment. - If there is no local.conf present, it is created from - local.conf.sample. - The local.conf file contains documentation on the various configuration options. - Any variable set here overrides any variable set elsewhere within the environment unless - that variable is hard-coded within a file (e.g. by using '=' instead of '?='). - Some variables are hard-coded for various reasons but these variables are + This file contains all the local user configuration for your build environment. + If there is no local.conf present, it is created from + local.conf.sample. + The local.conf file contains documentation on the various configuration options. + Any variable set here overrides any variable set elsewhere within the environment unless + that variable is hard-coded within a file (e.g. by using '=' instead of '?='). + Some variables are hard-coded for various reasons but these variables are relatively rare. - Edit this file to set the MACHINE - for which you want to build, which package types you wish to use - (PACKAGE_CLASSES), + Edit this file to set the MACHINE + for which you want to build, which package types you wish to use + (PACKAGE_CLASSES), where you want to downloaded files - (DL_DIR), - and how you want your host machine to use resources - (BB_NUMBER_THREADS and + (DL_DIR), + and how you want your host machine to use resources + (BB_NUMBER_THREADS and PARALLEL_MAKE). @@ -248,8 +248,8 @@ This file defines layers, which are directory trees, traversed (or walked) by BitBake. - If bblayers.conf - is not present, it is created from bblayers.conf.sample when + If bblayers.conf + is not present, it is created from bblayers.conf.sample when you source the environment setup script. @@ -276,7 +276,7 @@ This directory is used for the upstream source tarballs. - The directory can be reused by multiple builds or moved to another location. + The directory can be reused by multiple builds or moved to another location. You can control the location of this directory through the DL_DIR variable. @@ -287,7 +287,7 @@ This directory is used for the shared state cache. - The directory can be reused by multiple builds or moved to another location. + The directory can be reused by multiple builds or moved to another location. You can control the location of this directory through the SSTATE_DIR variable. @@ -298,9 +298,9 @@ This directory receives all the OpenEmbedded build system's output. - BitBake creates this directory if it does not exist. - As a last resort, to clean up a build and start it from scratch (other than the downloads), - you can remove everything in the tmp directory or get rid of the + BitBake creates this directory if it does not exist. + As a last resort, to clean up a build and start it from scratch (other than the downloads), + you can remove everything in the tmp directory or get rid of the directory completely. If you do, you should also completely remove the build/sstate-cache directory as well. @@ -320,7 +320,7 @@ When BitBake parses the metadata, it creates a cache file of the result that can - be used when subsequently running commands. + be used when subsequently running commands. These results are stored here on a per-machine basis. @@ -337,7 +337,7 @@ <filename>build/tmp/deploy/deb/</filename> - This directory receives any .deb packages produced by + This directory receives any .deb packages produced by the build process. The packages are sorted into feeds for different architecture types. @@ -347,8 +347,8 @@ <filename>build/tmp/deploy/rpm/</filename> - This directory receives any .rpm packages produced by - the build process. + This directory receives any .rpm packages produced by + the build process. The packages are sorted into feeds for different architecture types. @@ -368,16 +368,16 @@ <filename>build/tmp/deploy/images/</filename> - This directory receives complete filesystem images. + This directory receives complete filesystem images. If you want to flash the resulting image from a build onto a device, look here for the image. - Be careful when deleting files in this directory. - You can safely delete old images from this directory (e.g. + Be careful when deleting files in this directory. + You can safely delete old images from this directory (e.g. core-image-*, hob-image-*, - etc.). - However, the kernel (*zImage*, *uImage*, etc.), + etc.). + However, the kernel (*zImage*, *uImage*, etc.), bootloader and other supplementary files might be deployed here prior to building an image. Because these files, however, are not directly produced from the image, if you @@ -385,8 +385,8 @@ - If you do accidentally delete files here, you will need to force them to be - re-created. + If you do accidentally delete files here, you will need to force them to be + re-created. In order to do that, you will need to know the target that produced them. For example, these commands rebuild and re-create the kernel files: @@ -400,7 +400,7 @@ <filename>build/tmp/deploy/ipk/</filename> - This directory receives .ipk packages produced by + This directory receives .ipk packages produced by the build process. @@ -408,9 +408,9 @@ <filename>build/tmp/sysroots/</filename> - This directory contains shared header files and libraries as well as other shared - data. - Packages that need to share output with other packages do so within this directory. + This directory contains shared header files and libraries as well as other shared + data. + Packages that need to share output with other packages do so within this directory. The directory is subdivided by architecture so multiple builds can run within the one Build Directory. @@ -420,9 +420,9 @@ <filename>build/tmp/stamps/</filename> - This directory holds information that that BitBake uses for accounting purposes + This directory holds information that that BitBake uses for accounting purposes to track what tasks have run and when they have run. - The directory is sub-divided by architecture. + The directory is sub-divided by architecture. The files in the directory are empty of data. However, BitBake uses the filenames and timestamps for tracking purposes. @@ -432,9 +432,9 @@ <filename>build/tmp/log/</filename> - This directory contains general logs that are not otherwise placed using the + This directory contains general logs that are not otherwise placed using the package's WORKDIR. - Examples of logs are the output from the check_pkg or + Examples of logs are the output from the check_pkg or distro_check tasks. Running a build does not necessarily mean this directory is created. @@ -444,7 +444,7 @@ <filename>build/tmp/pkgdata/</filename> - This directory contains intermediate packaging data that is used later in the packaging process. + This directory contains intermediate packaging data that is used later in the packaging process. For more information, see the "Packaging - package*.bbclass" section. @@ -453,7 +453,7 @@ <filename>build/tmp/work/</filename> - This directory contains architecture-specific work sub-directories for packages built by BitBake. + This directory contains architecture-specific work sub-directories for packages built by BitBake. All tasks execute from a work directory. For example, the source for a particular package is unpacked, patched, configured and compiled all within its own work directory. @@ -462,31 +462,31 @@ - It is worth considering the structure of a typical work directory. + It is worth considering the structure of a typical work directory. As an example, consider the linux-yocto-kernel-3.0 - on the machine qemux86 - built within the Yocto Project. - For this package, a work directory of - tmp/work/qemux86-poky-linux/linux-yocto-3.0+git1+<.....>, - referred to as WORKDIR, is created. - Within this directory, the source is unpacked to - linux-qemux86-standard-build and then patched by Quilt - (see the - "Modifying Package - Source Code with Quilt" section in the Yocto Project Development Manual. - Within the linux-qemux86-standard-build directory, + on the machine qemux86 + built within the Yocto Project. + For this package, a work directory of + tmp/work/qemux86-poky-linux/linux-yocto-3.0+git1+<.....>, + referred to as WORKDIR, is created. + Within this directory, the source is unpacked to + linux-qemux86-standard-build and then patched by Quilt + (see the + "Modifying Package + Source Code with Quilt" section in the Yocto Project Development Manual. + Within the linux-qemux86-standard-build directory, standard Quilt directories linux-3.0/patches and linux-3.0/.pc are created, and standard Quilt commands can be used. - There are other directories generated within WORKDIR. - The most important directory is WORKDIR/temp/, which has log files for each - task (log.do_*.pid) and contains the scripts BitBake runs for - each task (run.do_*.pid). - The WORKDIR/image/ directory is where "make - install" places its output that is then split into sub-packages + There are other directories generated within WORKDIR. + The most important directory is WORKDIR/temp/, which has log files for each + task (log.do_*.pid) and contains the scripts BitBake runs for + each task (run.do_*.pid). + The WORKDIR/image/ directory is where "make + install" places its output that is then split into sub-packages within WORKDIR/packages-split/. @@ -496,7 +496,7 @@ The Metadata - <filename>meta/</filename> - As mentioned previously, metadata is the core of the Yocto Project. + As mentioned previously, metadata is the core of the Yocto Project. Metadata has several important subdivisions: @@ -504,16 +504,16 @@ <filename>meta/classes/</filename> - This directory contains the *.bbclass files. - Class files are used to abstract common code so it can be reused by multiple - packages. + This directory contains the *.bbclass files. + Class files are used to abstract common code so it can be reused by multiple + packages. Every package inherits the base.bbclass file. - Examples of other important classes are autotools.bbclass, which + Examples of other important classes are autotools.bbclass, which in theory allows any Autotool-enabled package to work with the Yocto Project with minimal effort. - Another example is kernel.bbclass that contains common code and functions - for working with the Linux kernel. - Functions like image generation or packaging also have their specific class files - such as image.bbclass, rootfs_*.bbclass and + Another example is kernel.bbclass that contains common code and functions + for working with the Linux kernel. + Functions like image generation or packaging also have their specific class files + such as image.bbclass, rootfs_*.bbclass and package*.bbclass. @@ -522,13 +522,13 @@ <filename>meta/conf/</filename> - This directory contains the core set of configuration files that start from - bitbake.conf and from which all other configuration + This directory contains the core set of configuration files that start from + bitbake.conf and from which all other configuration files are included. - See the include statements at the end of the file and you will note that even - local.conf is loaded from there. - While bitbake.conf sets up the defaults, you can often override - these by using the (local.conf) file, machine file or + See the include statements at the end of the file and you will note that even + local.conf is loaded from there. + While bitbake.conf sets up the defaults, you can often override + these by using the (local.conf) file, machine file or the distribution configuration file. @@ -537,11 +537,11 @@ <filename>meta/conf/machine/</filename> - This directory contains all the machine configuration files. - If you set MACHINE="qemux86", - the OpenEmbedded build system looks for a qemux86.conf file in this - directory. - The include directory contains various data common to multiple machines. + This directory contains all the machine configuration files. + If you set MACHINE="qemux86", + the OpenEmbedded build system looks for a qemux86.conf file in this + directory. + The include directory contains various data common to multiple machines. If you want to add support for a new machine to the Yocto Project, look in this directory. @@ -550,10 +550,10 @@ <filename>meta/conf/distro/</filename> - Any distribution-specific configuration is controlled from this directory. - For the Yocto Project, the defaultsetup.conf is the main file here. - This directory includes the versions and the - SRCDATE definitions for applications that are configured here. + Any distribution-specific configuration is controlled from this directory. + For the Yocto Project, the defaultsetup.conf is the main file here. + This directory includes the versions and the + SRCDATE definitions for applications that are configured here. An example of an alternative configuration might be poky-bleeding.conf. Although this file mainly inherits its configuration from Poky. @@ -563,7 +563,7 @@ <filename>meta/recipes-bsp/</filename> - This directory contains anything linking to specific hardware or hardware + This directory contains anything linking to specific hardware or hardware configuration information such as "u-boot" and "grub". @@ -580,7 +580,7 @@ <filename>meta/recipes-core/</filename> - This directory contains what is needed to build a basic working Linux image + This directory contains what is needed to build a basic working Linux image including commonly used dependencies. @@ -598,8 +598,8 @@ <filename>meta/recipes-extended/</filename> - This directory contains non-essential applications that add features compared to the - alternatives in core. + This directory contains non-essential applications that add features compared to the + alternatives in core. You might need this directory for full tool functionality or for Linux Standard Base (LSB) compliance. @@ -625,7 +625,7 @@ <filename>meta/recipes-kernel/</filename> - This directory contains the kernel and generic applications and libraries that + This directory contains the kernel and generic applications and libraries that have strong kernel dependencies. @@ -651,7 +651,7 @@ This directory contains package and image recipes for using and testing - the PREEMPT_RT kernel. + the PREEMPT_RT kernel. @@ -668,7 +668,7 @@ <filename>meta/recipes-support/</filename> - This directory contains recipes that used by other recipes, but that are not directly + This directory contains recipes that used by other recipes, but that are not directly included in images (i.e. dependencies of other recipes). @@ -678,9 +678,9 @@ This directory contains a list of cached results for various architectures. - Because certain "autoconf" test results cannot be determined when cross-compiling due to - the tests not able to run on a live system, the information in this directory is - passed to "autoconf" for the various architectures. + Because certain "autoconf" test results cannot be determined when cross-compiling due to + the tests not able to run on a live system, the information in this directory is + passed to "autoconf" for the various architectures. @@ -694,6 +694,6 @@ - diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml index 275a7465b8..03875132cc 100644 --- a/documentation/poky-ref-manual/ref-variables.xml +++ b/documentation/poky-ref-manual/ref-variables.xml @@ -16,48 +16,48 @@ - A - B - C - D - E - F + A + B + C + D + E + F - H - I + H + I K - L - M + L + M O - P + P - R - S - T + R + S + T - W + W - A + A ALLOW_EMPTY Specifies if an output package should still be produced if it is empty. By default, BitBake does not produce empty packages. - This default behavior can cause issues when there is an - RDEPENDS or + This default behavior can cause issues when there is an + RDEPENDS or some other runtime hard-requirement on the existence of the package. - Like all package-controlling variables, you must always use them in + Like all package-controlling variables, you must always use them in conjunction with a package name override. Here is an example: @@ -69,7 +69,7 @@ AUTHOR - The email address used to contact the original author or authors in + The email address used to contact the original author or authors in order to send patches, forward bugs, etc. @@ -86,7 +86,7 @@ - + B @@ -101,7 +101,7 @@ B = ${WORKDIR}/${BPN}-{PV}/ - You can separate the (S) directory and the directory pointed to + You can separate the (S) directory and the directory pointed to by the B variable. Most autotools-based recipes support separating these directories. The build system defaults to using separate directories for gcc @@ -114,7 +114,7 @@ A list of packages not to install despite being recommended by a recipe. - Support for this variable exists only when using the + Support for this variable exists only when using the ipk packaging backend. @@ -124,50 +124,50 @@ Monitors disk space and available inodes during the build - and allows you to control the build based on these + and allows you to control the build based on these parameters. Disk space monitoring is disabled by default. To enable monitoring, add the BB_DISKMON_DIRS - variable to your conf/local.conf file found in the + variable to your conf/local.conf file found in the Build Directory. Use the following form: BB_DISKMON_DIRS = "<action>,<dir>,<threshold> [...]" - + where: <action> is: ABORT: Immediately abort the build when a threshold is broken. STOPTASKS: Stop the build after the currently - executing tasks have finished when + executing tasks have finished when a threshold is broken. - WARN: Issue a warning but continue the + WARN: Issue a warning but continue the build when a threshold is broken. - Subsequent warnings are issued as - defined by the + Subsequent warnings are issued as + defined by the BB_DISKMON_WARNINTERVAL variable, - which must be defined in the + which must be defined in the conf/local.conf file. <dir> is: - Any directory you choose. You can specify one or - more directories to monitor by separating the - groupings with a space. If two directories are + Any directory you choose. You can specify one or + more directories to monitor by separating the + groupings with a space. If two directories are on the same device, only the first directory is monitored. <threshold> is: - Either the minimum available disk space, - the minimum number of free inodes, or - both. You must specify at least one. To + Either the minimum available disk space, + the minimum number of free inodes, or + both. You must specify at least one. To omit one or the other, simply omit the value. - Specify the threshold using G, M, K for Gbytes, - Mbytes, and Kbytes, respectively. If you do - not specify G, M, or K, Kbytes is assumed by + Specify the threshold using G, M, K for Gbytes, + Mbytes, and Kbytes, respectively. If you do + not specify G, M, or K, Kbytes is assumed by default. Do not use GB, MB, or KB. @@ -179,36 +179,36 @@ BB_DISKMON_DIRS = "STOPTASKS,${TMPDIR},1G" BB_DISKMON_DIRS = "ABORT,${TMPDIR},,100K" - The first example works only if you also provide + The first example works only if you also provide the BB_DISKMON_WARNINTERVAL variable in the conf/local.conf. This example causes the build system to immediately abort when either the disk space in ${TMPDIR} drops below 1 Gbyte or the available free inodes drops below 100 Kbytes. - Because two directories are provided with the variable, the - build system also issue a - warning when the disk space in the + Because two directories are provided with the variable, the + build system also issue a + warning when the disk space in the ${SSTATE_DIR} directory drops below 1 Gbyte or the number of free inodes drops below 100 Kbytes. - Subsequent warnings are issued during intervals as + Subsequent warnings are issued during intervals as defined by the BB_DISKMON_WARNINTERVAL variable. - The second example stops the build after all currently + The second example stops the build after all currently executing tasks complete when the minimum disk space - in the ${TMPDIR} directory drops - below 1 Gbyte. - No disk monitoring occurs for the free inodes in this case. + in the ${TMPDIR} directory drops + below 1 Gbyte. + No disk monitoring occurs for the free inodes in this case. - The final example immediately aborts the build when the + The final example immediately aborts the build when the number of free inodes in the ${TMPDIR} directory - drops below 100 Kbytes. + drops below 100 Kbytes. No disk space monitoring for the directory itself occurs in this case. @@ -219,26 +219,26 @@ Defines the disk space and free inode warning intervals. - To set these intervals, define the variable in your - conf/local.conf file in the + To set these intervals, define the variable in your + conf/local.conf file in the Build Directory. - If you are going to use the - BB_DISKMON_WARNINTERVAL variable, you must - also use the + If you are going to use the + BB_DISKMON_WARNINTERVAL variable, you must + also use the BB_DISKMON_DIRS variable and define its action as "WARN". - During the build, subsequent warnings are issued each time - disk space or number of free inodes further reduces by + During the build, subsequent warnings are issued each time + disk space or number of free inodes further reduces by the respective interval. If you do not provide a BB_DISKMON_WARNINTERVAL - variable and you do use BB_DISKMON_DIRS with - the "WARN" action, the disk monitoring interval defaults to + variable and you do use BB_DISKMON_DIRS with + the "WARN" action, the disk monitoring interval defaults to the following: BB_DISKMON_WARNINTERVAL = "50M,5K" @@ -246,22 +246,22 @@ - When specifying the variable in your configuration file, + When specifying the variable in your configuration file, use the following form: BB_DISKMON_WARNINTERVAL = "<disk_space_interval>,<disk_inode_interval>" - + where: <disk_space_interval> is: - An interval of memory expressed in either - G, M, or K for Gbytes, Mbytes, or Kbytes, - respectively. You cannot use GB, MB, or KB. + An interval of memory expressed in either + G, M, or K for Gbytes, Mbytes, or Kbytes, + respectively. You cannot use GB, MB, or KB. <disk_inode_interval> is: An interval of free inodes expressed in either - G, M, or K for Gbytes, Mbytes, or Kbytes, - respectively. You cannot use GB, MB, or KB. + G, M, or K for Gbytes, Mbytes, or Kbytes, + respectively. You cannot use GB, MB, or KB. @@ -271,12 +271,12 @@ BB_DISKMON_DIRS = "WARN,${SSTATE_DIR},1G,100K" BB_DISKMON_WARNINTERVAL = "50M,5K" - These variables cause the OpenEmbedded build system to - issue subsequent warnings each time the available - disk space further reduces by 50 Mbytes or the number - of free inodes further reduces by 5 Kbytes in the + These variables cause the OpenEmbedded build system to + issue subsequent warnings each time the available + disk space further reduces by 50 Mbytes or the number + of free inodes further reduces by 5 Kbytes in the ${SSTATE_DIR} directory. - Subsequent warnings based on the interval occur each time + Subsequent warnings based on the interval occur each time a respective interval is reached beyond the intial warning (i.e. 1 Gbytes and 100 Kbytes). @@ -310,24 +310,24 @@ BBMASK Prevents BitBake from processing recipes and recipe append files. - You can use the BBMASK variable to "hide" + You can use the BBMASK variable to "hide" these .bb and .bbappend files. BitBake ignores any recipe or recipe append files that match the expression. It is as if BitBake does not see them at all. - Consequently, matching files are not parsed or otherwise used by + Consequently, matching files are not parsed or otherwise used by BitBake. The value you provide is passed to python's regular expression compiler. - For complete syntax information, see python's documentation at + For complete syntax information, see python's documentation at . - The expression is compared against the full paths to the files. + The expression is compared against the full paths to the files. For example, the following uses a complete regular expression to tell - BitBake to ignore all recipe and recipe append files in the + BitBake to ignore all recipe and recipe append files in the .*/meta-ti/recipes-misc/ directory: BBMASK = ".*/meta-ti/recipes-misc/" - Use the BBMASK variable from within the - conf/local.conf file found + Use the BBMASK variable from within the + conf/local.conf file found in the Build Directory. @@ -342,9 +342,9 @@ BBFILE_COLLECTIONS - Lists the names of configured layers. + Lists the names of configured layers. These names are used to find the other BBFILE_* - variables. + variables. Typically, each layer will append its name to this variable in its conf/layer.conf file. @@ -353,9 +353,9 @@ BBFILE_PATTERN - Variable that expands to match files from BBFILES in a particular layer. - This variable is used in the conf/layer.conf file and must - be suffixed with the name of the specific layer (e.g. + Variable that expands to match files from BBFILES in a particular layer. + This variable is used in the conf/layer.conf file and must + be suffixed with the name of the specific layer (e.g. BBFILE_PATTERN_emenlow). @@ -364,21 +364,21 @@ Assigns the priority for recipe files in each layer. This variable is useful in situations where the same recipe appears in - more than one layer. + more than one layer. Setting this variable allows you to prioritize a layer against other layers that contain the same recipe - effectively - letting you control the precedence for the multiple layers. + letting you control the precedence for the multiple layers. The precedence established through this variable stands regardless of a - recipe's version (PV variable). - For example, a layer that has a recipe with a higher PV value but for - which the BBFILE_PRIORITY is set to have a lower precedence still has a + recipe's version (PV variable). + For example, a layer that has a recipe with a higher PV value but for + which the BBFILE_PRIORITY is set to have a lower precedence still has a lower precedence. A larger value for the BBFILE_PRIORITY variable results in a higher - precedence. - For example, the value 6 has a higher precedence than the value 5. + precedence. + For example, the value 6 has a higher precedence than the value 5. If not specified, the BBFILE_PRIORITY variable is set based on layer dependencies (see the - LAYERDEPENDS variable for + LAYERDEPENDS variable for more information. The default priority, if unspecified for a layer with no dependencies, is the lowest defined priority + 1 @@ -398,7 +398,7 @@ BBPATH - Used by BitBake to locate .bbclass and configuration files. + Used by BitBake to locate .bbclass and configuration files. This variable is analogous to the PATH variable. @@ -411,9 +411,9 @@ BBLAYERS - Lists the layers to enable during the build. - This variable is defined in the bblayers.conf configuration - file in the Build Directory. + Lists the layers to enable during the build. + This variable is defined in the bblayers.conf configuration + file in the Build Directory. Here is an example: BBLAYERS = " \ @@ -428,7 +428,7 @@ /home/scottrif/poky/meta-yocto \ " - This example enables four layers, one of which is a custom, user-defined layer + This example enables four layers, one of which is a custom, user-defined layer named meta-mykernel. @@ -464,7 +464,7 @@ Core layer for images cannot be removed BP - The base recipe name and version but without any special + The base recipe name and version but without any special recipe name suffix (i.e. -native, lib64-, and so forth). BP is comprised of the following: @@ -495,8 +495,8 @@ Core layer for images cannot be removed CFLAGS - Flags passed to C compiler for the target system. - This variable evaluates to the same as + Flags passed to C compiler for the target system. + This variable evaluates to the same as TARGET_CFLAGS. @@ -504,7 +504,7 @@ Core layer for images cannot be removed COMBINED_FEATURES - A set of features common between + A set of features common between MACHINE_FEATURES and DISTRO_FEATURES. See the glossary descriptions for these variables for more information. @@ -513,11 +513,11 @@ Core layer for images cannot be removed COMPATIBLE_MACHINE - A regular expression which evaluates to match the machines the recipe - works with. - It stops recipes being run on machines for which they are not compatible. - This is particularly useful with kernels. - It also helps to increase parsing speed as further parsing of the recipe is skipped + A regular expression which evaluates to match the machines the recipe + works with. + It stops recipes being run on machines for which they are not compatible. + This is particularly useful with kernels. + It also helps to increase parsing speed as further parsing of the recipe is skipped if it is found the current machine is not compatible. @@ -527,46 +527,46 @@ Core layer for images cannot be removed Identifies editable or configurable files that are part of a package. If the Package Management System (PMS) is being used to update - packages on the target system, it is possible that + packages on the target system, it is possible that configuration files you have changed after the original installation and that you now want to remain unchanged are overwritten. - In other words, editable files might exist in the package that you do not + In other words, editable files might exist in the package that you do not want reset as part of the package update process. - You can use the CONFFILES variable to list the files in the + You can use the CONFFILES variable to list the files in the package that you wish to prevent the PMS from overwriting during this update process. - + To use the CONFFILES variable, provide a package name override that identifies the resulting package. Then, provide a space-separated list of files. Here is an example: - + CONFFILES_${PN} += "${sysconfdir}/file1 \ ${sysconfdir}/file2 ${sysconfdir}/file3" - A relationship exists between the CONFFILES and + A relationship exists between the CONFFILES and FILES variables. - The files listed within CONFFILES must be a subset of + The files listed within CONFFILES must be a subset of the files listed within FILES. - Because the configuration files you provide with CONFFILES - are simply being identified so that the PMS will not overwrite them, + Because the configuration files you provide with CONFFILES + are simply being identified so that the PMS will not overwrite them, it makes sense that - the files must already be included as part of the package through the + the files must already be included as part of the package through the FILES variable. - When specifying paths as part of the CONFFILES variable, - it is good practice to use appropriate path variables. - For example, ${sysconfdir} rather than - /etc or ${bindir} rather + When specifying paths as part of the CONFFILES variable, + it is good practice to use appropriate path variables. + For example, ${sysconfdir} rather than + /etc or ${bindir} rather than /usr/bin. - You can find a list of these variables at the top of the - /meta/conf/bitbake.conf file in the + You can find a list of these variables at the top of the + /meta/conf/bitbake.conf file in the Source Directory. @@ -575,9 +575,9 @@ Core layer for images cannot be removed CONFIG_SITE - A list of files that contains autoconf test results relevant - to the current build. - This variable is used by the Autotools utilities when running + 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. @@ -586,9 +586,9 @@ Core layer for images cannot be removed CORE_IMAGE_EXTRA_INSTALL - Specifies the list of packages to be added to the image. + Specifies the list of packages to be added to the image. This variable should only be set in the local.conf - configuration file found in the + configuration file found in the Build Directory. @@ -611,9 +611,9 @@ Core layer for images cannot be removed DEBUG_BUILD - Specifies to build packages with debugging information. - This influences the value of the - SELECTED_OPTIMIZATION + Specifies to build packages with debugging information. + This influences the value of the + SELECTED_OPTIMIZATION variable. @@ -622,9 +622,9 @@ Core layer for images cannot be removed DEBUG_OPTIMIZATION - The options to pass in + The options to pass in TARGET_CFLAGS - and CFLAGS when compiling + and CFLAGS when compiling a system for debugging. This variable defaults to "-O -fno-omit-frame-pointer -g". @@ -641,9 +641,9 @@ Core layer for images cannot be removed Lists a recipe's build-time dependencies - (i.e. other recipe files). - The system ensures that all the dependencies listed - have been built and have their contents in the appropriate + (i.e. other recipe files). + The system ensures that all the dependencies listed + have been built and have their contents in the appropriate sysroots before the recipe's configure task is executed. @@ -652,8 +652,8 @@ Core layer for images cannot be removed DESCRIPTION The package description used by package managers. - If not set, DESCRIPTION takes - the value of the + If not set, DESCRIPTION takes + the value of the SUMMARY variable. @@ -669,11 +669,11 @@ Core layer for images cannot be removed DISTRO - The short name of the distribution. + The short name of the distribution. This variable corresponds to a file with the extension .conf located in a conf/distro directory - within the metadata that contains the distribution configuration. + within the metadata that contains the distribution configuration. The value must not contain spaces, and is typically all lower-case. @@ -689,11 +689,11 @@ Core layer for images cannot be removed Specifies a list of distro-specific packages to add to all images. - This variable takes affect through - packagegroup-base so the - variable only really applies to the more full-featured + This variable takes affect through + packagegroup-base so the + variable only really applies to the more full-featured images that include packagegroup-base. - You can use this variable to keep distro policy out of + You can use this variable to keep distro policy out of generic images. As with all other distro variables, you set this variable in the distro .conf file. @@ -704,10 +704,10 @@ Core layer for images cannot be removed DISTRO_EXTRA_RRECOMMENDS - Specifies a list of distro-specific packages to add to all images - if the packages exist. + Specifies a list of distro-specific packages to add to all images + if the packages exist. The packages might not exist or be empty (e.g. kernel modules). - The list of packages are automatically installed but can be + The list of packages are automatically installed but can be removed by the user. @@ -725,18 +725,18 @@ Core layer for images cannot be removed DISTRO_FEATURES_BACKFILL - Features to be added to + Features to be added to DISTRO_FEATURES - if not also present in + if not also present in DISTRO_FEATURES_BACKFILL_CONSIDERED. This variable is set in the meta/conf/bitbake.conf file. - It is not intended to be user-configurable. - It is best to just reference the variable to see which distro features are + It is not intended to be user-configurable. + It is best to just reference the variable to see which distro features are being backfilled for all distro configurations. - See the Feature backfilling section for + See the Feature backfilling section for more information. @@ -749,7 +749,7 @@ Core layer for images cannot be removed that should not backfilled (i.e. added to DISTRO_FEATURES) during the build. - See the "Feature Backfilling" section for + See the "Feature Backfilling" section for more information. @@ -764,9 +764,9 @@ Core layer for images cannot be removed DISTRO_PN_ALIAS Alias names used for the recipe in various Linux distributions. - See the + See the "Handling - a Package Name Alias" section in the Yocto Project Development + a Package Name Alias" section in the Yocto Project Development Manual for more information. @@ -784,8 +784,8 @@ Core layer for images cannot be removed You can set this directory by defining the DL_DIR variable in the /conf/local.conf file. This directory is self-maintaining and you should not have - to touch it. - By default, the directory is downloads in the + to touch it. + By default, the directory is downloads in the Build Directory. #DL_DIR ?= "${TOPDIR}/downloads" @@ -795,22 +795,22 @@ Core layer for images cannot be removed - During a first build, the system downloads many different source code - tarballs from various upstream projects. + During a first build, the system downloads many different source code + tarballs from various upstream projects. Downloading can take a while, particularly if your network - connection is slow. - Tarballs are all stored in the directory defined by - DL_DIR and the build system looks there first - to find source tarballs. + connection is slow. + Tarballs are all stored in the directory defined by + DL_DIR and the build system looks there first + to find source tarballs. - When wiping and rebuilding, you can preserve this directory to speed - up this part of subsequent builds. + When wiping and rebuilding, you can preserve this directory to speed + up this part of subsequent builds. - You can safely share this directory between multiple builds on the - same development machine. + You can safely share this directory between multiple builds on the + same development machine. For additional information on how the build process gets source files when working behind a firewall or proxy server, see the "FAQ" @@ -836,15 +836,15 @@ Core layer for images cannot be removed Used with file and pathnames to create a prefix for a recipe's - version based on the 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 (e.g if + EXTENDPE becomes that value (e.g if PE is equal to "1" then EXTENDPE - becomes "1_"). - If a recipe's PE is not set (the default) or is equal to + becomes "1_"). + If a recipe's PE is not set (the default) or is equal to zero, EXTENDPE becomes "". - See the STAMP + See the STAMP variable for an example. @@ -855,38 +855,38 @@ Core layer for images cannot be removed Allows extra packages to be added to the generated images. You set this variable in the local.conf configuration file. - Note that some image features are also added using the + Note that some image features are also added using the IMAGE_FEATURES variable generally configured in image recipes. You can use this variable to add more features in addition to those. Here are some examples of features you can add: "dbg-pkgs" - Adds -dbg packages for all installed packages - including symbol information for debugging and + including symbol information for debugging and profiling. -"dev-pkgs" - Adds -dev packages for all installed packages. - This is useful if you want to develop against +"dev-pkgs" - Adds -dev packages for all installed packages. + This is useful if you want to develop against the libraries in the image. -"tools-sdk" - Adds development tools such as gcc, make, +"tools-sdk" - Adds development tools such as gcc, make, pkgconfig and so forth. -"tools-debug" - Adds debugging tools such as gdb and +"tools-debug" - Adds debugging tools such as gdb and strace. -"tools-profile" - Adds profiling tools such as oprofile, +"tools-profile" - Adds profiling tools such as oprofile, exmap, lttng and valgrind (x86 only). -"tools-testapps" - Adds useful testing tools such as - ts_print, aplay, arecord and so +"tools-testapps" - Adds useful testing tools such as + ts_print, aplay, arecord and so forth. -"debug-tweaks" - Makes an image suitable for development. - For example, ssh root access has a blank - password. You should remove this feature - before you produce a production image. - +"debug-tweaks" - Makes an image suitable for development. + For example, ssh root access has a blank + password. You should remove this feature + before you produce a production image. + There are other valid features too, see the Images @@ -901,12 +901,12 @@ Core layer for images cannot be removed Sometimes a recipe is required to build the final image but is not needed in the root filesystem. - You can use the EXTRA_IMAGEDEPENDS variable to - list these recipes and thus, specify the dependencies. + You can use the EXTRA_IMAGEDEPENDS variable to + list these recipes and thus, specify the dependencies. A typical example is a required bootloader in a machine configuration. - To add packages to the root filesystem, see the various + To add packages to the root filesystem, see the various *DEPENDS and *RECOMMENDS variables. @@ -944,32 +944,32 @@ Core layer for images cannot be removed To use the FILES variable, provide a package name override that identifies the resulting package. - Then, provide a space-separated list of files or paths that identifies the + Then, provide a space-separated list of files or paths that identifies the files you want included as part of the resulting package. Here is an example: - + FILES_${PN} += "${bindir}/mydir1/ ${bindir}/mydir2/myfile" - When specifying paths as part of the FILES variable, - it is good practice to use appropriate path variables. - For example, ${sysconfdir} rather than - /etc or ${bindir} rather + When specifying paths as part of the FILES variable, + it is good practice to use appropriate path variables. + For example, ${sysconfdir} rather than + /etc or ${bindir} rather than /usr/bin. - You can find a list of these variables at the top of the - /meta/conf/bitbake.conf file in the + You can find a list of these variables at the top of the + /meta/conf/bitbake.conf file in the Source Directory. If some of the files you provide with the FILES variable - are editable and you know they should not be + are editable and you know they should not be overwritten during the package update process by the Package Management - System (PMS), you can identify these files so that the PMS will not - overwrite them. - See the CONFFILES + System (PMS), you can identify these files so that the PMS will not + overwrite them. + See the CONFFILES variable for information on how to identify these files to the PMS. @@ -979,11 +979,11 @@ Core layer for images cannot be removed FILESEXTRAPATHS - Extends the search path the OpenEmbedded build system uses when - looking for files and patches as it processes recipes. + Extends the search path the OpenEmbedded build system uses when + looking for files and patches as it processes recipes. The directories BitBake uses when it processes recipes is defined by the - FILESPATH variable. - You can add directories to the search path by defining the + FILESPATH variable. + You can add directories to the search path by defining the FILESEXTRAPATHS variable. @@ -993,17 +993,17 @@ Core layer for images cannot be removed FILESEXTRAPATHS_prepend := "path_1:path_2:path_3:" - Typically, you want your directories searched first. - To make sure that happens, use _prepend and - the immediate expansion (:=) operator as shown in the + Typically, you want your directories searched first. + To make sure that happens, use _prepend and + the immediate expansion (:=) operator as shown in the previous example. - Finally, to maintain the integrity of the FILESPATH variable, + Finally, to maintain the integrity of the FILESPATH variable, you must include the appropriate beginning or ending (as needed) colon character. - The FILESEXTRAPATHS variable is intended for use in - .bbappend files to include any additional files provided in that layer. + The FILESEXTRAPATHS variable is intended for use in + .bbappend files to include any additional files provided in that layer. You typically accomplish this with the following: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" @@ -1017,15 +1017,15 @@ Core layer for images cannot be removed The default set of directories the OpenEmbedded build system uses when searching for patches and files. - During the build process, BitBake searches each directory in - FILESPATH in the specified order when looking for + During the build process, BitBake searches each directory in + FILESPATH in the specified order when looking for files and patches specified by each file:// URI in a recipe. The default value for the FILESPATH variable is defined - in the base.bbclass class found in - meta/classes in the + in the base.bbclass class found in + meta/classes in the Source Directory: FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ @@ -1033,9 +1033,9 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ "${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", \ "${FILE_DIRNAME}/files", "${FILE_DIRNAME}" ], d)}" - Do not hand-edit the FILESPATH variable. - If you want to extend the set of pathnames that BitBake uses when searching for - files and patches, use the + Do not hand-edit the FILESPATH variable. + If you want to extend the set of pathnames that BitBake uses when searching for + files and patches, use the FILESEXTRAPATHS variable. @@ -1045,29 +1045,29 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ Allows you to define your own file permissions settings table as part of your configuration for the packaging process. - For example, suppose you need a consistent set of custom permissions for + For example, suppose you need a consistent set of custom permissions for a set of groups and users across an entire work project. - It is best to do this in the packages themselves but this is not always + It is best to do this in the packages themselves but this is not always possible. By default, the OpenEmbedded build system uses the fs-perms.txt, which - is located in the meta/files folder in the + is located in the meta/files folder in the Source Directory. If you create your own file permissions setting table, you should place it in your - layer or the distros layer. + layer or the distros layer. - You define the FILESYSTEM_PERMS_TABLES variable in the - conf/local.conf file, which is found in the - Build Directory, to + You define the FILESYSTEM_PERMS_TABLES variable in the + conf/local.conf file, which is found in the + Build Directory, to point to your custom fs-perms.txt. You can specify more than a single file permissions setting table. - The paths you specify to these files must be defined within the - BBPATH variable. + The paths you specify to these files must be defined within the + BBPATH variable. - For guidance on how to create your own file permissions settings table file, + For guidance on how to create your own file permissions settings table file, examine the existing fs-perms.txt. @@ -1076,11 +1076,11 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ FULL_OPTIMIZATION - The options to pass in + The options to pass in TARGET_CFLAGS and CFLAGS when compiling an optimized system. - This variable defaults to + This variable defaults to "-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2". @@ -1110,7 +1110,7 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ Typically, you configure this variable in an image recipe. Note that you can also add extra features to the image by using the EXTRA_IMAGE_FEATURES variable. - See the "Images" section for the + See the "Images" section for the full list of features that can be included in images built by the OpenEmbedded build system. @@ -1131,28 +1131,28 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ - Image recipes set IMAGE_INSTALL to specify the + Image recipes set IMAGE_INSTALL to specify the packages to install into an image through image.bbclass. Additionally, "helper" classes exist, such as core-image.bbclass, - that can take + that can take IMAGE_FEATURES lists - and turn these into auto-generated entries in + and turn these into auto-generated entries in IMAGE_INSTALL in addition to its default contents. Using IMAGE_INSTALL with the += - operator from the /conf/local.conf file or from within - an image recipe is not recommended as it can cause ordering issues. - Since core-image.bbclass sets IMAGE_INSTALL - to a default value using the ?= operator, using a - += operation against IMAGE_INSTALL - will result in unexpected behavior when used in + operator from the /conf/local.conf file or from within + an image recipe is not recommended as it can cause ordering issues. + Since core-image.bbclass sets IMAGE_INSTALL + to a default value using the ?= operator, using a + += operation against IMAGE_INSTALL + will result in unexpected behavior when used in /conf/local.conf. - Furthermore, the same operation from with an image recipe may or may not + Furthermore, the same operation from with an image recipe may or may not succeed depending on the specific situation. - In both these cases, the behavior is contrary to how most users expect - the += operator to work. + In both these cases, the behavior is contrary to how most users expect + the += operator to work. @@ -1171,27 +1171,27 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ 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 + for the image is greater than the sum of IMAGE_ROOTFS_SIZE - and + and IMAGE_ROOTFS_EXTRA_SPACE. The result of the multiplier applied to the initial image size creates free disk space in the image as overhead. - By default, the build process uses a multiplier of 1.3 for this variable. - This default value results in 30% free disk space added to the image when this + By default, the build process uses a multiplier of 1.3 for this variable. + This default value results in 30% free disk space added to the image when this method is used to determine the final generated image size. You should be aware that post install scripts and the package management - system uses disk space inside this overhead area. - Consequently, the multiplier does not produce an image with - all the theoretical free disk space. + system uses disk space inside this overhead area. + Consequently, the multiplier does not produce an image with + all the theoretical free disk space. See IMAGE_ROOTFS_SIZE for information on how the build system determines the overall image size. - The default 30% free disk space typically gives the image enough room to boot - and allows for basic post installs while still leaving a small amount of - free disk space. + The default 30% free disk space typically gives the image enough room to boot + and allows for basic post installs while still leaving a small amount of + free disk space. If 30% free space is inadequate, you can increase the default value. For example, the following setting gives you 50% free space added to the image: @@ -1201,12 +1201,12 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ Alternatively, you can ensure a specific amount of free disk space is added - to the image by using + to the image by using IMAGE_ROOTFS_EXTRA_SPACE the variable. - + IMAGE_ROOTFS_EXTRA_SPACE @@ -1214,32 +1214,32 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ Defines additional free disk space created in the image in Kbytes. By default, this variable is set to "0". This free disk space is added to the image after the build system determines - the image size as described in + the image size as described in IMAGE_ROOTFS_SIZE. - This variable is particularly useful when you want to ensure that a - specific amount of free disk space is available on a device after an image - is installed and running. - For example, to be sure 5 Gbytes of free disk space is available, set the + This variable is particularly useful when you want to ensure that a + specific amount of free disk space is available on a device after an image + is installed and running. + For example, to be sure 5 Gbytes of free disk space is available, set the variable as follows: IMAGE_ROOTFS_EXTRA_SPACE = "5242880" - + IMAGE_ROOTFS_SIZE Defines the size in Kbytes for the generated image. - The OpenEmbedded build system determines the final size for the generated + The OpenEmbedded build system determines the final size for the generated image using an algorithm that takes into account the initial disk space used - for the generated image, a requested size for the image, and requested + for the generated image, a requested size for the image, and requested additional free disk space to be added to the image. - Programatically, the build system determines the final size of the + Programatically, the build system determines the final size of the generated image as follows: if (image-du * overhead) < rootfs-size: @@ -1251,7 +1251,7 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ image-du = Returned value of the du command on the image. - + overhead = IMAGE_OVERHEAD_FACTOR rootfs-size = IMAGE_ROOTFS_SIZE @@ -1261,12 +1261,12 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ xspace = IMAGE_ROOTFS_EXTRA_SPACE - + variable, and du is the results of the disk usage command + on the initially generated image. --> @@ -1275,38 +1275,38 @@ FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \ Helps define the recipe revision for recipes that share a common include file. - You can think of this variable as part of the recipe revision + You can think of this variable as part of the recipe revision as set from within an include file. - Suppose, for example, you have a set of recipes that + Suppose, for example, you have a set of recipes that are used across several projects. And, within each of those recipes the revision (its PR value) is set accordingly. In this case, when the revision of those recipes changes - the burden is on you to find all those recipes and - be sure that they get changed to reflect the updated + the burden is on you to find all those recipes and + be sure that they get changed to reflect the updated version of the recipe. In this scenario, it can get complicated when recipes - used in many places and that provide common functionality + used in many places and that provide common functionality are upgraded to a new revision. A more efficient way of dealing with this situation is to set the INC_PR variable inside the include files that the recipes share and then expand the INC_PR - variable within the recipes to help + variable within the recipes to help define the recipe revision. - The following provides an example that shows how to use + The following provides an example that shows how to use the INC_PR variable - given a common include file that + given a common include file that defines the variable. - Once the variable is defined in the - include file, you can use the + Once the variable is defined in the + include file, you can use the variable to set the PR values in - each recipe. - You will notice that when you set a recipe's + each recipe. + You will notice that when you set a recipe's PR you can provide more granular - revisioning by appending values to the + revisioning by appending values to the INC_PR variable: recipes-graphics/xorg-font/xorg-font-common.inc:INC_PR = "r2" @@ -1314,8 +1314,8 @@ recipes-graphics/xorg-font/encodings_1.0.4.bb:PR = "${INC_PR}.1" recipes-graphics/xorg-font/font-util_1.3.0.bb:PR = "${INC_PR}.0" recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - The first line of the example establishes the baseline - revision to be used for all recipes that use the + The first line of the example establishes the baseline + revision to be used for all recipes that use the include file. The remaining lines in the example are from individual recipes and show how the PR value @@ -1335,8 +1335,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" INHERIT - Causes the named class to be inherited at - this point during parsing. + Causes the named class to be inherited at + this point during parsing. The variable is only valid in configuration files. @@ -1346,8 +1346,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" INITSCRIPT_PACKAGES - A list of the packages that contain initscripts. - If multiple packages are specified, you need to append the package name + A list of the packages that contain initscripts. + If multiple packages are specified, you need to append the package name to the other INITSCRIPT_* as an override. This variable is used in recipes when using update-rc.d.bbclass. @@ -1372,12 +1372,12 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Specifies the options to pass to update-rc.d. - An example is start 99 5 2 . stop 20 0 1 6 ., which gives the script a - runlevel of 99, starts the script in initlevels 2 and 5, and - stops the script in levels 0, 1 and 6. + An example is start 99 5 2 . stop 20 0 1 6 ., which gives the script a + runlevel of 99, starts the script in initlevels 2 and 5, and + stops the script in levels 0, 1 and 6. - The variable is mandatory and is used in recipes when using + The variable is mandatory and is used in recipes when using update-rc.d.bbclass. @@ -1394,36 +1394,36 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" KBRANCH - A regular expression used by the build process to explicitly identify the kernel - branch that is validated, patched and configured during a build. + A regular expression used by the build process to explicitly identify the kernel + branch that is validated, patched and configured during a build. The KBRANCH variable is optional. - You can use it to trigger checks to ensure the exact kernel branch you want is + You can use it to trigger checks to ensure the exact kernel branch you want is being used by the build process. - Values for this variable are set in the kernel's recipe file and the kernel's - append file. - For example, if you are using the Yocto Project kernel that is based on the - Linux 3.4 kernel, the kernel recipe file is the - meta/recipes-kernel/linux/linux-yocto_3.4.bb file. + Values for this variable are set in the kernel's recipe file and the kernel's + append file. + For example, if you are using the Yocto Project kernel that is based on the + Linux 3.4 kernel, the kernel recipe file is the + meta/recipes-kernel/linux/linux-yocto_3.4.bb file. Following is the default value for KBRANCH and the default override for the architectures the Yocto Project supports: KBRANCH_DEFAULT = "standard/base" KBRANCH = "${KBRANCH_DEFAULT}" - This branch exists in the linux-yocto-3.4 kernel Git - repository . + This branch exists in the linux-yocto-3.4 kernel Git + repository . - This variable is also used from the kernel's append file to identify the kernel - branch specific to a particular machine or target hardware. - The kernel's append file is located in the BSP layer for a given machine. - For example, the kernel append file for the Crown Bay BSP is in the - meta-intel Git repository and is named - meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend. + This variable is also used from the kernel's append file to identify the kernel + branch specific to a particular machine or target hardware. + The kernel's append file is located in the BSP layer for a given machine. + For example, the kernel append file for the Crown Bay BSP is in the + meta-intel Git repository and is named + meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend. Here are the related statements from the append file: COMPATIBLE_MACHINE_crownbay = "crownbay" @@ -1434,9 +1434,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" KMACHINE_crownbay-noemgd = "crownbay" KBRANCH_crownbay-noemgd = "standard/crownbay" - The KBRANCH_* statements identify the kernel branch to - use when building for the Crown Bay BSP. - In this case there are two identical statements: one for each type of + The KBRANCH_* statements identify the kernel branch to + use when building for the Crown Bay BSP. + In this case there are two identical statements: one for each type of Crown Bay machine. @@ -1446,18 +1446,18 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Includes additional metadata from the Yocto Project kernel Git repository. In the OpenEmbedded build system, the default Board Support Packages (BSPs) - metadata is provided through + metadata is provided through the KMACHINE and KBRANCH variables. - You can use the KERNEL_FEATURES variable to further + You can use the KERNEL_FEATURES variable to further add metadata for all BSPs. - The metadata you add through this variable includes config fragments and + The metadata you add through this variable includes config fragments and features descriptions, which usually includes patches as well as config fragments. You typically override the KERNEL_FEATURES variable for a specific machine. In this way, you can provide validated, but optional, sets of kernel configurations and features. - For example, the following adds netfilter to all + For example, the following adds netfilter to all the Yocto Project kernels and adds sound support to the qemux86 machine: @@ -1472,10 +1472,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" KERNEL_IMAGETYPE - The type of kernel to build for a device, usually set by the - machine configuration files and defaults to "zImage". - This variable is used - when building the kernel and is passed to make as the target to + The type of kernel to build for a device, usually set by the + machine configuration files and defaults to "zImage". + This variable is used + when building the kernel and is passed to make as the target to build. @@ -1486,22 +1486,22 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The machine as known by the kernel. Sometimes the machine name used by the kernel does not match the machine name used by the OpenEmbedded build system. - For example, the machine name that the OpenEmbedded build system understands as + For example, the machine name that the OpenEmbedded build system understands as qemuarm goes by a different name in the Linux Yocto kernel. The kernel understands that machine as arm_versatile926ejs. - For cases like these, the KMACHINE variable maps the + For cases like these, the KMACHINE variable maps the kernel machine name to the OpenEmbedded build system machine name. - Kernel machine names are initially defined in the - Yocto Linux Kernel in + Kernel machine names are initially defined in the + Yocto Linux Kernel in the meta branch. - From the meta branch, look in + From the meta branch, look in the meta/cfg/kernel-cache/bsp/<bsp_name>/<bsp-name>-<kernel-type>.scc file. - For example, from the meta branch in the - linux-yocto-3.0 kernel, the - meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-standard.scc file + For example, from the meta branch in the + linux-yocto-3.0 kernel, the + meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-standard.scc file has the following: define KMACHINE cedartrail @@ -1511,7 +1511,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" include ktypes/standard branch cedartrail - include cedartrail.scc + include cedartrail.scc You can see that the kernel understands the machine name for the Cedar Trail BSP as cedartrail. @@ -1533,14 +1533,14 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" KBRANCH_cedartrail-nopvr = "yocto/standard/cedartrail" KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc" - The KMACHINE statements in the kernel's append file make sure that - the OpenEmbedded build system and the Yocto Linux kernel understand the same machine - names. + The KMACHINE statements in the kernel's append file make sure that + the OpenEmbedded build system and the Yocto Linux kernel understand the same machine + names. This append file uses two KMACHINE statements. - The first is not really necessary but does ensure that the machine known to the + The first is not really necessary but does ensure that the machine known to the OpenEmbedded build system as cedartrail maps to the machine in the kernel also known as cedartrail: @@ -1550,12 +1550,12 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The second statement is a good example of why the KMACHINE variable - is needed. + is needed. In this example, the OpenEmbedded build system uses the cedartrail-nopvr - machine name to refer to the Cedar Trail BSP that does not support the propriatory + machine name to refer to the Cedar Trail BSP that does not support the propriatory PowerVR driver. The kernel, however, uses the machine name cedartrail. - Thus, the append file must map the cedartrail-nopvr machine name to + Thus, the append file must map the cedartrail-nopvr machine name to the kernel's cedartrail name: KMACHINE_cedartrail-nopvr = "cedartrail" @@ -1563,9 +1563,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - BSPs that ship with the Yocto Project release provide all mappings between the Yocto - Project kernel machine names and the OpenEmbedded machine names. - Be sure to use the KMACHINE if you create a BSP and the machine + BSPs that ship with the Yocto Project release provide all mappings between the Yocto + Project kernel machine names and the OpenEmbedded machine names. + Be sure to use the KMACHINE if you create a BSP and the machine name you use is different than that used in the kernel. @@ -1583,16 +1583,16 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" to be compared against LAYERVERSION_anotherlayer in this case). An error will be produced if any dependency is missing or the version numbers do not match exactly (if specified). - This variable is used in the conf/layer.conf file - and must be suffixed with the name of the specific layer (e.g. + This variable is used in the conf/layer.conf file + and must be suffixed with the name of the specific layer (e.g. LAYERDEPENDS_mylayer). LAYERDIR - When used inside the layer.conf configuration - file, this variable provides the path of the current layer. + When used inside the layer.conf configuration + file, this variable provides the path of the current layer. This variable requires immediate expansion (see the BitBake manual) as lazy expansion can result in the expansion happening in the wrong directory and therefore @@ -1605,7 +1605,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Optionally specifies the version of a layer as a single number. You can use this within LAYERDEPENDS for another layer in order to depend on a specific version of the layer. - This variable is used in the conf/layer.conf file + This variable is used in the conf/layer.conf file and must be suffixed with the name of the specific layer (e.g. LAYERVERSION_mylayer). @@ -1615,9 +1615,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Checksums of the license text in the recipe source code. This variable tracks changes in license text of the source - code files. + code files. If the license text is changed, it will trigger a build - failure, which gives the developer an opportunity to review any + failure, which gives the developer an opportunity to review any license change. This variable must be defined for all recipes (unless LICENSE @@ -1636,14 +1636,14 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Do not use spaces within individual license names. - Separate license names using + Separate license names using | (pipe) when there is a choice between licenses. - Separate license names using - & (ampersand) when multiple licenses exist - that cover different parts of the source. + Separate license names using + & (ampersand) when multiple licenses exist + that cover different parts of the source. - You can use spaces between license + You can use spaces between license names. @@ -1655,12 +1655,12 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" LICENSE = "MPL-1 & LGPLv2.1" LICENSE = "GPLv2+" - The first example is from the recipes for Qt, which the user + The first example is from the recipes for Qt, which the user may choose to distribute under either the LGPL version 2.1 or GPL version 3. The second example is from Cairo where two licenses cover - different parts of the source code. - The final example is from sysstat, + different parts of the source code. + The final example is from sysstat, which presents a single license. @@ -1669,10 +1669,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" LICENSE_PATH Path to additional licenses used during the build. - By default, the OpenEmbedded build system uses COMMON_LICENSE_DIR - to define the directory that holds common license text used during the build. + By default, the OpenEmbedded build system uses COMMON_LICENSE_DIR + to define the directory that holds common license text used during the build. The LICENSE_PATH variable allows you to extend that - location to other areas that have additional licenses: + location to other areas that have additional licenses: LICENSE_PATH += "/path/to/additional/common/licenses" @@ -1687,26 +1687,26 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Specifies the target device for which the image is built. - You define MACHINE in the - local.conf file found in the + You define MACHINE in the + local.conf file found in the Build Directory. - By default, MACHINE is set to - "qemux86", which is an x86-based architecture machine to + By default, MACHINE is set to + "qemux86", which is an x86-based architecture machine to be emulated using QEMU: MACHINE ?= "qemux86" - - The variable corresponds to a machine configuration file of the + + The variable corresponds to a machine configuration file of the same name, through which machine-specific configurations are set. Thus, when MACHINE is set to "qemux86" there exists the corresponding qemux86.conf machine - configuration file, which can be found in the + configuration file, which can be found in the Source Directory in meta/conf/machine. - + - The list of machines supported by the Yocto Project as + The list of machines supported by the Yocto Project as shipped include the following: MACHINE ?= "qemuarm" @@ -1721,10 +1721,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The last four are Yocto Project reference hardware boards, which are provided in the meta-yocto-bsp layer. - Adding additional Board Support Package (BSP) layers + Adding additional Board Support Package (BSP) layers to your configuration adds new possible settings for MACHINE. - + @@ -1736,16 +1736,16 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" A list of required machine-specific packages to install as part of the image being built. The build process depends on these packages being present. - Furthermore, because this is a "machine essential" variable, the list of + Furthermore, because this is a "machine essential" variable, the list of packages are essential for the machine to boot. - The impact of this variable affects images based on + The impact of this variable affects images based on packagegroup-core-boot, including the core-image-minimal image. - This variable is similar to the + This variable is similar to the MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS - variable with the exception that the image being built has a build + variable with the exception that the image being built has a build dependency on the variable's list of packages. In other words, the image will not build if a file in this list is not found. @@ -1768,16 +1768,16 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" A list of recommended machine-specific packages to install as part of the image being built. The build process does not depend on these packages being present. - However, because this is a "machine essential" variable, the list of + However, because this is a "machine essential" variable, the list of packages are essential for the machine to boot. - The impact of this variable affects images based on + The impact of this variable affects images based on packagegroup-core-boot, including the core-image-minimal image. - This variable is similar to the + This variable is similar to the MACHINE_ESSENTIAL_EXTRA_RDEPENDS - variable with the exception that the image being built does not have a build + variable with the exception that the image being built does not have a build dependency on the variable's list of packages. In other words, the image will still build if a package in this list is not found. Typically, this variable is used to handle essential kernel modules, whose @@ -1790,20 +1790,20 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" However, the driver can be built as a module or into the kernel depending on the kernel configuration. If the driver is built as a module, you want it to be installed. - But, when the driver is built into the kernel, you still want the + But, when the driver is built into the kernel, you still want the build to succeed. This variable sets up a "recommends" relationship so that in the latter case, the build will not fail due to the missing package. To accomplish this, assuming the package for the module was called kernel-module-ab123, you would use the - following in the machine's .conf configuration + following in the machine's .conf configuration file: MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-ab123" - Some examples of these machine essentials are flash, screen, keyboard, mouse, + Some examples of these machine essentials are flash, screen, keyboard, mouse, or touchscreen drivers (depending on the machine). @@ -1812,21 +1812,21 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" MACHINE_EXTRA_RDEPENDS - A list of machine-specific packages to install as part of the + 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 + However, the build process for more fully-featured images depends on the packages being present. This variable affects all images based on - packagegroup-base, which does not include the - core-image-minimal or core-image-basic + packagegroup-base, which does not include the + core-image-minimal or core-image-basic images. - The variable is similar to the + The variable is similar to the MACHINE_EXTRA_RRECOMMENDS - variable with the exception that the image being built has a build + variable with the exception that the image being built has a build dependency on the variable's list of packages. In other words, the image will not build if a file in this list is not found. @@ -1834,8 +1834,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" An example is a machine that has WiFi capability but is not essential For the machine to boot the image. However, if you are building a more fully-featured image, you want to enable - the WiFi. - The package containing the firmware for the WiFi hardware is always + the WiFi. + The package containing the firmware for the WiFi hardware is always expected to exist, so it is acceptable for the build process to depend upon finding the package. In this case, assuming the package for the firmware was called @@ -1852,20 +1852,20 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - A list of machine-specific packages to install as part of the + 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 dependency on this list of packages. - This variable affects only images based on - packagegroup-base, which does not include the - core-image-minimal or core-image-basic + This variable affects only images based on + packagegroup-base, which does not include the + core-image-minimal or core-image-basic images. - This variable is similar to the + This variable is similar to the MACHINE_EXTRA_RDEPENDS - variable with the exception that the image being built does not have a build + variable with the exception that the image being built does not have a build dependency on the variable's list of packages. In other words, the image will build if a file in this list is not found. @@ -1873,7 +1873,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" An example is a machine that has WiFi capability but is not essential For the machine to boot the image. However, if you are building a more fully-featured image, you want to enable - WiFi. + WiFi. In this case, the package containing the WiFi kernel module will not be produced if the WiFi driver is built into the kernel, in which case you still want the build to succeed instead of failing as a result of the package not being found. @@ -1889,19 +1889,19 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" MACHINE_FEATURES - Specifies the list of hardware features the + Specifies the list of hardware features the MACHINE supports. - For example, including the "bluetooth" feature causes the - bluez bluetooth daemon to be built and + For example, including the "bluetooth" feature causes the + bluez bluetooth daemon to be built and added to the image. - It also causes the connman recipe + It also causes the connman recipe to look at MACHINE_FEATURES and when it - finds "bluetooth" there it enables the bluetooth + finds "bluetooth" there it enables the bluetooth support in ConnMan. - For a list of features supported by the Yocto Project as shipped, + For a list of features supported by the Yocto Project as shipped, see the "Machine" section. @@ -1909,18 +1909,18 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" MACHINE_FEATURES_BACKFILL - Features to be added to + Features to be added to MACHINE_FEATURES - if not also present in + if not also present in MACHINE_FEATURES_BACKFILL_CONSIDERED. This variable is set in the meta/conf/bitbake.conf file. - It is not intended to be user-configurable. - It is best to just reference the variable to see which machine features are + It is not intended to be user-configurable. + It is best to just reference the variable to see which machine features are being backfilled for all machine configurations. - See the Feature backfilling section for + See the Feature backfilling section for more information. @@ -1933,7 +1933,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" that should not be backfilled (i.e. added to MACHINE_FEATURES) during the build. - See the Feature backfilling section for + See the Feature backfilling section for more information. @@ -1949,13 +1949,13 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Specifies a prefix has been added to - PN to create a special version + PN to create a special version of a recipe or package, such as a multilib version. - The variable is used in places where the prefix needs to be + The variable is used in places where the prefix needs to be added to or removed from a the name (e.g. the BPN variable). - MLPREFIX gets set when a prefix has been - added to PN. + MLPREFIX gets set when a prefix has been + added to PN. @@ -1981,17 +1981,17 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" OE_TERMINAL - Controls how the OpenEmbedded build system spawns + Controls how the OpenEmbedded build system spawns interactive terminals on the host development system - (e.g. using the BitBake command with the + (e.g. using the BitBake command with the -c devshell command-line option). - For more information, see the + For more information, see the "Using a Development Shell" section in the Yocto Project Development Manual. - + - You can use the following values for the + You can use the following values for the OE_TERMINAL variable: auto @@ -2000,10 +2000,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" rxvt screen konsole - none + none Konsole support only works for KDE 3.x. - Also, "auto" is the default behavior for + Also, "auto" is the default behavior for OE_TERMINAL @@ -2030,9 +2030,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PACKAGE_BEFORE_PN - Enables easily adding packages to + Enables easily adding packages to PACKAGES - before ${PN} so that the packages can pick + before ${PN} so that the packages can pick up files that would normally be included in the default package. @@ -2040,15 +2040,15 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PACKAGE_CLASSES This variable, which is set in the local.conf configuration - file found in the conf folder of the + file found in the conf folder of the Source Directory, specifies the package manager to use when packaging data. - You can provide one or more arguments for the variable with the first + You can provide one or more arguments for the variable with the first argument being the package manager used to create images: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" - For information on build performance effects as a result of the + For information on build performance effects as a result of the package manager use, see Packaging - package*.bbclass in this manual. @@ -2067,33 +2067,33 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PACKAGECONFIG - This variable provides a means of enabling or disabling - features of a recipe on a per-recipe basis. + This variable provides a means of enabling or disabling + features of a recipe on a per-recipe basis. The PACKAGECONFIG - variable itself specifies a space-separated list of the + variable itself specifies a space-separated list of the features to enable. - The features themselves are specified as flags on the + The features themselves are specified as flags on the PACKAGECONFIG variable. You can provide up to four arguments, which are separated by - commas, to determine the behavior of each feature + commas, to determine the behavior of each feature when it is enabled or disabled. - You can omit any argument you like but must retain the + You can omit any argument you like but must retain the separating commas. The arguments specify the following: - Extra arguments - that should be added to the configure script argument list + Extra arguments + that should be added to the configure script argument list (EXTRA_OECONF) if the feature is enabled. - Extra arguments + Extra arguments that should be added to EXTRA_OECONF if the feature is disabled. - Additional build dependencies + Additional build dependencies (DEPENDS) that should be added if the feature is enabled. - Additional runtime dependencies + Additional runtime dependencies (RDEPENDS) that should be added if the feature is enabled. @@ -2101,25 +2101,25 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - Consider the following example taken from the + Consider the following example taken from the librsvg recipe. - In this example the feature is croco, which + In this example the feature is croco, which has three arguments that determine the feature's behavior. PACKAGECONFIG ??= "croco" PACKAGECONFIG[croco] = "--with-croco,--without-croco,libcroco" - The --with-croco and - libcroco arguments apply only if + The --with-croco and + libcroco arguments apply only if the feature is enabled. - In this case, --with-croco is - added to the configure script argument list and - libcroco is added to + In this case, --with-croco is + added to the configure script argument list and + libcroco is added to DEPENDS. On the other hand, if the feature is disabled say through a .bbappend file in another layer, then - the second argument --without-croco is - added to the configure script rather than + the second argument --without-croco is + added to the configure script rather than --with-croco. @@ -2138,29 +2138,29 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PACKAGES_DYNAMIC - A promise that your recipe satisfies runtime dependencies + A promise that your recipe satisfies runtime dependencies for optional modules that are found in other recipes. PACKAGES_DYNAMIC - does not actually satisfy the dependencies, it only states that - they should be satisfied. - For example, if a hard, runtime dependency - (RDEPENDS) of another package is satisfied + does not actually satisfy the dependencies, it only states that + they should be satisfied. + For example, if a hard, runtime dependency + (RDEPENDS) of another package is satisfied at build time through the PACKAGES_DYNAMIC - variable, but a package with the module name is never actually + variable, but a package with the module name is never actually produced, then the other package will be broken. Thus, if you attempt to include that package in an image, - you will get a dependency failure from the packaging system - during do_rootfs. + you will get a dependency failure from the packaging system + during do_rootfs. Typically, if there is a chance that such a situation can - occur and the package that is not created is valid - without the dependency being satisfied, then you should use - RRECOMMENDS (a soft runtime dependency) + occur and the package that is not created is valid + without the dependency being satisfied, then you should use + RRECOMMENDS (a soft runtime dependency) instead of RDEPENDS. - + For an example of how to use the PACKAGES_DYNAMIC - variable when you are splitting packages, see the + variable when you are splitting packages, see the "Handling Optional Module Packaging" section in the Yocto Project Development Manual. @@ -2169,11 +2169,11 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PARALLEL_MAKE - Specifies extra options that are passed to the make command during the - compile tasks. + 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. - If you development host supports multiple cores a good rule of thumb is to set + If you development host supports multiple cores a good rule of thumb is to set this variable to twice the number of cores on the host. @@ -2194,21 +2194,21 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" This variable can have two separate functions depending on the context: a recipe name or a resulting package name. - PN refers to a recipe name in the context of a file used + PN refers to a recipe name in the context of a file used by the OpenEmbedded build system as input to create a package. The name is normally extracted from the recipe file name. - For example, if the recipe is named + For example, if the recipe is named expat_2.0.1.bb, then the default value of PN will be "expat". - + The variable refers to a package name in the context of a file created or produced by the OpenEmbedded build system. - If applicable, the PN variable also contains any special + If applicable, the PN variable also contains any special suffix or prefix. For example, using bash to build packages for the native machine, PN is bash-native. Using bash to build packages for the target and for Multilib, - PN would be bash and + PN would be bash and lib64-bash, respectively. @@ -2216,7 +2216,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PR - The revision of the recipe. + The revision of the recipe. The default value for this variable is "r0". @@ -2224,10 +2224,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PRINC - Causes the PR variable of + Causes the PR variable of .bbappend files to dynamically increment. This increment minimizes the impact of layer ordering. - In order to ensure multiple .bbappend files can co-exist, + In order to ensure multiple .bbappend files can co-exist, PRINC should be self referencing. This variable defaults to 0. Following is an example that increments PR by two: @@ -2235,8 +2235,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PRINC := "${@int(PRINC) + 2}" It is adviseable not to use strings such as ".= '.1'" with the variable because - this usage is very sensitive to layer ordering. - Explicit assignments should be avoided as they cannot adequately represent multiple + this usage is very sensitive to layer ordering. + Explicit assignments should be avoided as they cannot adequately represent multiple .bbappend files. @@ -2245,11 +2245,11 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The version of the recipe. The version is normally extracted from the recipe filename. - For example, if the recipe is named - expat_2.0.1.bb, then the default value of PV - will be "2.0.1". - PV is generally not overridden within - a recipe unless it is building an unstable (i.e. development) version from a source code repository + For example, if the recipe is named + expat_2.0.1.bb, then the default value of PV + will be "2.0.1". + PV is generally not overridden within + a recipe unless it is building an unstable (i.e. development) version from a source code repository (e.g. Git or Subversion). @@ -2258,9 +2258,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PE - the epoch of the recipe. - The default value is "0". - The field is used to make upgrades possible when the versioning scheme changes in + 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. @@ -2270,10 +2270,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" If multiple recipes provide an item, this variable - determines which recipe should be given preference. - The variable must always be suffixed with the name of the - provided item, and should be set to the - PN of the recipe + determines which recipe should be given preference. + The variable must always be suffixed with the name of the + provided item, and should be set to the + PN of the recipe to which you want to give precedence. Here is an example: @@ -2288,17 +2288,17 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" If there are multiple versions of recipes available, this variable determines which recipe should be given preference. - The variable must always be suffixed with the PN - for which to select, and should be set to the + The variable must always be suffixed with the PN + for which to select, and should be set to the PV to which you want to give precedence. You can use the "%" character as a wildcard - to match any number of characters, which can be useful when - specifying versions that contain long revision number that could + to match any number of characters, which can be useful when + specifying versions that contain long revision number that could potentially change. Here are two examples: PREFERRED_VERSION_python = "2.6.6" - PREFERRED_VERSION_linux-yocto = "3.0+git%" + PREFERRED_VERSION_linux-yocto = "3.0+git%" @@ -2317,7 +2317,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Note that the package will not be installed if the conflicting packages are not first removed. - Like all package-controlling variables, you must always use them in + Like all package-controlling variables, you must always use them in conjunction with a package name override. Here is an example: @@ -2330,59 +2330,59 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" RDEPENDS - Lists a package's run-time dependencies (i.e. other packages) + Lists a package's run-time dependencies (i.e. other packages) that must be installed for the package to be built. - In other words, in order for the package to be built and + In other words, in order for the package to be built and run correctly, it depends on the listed packages. - If a package in this list cannot be found, it is probable + If a package in this list cannot be found, it is probable that a dependency error would occur before the build. - The names of the variables you list with - RDEPENDS must be the names of other - packages as listed in the + The names of the variables you list with + RDEPENDS must be the names of other + packages as listed in the PACKAGES variable. You should not list recipe names (PN). - + - Because the RDEPENDS variable applies - to packages being built, you should - always attach a package name to the variable to specify the + Because the RDEPENDS variable applies + to packages being built, you should + always attach a package name to the variable to specify the particular run-time package that has the dependency. - For example, suppose you are building a development package + For example, suppose you are building a development package that depends on the perl package. - In this case, you would use the following + In this case, you would use the following RDEPENDS statement: RDEPENDS_${PN}-dev += "perl" - In the example, the package name - (${PN}-dev) must appear as it would - in the - PACKAGES - namespace before any renaming of the output package by + In the example, the package name + (${PN}-dev) must appear as it would + in the + PACKAGES + namespace before any renaming of the output package by classes like debian.bbclass. - In many cases you do not need to explicitly add dependencies - to RDEPENDS since some automatic + In many cases you do not need to explicitly add dependencies + to RDEPENDS since some automatic handling occurs: - shlibdeps: If - a run-time package contains a shared library + shlibdeps: If + a run-time package contains a shared library (.so), the build - processes the library in order to determine other - libraries to which it is dynamically linked. - The build process adds these libraries to - RDEPENDS when creating the run-time + processes the library in order to determine other + libraries to which it is dynamically linked. + The build process adds these libraries to + RDEPENDS when creating the run-time package. - pcdeps: If - the package ships a pkg-config - information file, the build process uses this file + pcdeps: If + the package ships a pkg-config + information file, the build process uses this file to add items to the RDEPENDS variable to create the run-time packages. @@ -2394,11 +2394,11 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" RRECOMMENDS - A list of packages that extend the usability of a package being + A list of packages that extend the usability of a package being built. - The package being built does not depend on this list of packages in + The package being built does not depend on this list of packages in order to successfully build, but needs them for the extended usability. - To specify runtime dependencies for packages, see the + To specify runtime dependencies for packages, see the RDEPENDS variable. @@ -2409,8 +2409,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" process continues without an error. - Because the RRECOMMENDS variable applies to packages - being built, you should + Because the RRECOMMENDS variable applies to packages + being built, you should always attach an override to the variable to specify the particular package whose usability is being extended. For example, suppose you are building a development package that is extended @@ -2419,9 +2419,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" RRECOMMENDS_${PN}-dev += "<wireless_package_name>" - In the example, the package name (${PN}-dev) must - appear as it would in the - PACKAGES namespace before any + In the example, the package name (${PN}-dev) must + appear as it would in the + PACKAGES namespace before any renaming of the output package by classes like debian.bbclass. @@ -2442,22 +2442,22 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The location in the Build Directory where unpacked package source code resides. - This location is within the working directory - (WORKDIR), which + This location is within the working directory + (WORKDIR), which is not static. - The unpacked source location depends on the package name - (PN) and - package version (PV) as + The unpacked source location depends on the package name + (PN) and + package version (PV) as follows: ${WORKDIR}/${PN}-${PV} - As an example, assume a - Source Directory top-level - folder named poky + As an example, assume a + Source Directory top-level + folder named poky and a default Build Directory at poky/build. - In this case, the working directory the build system uses to build + In this case, the working directory the build system uses to build the db package is the following: ~/poky/build/tmp/work/qemux86-poky-linux/db-5.1.19-r3/db-5.1.19 @@ -2468,9 +2468,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SDKIMAGE_FEATURES - Equivalent to + Equivalent to IMAGE_FEATURES. - However, this variable applies to the SDK generated from an image using + However, this variable applies to the SDK generated from an image using bitbake -c populate_sdk imagename). @@ -2486,10 +2486,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SELECTED_OPTIMIZATION - The variable takes the value of + The variable takes the value of FULL_OPTIMIZATION unless DEBUG_BUILD = "1". - In this case the value of + In this case the value of DEBUG_OPTIMIZATION is used. @@ -2498,7 +2498,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SERIAL_CONSOLE - The speed and device for the serial port used to attach the serial console. + The speed and device for the serial port used to attach the serial console. This variable is given to the kernel as the "console" parameter and after booting occurs getty is started on that port so remote login is possible. @@ -2508,7 +2508,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SITEINFO_ENDIANNESS - Specifies the endian byte order of the target system. + Specifies the endian byte order of the target system. The value should be either "le" for little-endian or "be" for big-endian. @@ -2526,7 +2526,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SPECIAL_PKGSUFFIX - A list of prefixes for PN used by the + 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. @@ -2539,7 +2539,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The list of source files - local or remote. This variable tells the OpenEmbedded build system which bits to pull in for the build and how to pull them in. - For example, if the recipe only needs to fetch a tarball from the + For example, if the recipe only needs to fetch a tarball from the internet, the recipe uses a single SRC_URI entry. On the other hand, if the recipe needs to fetch a tarball, apply two patches, and include a custom file, the recipe would include four @@ -2547,120 +2547,120 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The following list explains the available URI protocols: file:// - Fetches files, which is usually - a file shipped with the metadata, from the local machine. - The path is relative to the - FILESPATH + a file shipped with the metadata, from the local machine. + The path is relative to the + FILESPATH variable. Thus, the build system searches, in order, from the following directories, - which are assumed to be a subdirectories of the directory in which the + which are assumed to be a subdirectories of the directory in which the recipe file resides: - ${PN} - The recipe name + ${PN} - The recipe name with any special suffix or prefix, if applicable. For example, using bash to build for the native machine, PN is bash-native. Using bash to build for the target and for Multilib, - PN would be bash and + PN would be bash and lib64-bash, respectively. ${PF} - ${PN}-${EXTENDPE}${PV}-${PR}. - The recipe name including all version and revision numbers + The recipe name including all version and revision numbers (i.e. eglibc-2.13-r20+svnr15508/ and bash-4.2-r1/). - ${P} - - ${PN}-${PV}. + ${P} - + ${PN}-${PV}. The recipe name and version (i.e. bash-4.2). - ${BPN} - The + ${BPN} - The base recipe name without any special suffix or version numbers. - ${BP} - + ${BP} - ${BPN}-${PV}. - The base recipe name and version but without any special + The base recipe name and version but without any special package name suffix. Files - Files beneath the directory in which the recipe resides. Directory - The directory itself in which the recipe resides. - bzr:// - Fetches files from a + bzr:// - Fetches files from a Bazaar revision control repository. - git:// - Fetches files from a + git:// - Fetches files from a Git revision control repository. - osc:// - Fetches files from + osc:// - Fetches files from an OSC (OpenSuse Build service) revision control repository. - repo:// - Fetches files from + repo:// - Fetches files from a repo (Git) repository. - svk:// - Fetches files from + svk:// - Fetches files from an SVK revision control repository. - http:// - Fetches files from + http:// - Fetches files from the Internet using http. - https:// - Fetches files + https:// - Fetches files from the Internet using https. - ftp:// - Fetches files + ftp:// - Fetches files from the Internet using ftp. - cvs:// - Fetches files from + cvs:// - Fetches files from a CVS revision control repository. - hg:// - Fetches files from + hg:// - Fetches files from a Mercurial (hg) revision control repository. - p4:// - Fetches files from + p4:// - Fetches files from a Perforce (p4) revision control repository. - ssh:// - Fetches files from + ssh:// - Fetches files from a secure shell. - svn:// - Fetches files from + svn:// - Fetches files from a Subversion (svn) revision control repository. Standard and recipe-specific options for SRC_URI exist. Here are standard options: - apply - Whether to apply - the patch or not. + apply - Whether to apply + the patch or not. The default action is to apply the patch. - striplevel - Which + striplevel - Which striplevel to use when applying the patch. The default level is 1. Here are options specific to recipes building code from a revision control system: - mindate - Only applies - the patch if SRCDATE + mindate - Only applies + the patch if SRCDATE is equal to or greater than mindate. - maxdate - Only applies - the patch if SRCDATE + maxdate - Only applies + the patch if SRCDATE is not later than mindate. - minrev - Only applies - the patch if SRCREV + minrev - Only applies + the patch if SRCREV is equal to or greater than minrev. - maxrev - Only applies - the patch if SRCREV + maxrev - Only applies + the patch if SRCREV is not later than maxrev. - rev - Only applies the - patch if SRCREV + rev - Only applies the + patch if SRCREV is equal to rev. - notrev - Only applies - the patch if SRCREV + notrev - Only applies + the patch if SRCREV is not equal to rev. Here are some additional options worth mentioning: - unpack - Controls + unpack - Controls whether or not to unpack the file if it is an archive. The default action is to upack the file. - subdir - Places the file - (or extracts its contents) into the specified + subdir - Places the file + (or extracts its contents) into the specified subdirectory of WORKDIR. - This option is useful for unusual tarballs or other archives that + This option is useful for unusual tarballs or other archives that don't have their files already in a subdirectory within the archive. - name - Specifies a - name to be used for association with SRC_URI checksums + name - Specifies a + name to be used for association with SRC_URI checksums when you have more than one file specified in SRC_URI. - downloadfilename - Specifies + downloadfilename - Specifies the filename used when storing the downloaded file. @@ -2671,11 +2671,11 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - By default, the OpenEmbedded build system automatically detects whether - SRC_URI + 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. + If so, the build system automatically changes + PACKAGE_ARCH. Setting this variable to "0" disables this behavior. @@ -2695,7 +2695,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The revision of the source code used to build the package. This variable applies to Subversion, Git, Mercurial and Bazaar - only. + only. Note that if you wish to build a fixed revision and you wish to avoid performing a query on the remote repository every time BitBake parses your recipe, you should specify a SRCREV that is a @@ -2713,30 +2713,30 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SSTATE_MIRRORS - Configures the OpenEmbedded build system to search other - mirror locations for prebuilt cache data objects before + Configures the OpenEmbedded build system to search other + mirror locations for prebuilt cache data objects before building out the data. - This variable works like fetcher + This variable works like fetcher MIRRORS/PREMIRRORS - and points to the cache locations to check for the shared + and points to the cache locations to check for the shared objects. - You can specify a filesystem directory or a remote URL such + You can specify a filesystem directory or a remote URL such as HTTP or FTP. The locations you specify need to contain the shared state cache (sstate-cache) results from previous builds. - The sstate-cache you point to can also be from builds on - other machines. + The sstate-cache you point to can also be from builds on + other machines. - If a mirror uses the same structure as - SSTATE_DIR, - you need to add - "PATH" at the end as shown in the examples below. - The build system substitues the correct path within the + If a mirror uses the same structure as + SSTATE_DIR, + you need to add + "PATH" at the end as shown in the examples below. + The build system substitues the correct path within the directory structure. SSTATE_MIRRORS ?= "\ @@ -2761,14 +2761,14 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" 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. + string and then appending additional information. Currently, the default assignment for STAMP as set in the meta/conf/bitbake.conf file is: STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}-${EXTENDPE}${PV}-${PR}" - See TMPDIR, + See TMPDIR, MULTIMACH_TARGET_SYS, PN, EXTENDPE, @@ -2781,12 +2781,12 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" SUMMARY - The short (72 characters or less) summary of the binary package for packaging - systems such as opkg, rpm or + The short (72 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 + variable if DESCRIPTION is not set in the recipe. @@ -2798,18 +2798,18 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" T - This variable points to a directory were Bitbake places temporary - files when building a particular package. + This variable points to a directory were Bitbake places temporary + files when building a particular package. It is typically set as follows: T = ${WORKDIR}/temp The WORKDIR - is the directory into which Bitbake unpacks and builds the package. + is the directory into which Bitbake unpacks and builds the package. The default bitbake.conf file sets this variable. - The T variable is not to be confused with + The T variable is not to be confused with the TMPDIR variable, - which points to the root of the directory tree where Bitbake + which points to the root of the directory tree where Bitbake places the output of an entire build. @@ -2817,7 +2817,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" TARGET_ARCH - The architecture of the device being built. + The architecture of the device being built. While a number of values are possible, the OpenEmbedded build system primarily supports arm and i586. @@ -2826,8 +2826,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" TARGET_CFLAGS - Flags passed to the C compiler for the target system. - This variable evaluates to the same as + Flags passed to the C compiler for the target system. + This variable evaluates to the same as CFLAGS. @@ -2836,7 +2836,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" TARGET_FPU - Specifies the method for handling FPU code. + 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. @@ -2845,9 +2845,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" TARGET_OS - Specifies the target's operating system. + Specifies the target's operating system. The variable can be set to "linux" for eglibc-based systems and - to "linux-uclibc" for uclibc. + to "linux-uclibc" for uclibc. For ARM/EABI targets, there are also "linux-gnueabi" and "linux-uclibc-gnueabi" values possible. @@ -2864,7 +2864,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" You can select eglibc or uclibc. - This release of the Yocto Project does not support the + This release of the Yocto Project does not support the glibc implementation of libc. @@ -2874,7 +2874,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" TCMODE - The toolchain selector. + The toolchain selector. This variable replaces POKYMODE, which is no longer supported. @@ -2882,39 +2882,39 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" The TCMODE variable selects the external toolchain built using the OpenEmbedded build system or a few supported combinations of the upstream GCC or CodeSourcery Labs toolchain. - The variable identifies the tcmode-* files used in + The variable identifies the tcmode-* files used in the meta/conf/distro/include directory, which is found in the - Source Directory. + Source Directory. - By default, TCMODE is set to "default", which + By default, TCMODE is set to "default", which chooses the tcmode-default.inc file. - The variable is similar to - TCLIBC, which controls + The variable is similar to + TCLIBC, which controls the variant of the GNU standard C library (libc) used during the build process: eglibc or uclibc. - + TMPDIR - This variable is 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 + This variable is 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. If you want to establish this directory in a location other than the - default, you can uncomment the following statement in the - conf/local.conf file in the + default, you can uncomment the following statement in the + conf/local.conf file in the Source Directory: #TMPDIR = "${TOPDIR}/tmp" - + @@ -2922,10 +2922,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" TOPDIR - This variable is the + This variable is the Build Directory. BitBake automatically sets this variable. - The OpenEmbedded build system uses the Build Directory when building images. + The OpenEmbedded build system uses the Build Directory when building images. @@ -2943,7 +2943,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" WORKDIR - The pathname of the working directory in which the OpenEmbedded build system + 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 @@ -2964,17 +2964,17 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - For packages that are not dependent on a particular machine, + For packages that are not dependent on a particular machine, WORKDIR is defined as follows: ${TMPDIR}/work/${PACKAGE_ARCH}-poky-${TARGET_OS}/${PN}-${PV}-${PR} - As an example, assume a - Source Directory top-level - folder name poky and a default - Build Directory + As an example, assume a + Source Directory top-level + folder name poky and a default + Build Directory at poky/build. - In this case, the working directory the build system uses to build + In this case, the working directory the build system uses to build the v86d package is the following: ~/poky/build/tmp/work/qemux86-poky-linux/v86d-01.9-r0 @@ -2987,11 +2987,11 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR} - As an example, again assume a Source Directory top-level folder - named poky and a default Build Directory + As an example, again assume a Source Directory top-level folder + named poky and a default Build Directory at poky/build. In this case, the working directory the build system uses to build - the acl recipe, which is being built for a + the acl recipe, which is being built for a MIPS-based device, is the following: ~/poky/build/tmp/work/mips-poky-linux/acl-2.2.51-r2 @@ -3013,6 +3013,6 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - diff --git a/documentation/poky-ref-manual/ref-varlocality.xml b/documentation/poky-ref-manual/ref-varlocality.xml index a9db35fe4b..ae8f75c2f5 100644 --- a/documentation/poky-ref-manual/ref-varlocality.xml +++ b/documentation/poky-ref-manual/ref-varlocality.xml @@ -6,10 +6,10 @@ Variable Context - While most variables can be used in almost any context such as + While most variables can be used in almost any context such as .conf, .bbclass, .inc, and .bb files, - some variables are often associated with a particular locality or context. + some variables are often associated with a particular locality or context. This chapter describes some common associations. @@ -80,7 +80,7 @@ Local - This section lists variables whose context is the local configuration through the + This section lists variables whose context is the local configuration through the local.conf file. DISTRO @@ -188,6 +188,6 @@ - diff --git a/documentation/poky-ref-manual/resources.xml b/documentation/poky-ref-manual/resources.xml index 8c47b18ec7..a6916064f6 100644 --- a/documentation/poky-ref-manual/resources.xml +++ b/documentation/poky-ref-manual/resources.xml @@ -9,7 +9,7 @@ Introduction The Yocto Project team is happy for people to experiment with the Yocto Project. - A number of places exist to find help if you run into difficulties or find bugs. + A number of places exist to find help if you run into difficulties or find bugs. To find out how to download source code, see the "Yocto Project Release" list item in the Yocto Project Development Manual. @@ -20,7 +20,7 @@ Tracking Bugs - If you find problems with the Yocto Project, you should report them using the + If you find problems with the Yocto Project, you should report them using the Bugzilla application at . @@ -75,18 +75,18 @@ The company where the Yocto Project build system Poky was first developed. OpenedHand has since been acquired by Intel Corporation. --> Intel Corporation: - The company who acquired OpenedHand in 2008 and began development on the + The company who acquired OpenedHand in 2008 and began development on the Yocto Project. OpenEmbedded: - The upstream, generic, embedded distribution used as the basis for the build system in the + The upstream, generic, embedded distribution used as the basis for the build system in the Yocto Project. Poky derives from and contributes back to the OpenEmbedded project. BitBake: The tool used to process metadata. BitBake User Manual: A comprehensive guide to the BitBake tool. - You can find the BitBake User Manual in the bitbake/doc/manual - directory, which is found in the + You can find the BitBake User Manual in the bitbake/doc/manual + directory, which is found in the Source Directory. QEMU: @@ -100,7 +100,7 @@ The Yocto Project gladly accepts contributions. - You can submit changes to the project either by creating and sending pull requests, + You can submit changes to the project either by creating and sending pull requests, or by submitting patches through email. For information on how to do both, see the "How to Submit a Change" @@ -109,6 +109,6 @@ - diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml index 042a96ed87..72689a0e22 100644 --- a/documentation/poky-ref-manual/technical-details.xml +++ b/documentation/poky-ref-manual/technical-details.xml @@ -6,7 +6,7 @@ Technical Details - This chapter provides technical details for various parts of the Yocto Project. + This chapter provides technical details for various parts of the Yocto Project. Currently, topics include Yocto Project components and shared state (sstate) cache. @@ -14,21 +14,21 @@ Yocto Project Components - The BitBake task executor together with various types of configuration files form the + The BitBake task executor together with various types of configuration files form the OpenEmbedded Core. This section overviews the BitBake task executor and the configuration files by describing what they are used for and how they interact. - - - BitBake handles the parsing and execution of the data files. + + + BitBake handles the parsing and execution of the data files. The data itself is of various types: - Recipes: Provides details about particular + Recipes: Provides details about particular pieces of software - Class Data: An abstraction of common build + Class Data: An abstraction of common build information (e.g. how to build a Linux kernel). - Configuration Data: Defines machine-specific settings, + Configuration Data: Defines machine-specific settings, policy decisions, etc. Configuration data acts as the glue to bind everything together. @@ -37,17 +37,17 @@ section in the Yocto Project Development Manual. - + BitBake knows how to combine multiple data sources together and refers to each data source as a layer. - For information on layers, see the - "Understanding and + For information on layers, see the + "Understanding and Creating Layers" section of the Yocto Project Development Manual. Following are some brief details on these core components. - For more detailed information on these components see the + For more detailed information on these components see the "Directory Structure" chapter. @@ -57,7 +57,7 @@ BitBake is the tool at the heart of the OpenEmbedded build system and is responsible for parsing the metadata, generating a list of tasks from it, - and then executing those tasks. + and then executing those tasks. To see a list of the options BitBake supports, use the following help command: $ bitbake --help @@ -66,8 +66,8 @@ The most common usage for BitBake is bitbake <packagename>, where - packagename is the name of the package you want to build - (referred to as the "target" in this manual). + packagename is the name of the package you want to build + (referred to as the "target" in this manual). The target often equates to the first part of a .bb filename. So, to run the matchbox-desktop_1.2.3.bb file, you might type the following: @@ -76,15 +76,15 @@ Several different versions of matchbox-desktop might exist. BitBake chooses the one selected by the distribution configuration. - You can get more details about how BitBake chooses between different - target versions and providers in the + You can get more details about how BitBake chooses between different + target versions and providers in the "Preferences and Providers" section. BitBake also tries to execute any dependent tasks first. So for example, before building matchbox-desktop, BitBake - would build a cross compiler and eglibc if they had not already + would build a cross compiler and eglibc if they had not already been built. This release of the Yocto Project does not support the glibc GNU version of the Unix standard C library. By default, the OpenEmbedded build system @@ -92,12 +92,12 @@ - A useful BitBake option to consider is the -k or - --continue option. - This option instructs BitBake to try and continue processing the job as much - as possible even after encountering an error. + A useful BitBake option to consider is the -k or + --continue option. + This option instructs BitBake to try and continue processing the job as much + as possible even after encountering an error. When an error occurs, the target that - failed and those that depend on it cannot be remade. + failed and those that depend on it cannot be remade. However, when you use this option other dependencies can still be processed. @@ -106,17 +106,17 @@ Metadata (Recipes) - The .bb files are usually referred to as "recipes." + The .bb files are usually referred to as "recipes." In general, a recipe contains information about a single piece of software. - The information includes the location from which to download the source patches - (if any are needed), which special configuration options to apply, - how to compile the source files, and how to package the compiled output. + The information includes the location from which to download the source patches + (if any are needed), which special configuration options to apply, + how to compile the source files, and how to package the compiled output. The term "package" can also be used to describe recipes. - However, since the same word is used for the packaged output from the OpenEmbedded - build system (i.e. .ipk or .deb files), + However, since the same word is used for the packaged output from the OpenEmbedded + build system (i.e. .ipk or .deb files), this document avoids using the term "package" when referring to recipes. @@ -126,7 +126,7 @@ Class files (.bbclass) contain information that is useful to share - between metadata files. + between metadata files. An example is the Autotools class, which contains common settings for any application that Autotools uses. The "Classes" chapter provides details @@ -139,8 +139,8 @@ The configuration files (.conf) define various configuration variables - that govern the OpenEmbedded build process. - These files fall into several areas that define machine configuration options, + that govern the OpenEmbedded build process. + These files fall into several areas that define machine configuration options, distribution configuration options, compiler tuning options, general common configuration options and user configuration options (local.conf, which is found in the Build Directory). @@ -152,19 +152,19 @@ Shared State Cache - By design, the OpenEmbedded build system builds everything from scratch unless + By design, the OpenEmbedded build system builds everything from scratch unless BitBake can determine that parts don't need to be rebuilt. - Fundamentally, building from scratch is attractive as it means all parts are - built fresh and there is no possibility of stale data causing problems. + Fundamentally, building from scratch is attractive as it means all parts are + built fresh and there is no possibility of stale data causing problems. When developers hit problems, they typically default back to building from scratch so they know the state of things from the start. - - Building an image from scratch is both an advantage and a disadvantage to the process. - As mentioned in the previous paragraph, building from scratch ensures that + + Building an image from scratch is both an advantage and a disadvantage to the process. + As mentioned in the previous paragraph, building from scratch ensures that everything is current and starts from a known state. - However, building from scratch also takes much longer as it generally means + However, building from scratch also takes much longer as it generally means rebuilding things that don't necessarily need rebuilt. @@ -181,15 +181,15 @@ - For the first question, the build system detects changes in the "inputs" to a given task by - creating a checksum (or signature) of the task's inputs. - If the checksum changes, the system assumes the inputs have changed and the task needs to be + For the first question, the build system detects changes in the "inputs" to a given task by + creating a checksum (or signature) of the task's inputs. + If the checksum changes, the system assumes the inputs have changed and the task needs to be rerun. For the second question, the shared state (sstate) code tracks which tasks add which output - to the build process. + to the build process. This means the output from a given task can be removed, upgraded or otherwise manipulated. The third question is partly addressed by the solution for the second question - assuming the build system can fetch the sstate objects from remote locations and + assuming the build system can fetch the sstate objects from remote locations and install them if they are deemed to be valid. @@ -202,18 +202,18 @@ Overall Architecture - When determining what parts of the system need to be built, BitBake + When determining what parts of the system need to be built, BitBake uses a per-task basis and does not use a per-recipe basis. You might wonder why using a per-task basis is preferred over a per-recipe basis. - To help explain, consider having the IPK packaging backend enabled and then switching to DEB. + To help explain, consider having the IPK packaging backend enabled and then switching to DEB. In this case, do_install and do_package output are still valid. - However, with a per-recipe approach, the build would not include the - .deb files. - Consequently, you would have to invalidate the whole build and rerun it. + However, with a per-recipe approach, the build would not include the + .deb files. + Consequently, you would have to invalidate the whole build and rerun it. Rerunning everything is not the best situation. - Also in this case, the core must be "taught" much about specific tasks. - This methodology does not scale well and does not allow users to easily add new tasks + Also in this case, the core must be "taught" much about specific tasks. + This methodology does not scale well and does not allow users to easily add new tasks in layers or as external recipes without touching the packaged-staging core. @@ -222,37 +222,37 @@ Checksums (Signatures) - The shared state code uses a checksum, which is a unique signature of a task's - inputs, to determine if a task needs to be run again. + The shared state code uses a checksum, which is a unique signature of a task's + inputs, to determine if a task needs to be run again. Because it is a change in a task's inputs that triggers a rerun, the process - needs to detect all the inputs to a given task. + needs to detect all the inputs to a given task. For shell tasks, this turns out to be fairly easy because - the build process generates a "run" shell script for each task and - it is possible to create a checksum that gives you a good idea of when + the build process generates a "run" shell script for each task and + it is possible to create a checksum that gives you a good idea of when the task's data changes. - To complicate the problem, there are things that should not be included in - the checksum. - First, there is the actual specific build path of a given task - - the WORKDIR. - It does not matter if the working directory changes because it should not + To complicate the problem, there are things that should not be included in + the checksum. + First, there is the actual specific build path of a given task - + the WORKDIR. + It does not matter if the working directory changes because it should not affect the output for target packages. - Also, the build process has the objective of making native/cross packages relocatable. + Also, the build process has the objective of making native/cross packages relocatable. The checksum therefore needs to exclude WORKDIR. - The simplistic approach for excluding the working directory is to set + The simplistic approach for excluding the working directory is to set WORKDIR to some fixed value and create the checksum - for the "run" script. + for the "run" script. - Another problem results from the "run" scripts containing functions that - might or might not get called. - The incremental build solution contains code that figures out dependencies + Another problem results from the "run" scripts containing functions that + might or might not get called. + The incremental build solution contains code that figures out dependencies between shell functions. - This code is used to prune the "run" scripts down to the minimum set, - thereby alleviating this problem and making the "run" scripts much more + This code is used to prune the "run" scripts down to the minimum set, + thereby alleviating this problem and making the "run" scripts much more readable as a bonus. @@ -260,62 +260,62 @@ So far we have solutions for shell scripts. What about python tasks? The same approach applies even though these tasks are more difficult. - The process needs to figure out what variables a python function accesses + The process needs to figure out what variables a python function accesses and what functions it calls. - Again, the incremental build solution contains code that first figures out - the variable and function dependencies, and then creates a checksum for the data + Again, the incremental build solution contains code that first figures out + the variable and function dependencies, and then creates a checksum for the data used as the input to the task. - Like the WORKDIR case, situations exist where dependencies + Like the WORKDIR case, situations exist where dependencies should be ignored. For these cases, you can instruct the build process to ignore a dependency by using a line like the following: PACKAGE_ARCHS[vardepsexclude] = "MACHINE" - This example ensures that the PACKAGE_ARCHS variable does not + This example ensures that the PACKAGE_ARCHS variable does not depend on the value of MACHINE, even if it does reference it. - + Equally, there are cases where we need to add dependencies BitBake is not able to find. You can accomplish this by using a line like the following: PACKAGE_ARCHS[vardeps] = "MACHINE" - This example explicitly adds the MACHINE variable as a + This example explicitly adds the MACHINE variable as a dependency for PACKAGE_ARCHS. - + Consider a case with inline python, for example, where BitBake is not - able to figure out dependencies. - When running in debug mode (i.e. using -DDD), BitBake + able to figure out dependencies. + When running in debug mode (i.e. using -DDD), BitBake produces output when it discovers something for which it cannot figure out - dependencies. - The Yocto Project team has currently not managed to cover those dependencies + dependencies. + The Yocto Project team has currently not managed to cover those dependencies in detail and is aware of the need to fix this situation. Thus far, this section has limited discussion to the direct inputs into a task. Information based on direct inputs is referred to as the "basehash" in the - code. + code. However, there is still the question of a task's indirect inputs - the - things that were already built and present in the Build Directory. - The checksum (or signature) for a particular task needs to add the hashes - of all the tasks on which the particular task depends. - Choosing which dependencies to add is a policy decision. - However, the effect is to generate a master checksum that combines the basehash + things that were already built and present in the Build Directory. + The checksum (or signature) for a particular task needs to add the hashes + of all the tasks on which the particular task depends. + Choosing which dependencies to add is a policy decision. + However, the effect is to generate a master checksum that combines the basehash and the hashes of the task's dependencies. At the code level, there are a variety of ways both the basehash and the - dependent task hashes can be influenced. - Within the BitBake configuration file, we can give BitBake some extra information + dependent task hashes can be influenced. + Within the BitBake configuration file, we can give BitBake some extra information to help it construct the basehash. The following statements effectively result in a list of global variable dependency excludes - variables never included in any checksum: @@ -325,42 +325,42 @@ BB_HASHBASE_WHITELIST += "FILE_DIRNAME HOME LOGNAME SHELL TERM USER" BB_HASHBASE_WHITELIST += "FILESPATH USERNAME STAGING_DIR_HOST STAGING_DIR_TARGET" - The previous example actually excludes + The previous example actually excludes WORKDIR - since it is actually constructed as a path within - TMPDIR, which is on - the whitelist. + since it is actually constructed as a path within + TMPDIR, which is on + the whitelist. The rules for deciding which hashes of dependent tasks to include through - dependency chains are more complex and are generally accomplished with a - python function. + dependency chains are more complex and are generally accomplished with a + python function. The code in meta/lib/oe/sstatesig.py shows two examples - of this and also illustrates how you can insert your own policy into the system + of this and also illustrates how you can insert your own policy into the system if so desired. This file defines the two basic signature generators OE-Core - uses: "OEBasic" and "OEBasicHash". - By default, there is a dummy "noop" signature handler enabled in BitBake. - This means that behavior is unchanged from previous versions. + uses: "OEBasic" and "OEBasicHash". + By default, there is a dummy "noop" signature handler enabled in BitBake. + This means that behavior is unchanged from previous versions. OE-Core uses the "OEBasic" signature handler by default through this setting in the bitbake.conf file: BB_SIGNATURE_HANDLER ?= "OEBasic" - The "OEBasicHash" BB_SIGNATURE_HANDLER is the same as the - "OEBasic" version but adds the task hash to the stamp files. - This results in any metadata change that changes the task hash, automatically - causing the task to be run again. + The "OEBasicHash" BB_SIGNATURE_HANDLER is the same as the + "OEBasic" version but adds the task hash to the stamp files. + This results in any metadata change that changes the task hash, automatically + causing the task to be run again. This removes the need to bump PR - values and changes to metadata automatically ripple across the build. + values and changes to metadata automatically ripple across the build. Currently, this behavior is not the default behavior for OE-Core but is the default in poky. It is also worth noting that the end result of these signature generators is to - make some dependency and hash information available to the build. + make some dependency and hash information available to the build. This information includes: BB_BASEHASH_task-<taskname> - the base hashes for each task in the recipe @@ -375,15 +375,15 @@ Shared State - Checksums and dependencies, as discussed in the previous section, solve half the + Checksums and dependencies, as discussed in the previous section, solve half the problem. The other part of the problem is being able to use checksum information during the build and being able to reuse or rebuild specific components. - The shared state class (sstate.bbclass) - is a relatively generic implementation of how to "capture" a snapshot of a given task. + The shared state class (sstate.bbclass) + is a relatively generic implementation of how to "capture" a snapshot of a given task. The idea is that the build process does not care about the source of a task's output. Output could be freshly built or it could be downloaded and unpacked from somewhere - the build process doesn't need to worry about its source. @@ -392,17 +392,17 @@ There are two types of output, one is just about creating a directory in WORKDIR. - A good example is the output of either do_install or - do_package. - The other type of output occurs when a set of data is merged into a shared directory + A good example is the output of either do_install or + do_package. + The other type of output occurs when a set of data is merged into a shared directory tree such as the sysroot. - The Yocto Project team has tried to keep the details of the implementation hidden in - sstate.bbclass. + The Yocto Project team has tried to keep the details of the implementation hidden in + sstate.bbclass. From a user's perspective, adding shared state wrapping to a task - is as simple as this do_deploy example taken from + is as simple as this do_deploy example taken from do_deploy.bbclass: DEPLOYDIR = "${WORKDIR}/deploy-${PN}" @@ -418,13 +418,13 @@ In the example, we add some extra flags to the task, a name field ("deploy"), an input directory where the task sends data, and the output - directory where the data from the task should eventually be copied. + directory where the data from the task should eventually be copied. We also add a _setscene variant of the task and add the task name to the SSTATETASKS list. - If you have a directory whose contents you need to preserve, you can do this with + If you have a directory whose contents you need to preserve, you can do this with a line like the following: do_package[sstate-plaindirs] = "${PKGD} ${PKGDEST}" @@ -441,21 +441,21 @@ - Behind the scenes, the shared state code works by looking in - SSTATE_DIR and + Behind the scenes, the shared state code works by looking in + SSTATE_DIR and SSTATE_MIRRORS - for shared state files. + for shared state files. Here is an example: SSTATE_MIRRORS ?= "\ file://.* http://someserver.tld/share/sstate/PATH \n \ file://.* file:///some/local/dir/sstate/PATH" - - The shared state directory (SSTATE_DIR) is - organized into two-character subdirectories, where the subdirectory + + The shared state directory (SSTATE_DIR) is + organized into two-character subdirectories, where the subdirectory names are based on the first two characters of the hash. - If the shared state directory structure for a mirror has the + If the shared state directory structure for a mirror has the same structure as SSTATE_DIR, you must specify "PATH" as part of the URI to enable the build system to map to the appropriate subdirectory. @@ -465,8 +465,8 @@ The shared state package validity can be detected just by looking at the filename since the filename contains the task checksum (or signature) as - described earlier in this section. - If a valid shared state package is found, the build process downloads it + described earlier in this section. + If a valid shared state package is found, the build process downloads it and uses it to accelerate the task. @@ -474,19 +474,19 @@ The build processes uses the *_setscene tasks for the task acceleration phase. BitBake goes through this phase before the main execution code and tries - to accelerate any tasks for which it can find shared state packages. + to accelerate any tasks for which it can find shared state packages. If a shared state package for a task is available, the shared state package is used. - This means the task and any tasks on which it is dependent are not + This means the task and any tasks on which it is dependent are not executed. As a real world example, the aim is when building an IPK-based image, - only the do_package_write_ipk tasks would have their - shared state packages fetched and extracted. - Since the sysroot is not used, it would never get extracted. - This is another reason why a task-based approach is preferred over a + only the do_package_write_ipk tasks would have their + shared state packages fetched and extracted. + Since the sysroot is not used, it would never get extracted. + This is another reason why a task-based approach is preferred over a recipe-based approach, which would have to install the output from every task. @@ -495,9 +495,9 @@ Tips and Tricks - The code in the build system that supports incremental builds is not + The code in the build system that supports incremental builds is not simple code. - This section presents some tips and tricks that help you work around + This section presents some tips and tricks that help you work around issues related to shared state code. @@ -505,25 +505,25 @@ Debugging - When things go wrong, debugging needs to be straightforward. + When things go wrong, debugging needs to be straightforward. Because of this, the Yocto Project team included strong debugging tools: Whenever a shared state package is written out, so is a - corresponding .siginfo file. + corresponding .siginfo file. This practice results in a pickled python database of all the metadata that went into creating the hash for a given shared state package. If BitBake is run with the --dump-signatures - (or -S) option, BitBake dumps out + (or -S) option, BitBake dumps out .siginfo files in the stamp directory for every task it would have executed instead of building the specified target package. There is a bitbake-diffsigs command that - can process these .siginfo files. + can process these .siginfo files. If one file is specified, it will dump out the dependency - information in the file. - If two files are specified, it will compare the two files and dump out + information in the file. + If two files are specified, it will compare the two files and dump out the differences between the two. This allows the question of "What changed between X and Y?" to be answered easily. @@ -538,41 +538,41 @@ The shared state code uses checksums and shared state cache to avoid unnecessarily rebuilding tasks. As with all schemes, this one has some drawbacks. - It is possible that you could make implicit changes that are not factored - into the checksum calculation, but do affect a task's output. + It is possible that you could make implicit changes that are not factored + into the checksum calculation, but do affect a task's output. A good example is perhaps when a tool changes its output. Let's say that the output of rpmdeps needed to change. The result of the change should be that all the "package", "package_write_rpm", and "package_deploy-rpm" shared state cache items would become invalid. But, because this is a change that is external to the code and therefore implicit, the associated shared state cache items do not become invalidated. - In this case, the build process would use the cached items rather than running the - task again. + In this case, the build process would use the cached items rather than running the + task again. Obviously, these types of implicit changes can cause problems. To avoid these problems during the build, you need to understand the effects of any change you make. - Note that any changes you make directly to a function automatically are factored into + Note that any changes you make directly to a function automatically are factored into the checksum calculation and thus, will invalidate the associated area of sstate cache. - You need to be aware of any implicit changes that are not obvious changes to the - code and could affect the output of a given task. - Once you are aware of such a change, you can take steps to invalidate the cache - and force the task to run. - The step to take is as simple as changing a function's comments in the source code. + You need to be aware of any implicit changes that are not obvious changes to the + code and could affect the output of a given task. + Once you are aware of such a change, you can take steps to invalidate the cache + and force the task to run. + The step to take is as simple as changing a function's comments in the source code. For example, to invalidate package shared state files, change the comment statements of do_package or the comments of one of the functions it calls. - The change is purely cosmetic, but it causes the checksum to be recalculated and + The change is purely cosmetic, but it causes the checksum to be recalculated and forces the task to be run again. - For an example of a commit that makes a cosmetic change to invalidate + For an example of a commit that makes a cosmetic change to invalidate a shared state, see this commit. - + @@ -580,24 +580,24 @@ x32 - x32 is a new processor-specific Application Binary Interface (psABI) for x86_64. - An ABI defines the calling conventions between functions in a processing environment. + x32 is a new processor-specific Application Binary Interface (psABI) for x86_64. + An ABI defines the calling conventions between functions in a processing environment. The interface determines what registers are used and what the sizes are for various C data types. - Some processing environments prefer using 32-bit applications even when running - on Intel 64-bit platforms. + Some processing environments prefer using 32-bit applications even when running + on Intel 64-bit platforms. Consider the i386 psABI, which is a very old 32-bit ABI for Intel 64-bit platforms. The i386 psABI does not provide efficient use and access of the Intel 64-bit processor resources, - leaving the system underutilized. + leaving the system underutilized. Now consider the x86_64 psABI. This ABI is newer and uses 64-bits for data sizes and program pointers. - The extra bits increase the footprint size of the programs, libraries, + The extra bits increase the footprint size of the programs, libraries, and also increases the memory and file system size requirements. - Executing under the x32 psABI enables user programs to utilize CPU and system resources + Executing under the x32 psABI enables user programs to utilize CPU and system resources more efficiently while keeping the memory footprint of the applications low. - Extra bits are used for registers but not for addressing mechanisms. + Extra bits are used for registers but not for addressing mechanisms.
@@ -608,14 +608,14 @@ release supports current development specifications of x32 psABI. As of this release of the Yocto Project, x32 psABI support exists as follows: - You can create packages and images in x32 psABI format on x86_64 architecture targets. + You can create packages and images in x32 psABI format on x86_64 architecture targets. You can use the x32 psABI support through the meta-x32 layer on top of the OE-core/Yocto layer. - The toolchain from the experimental/meta-x32 layer + The toolchain from the experimental/meta-x32 layer is used for building x32 psABI program binaries. You can successfully build many recipes with the x32 toolchain. - You can create and boot core-image-minimal and + You can create and boot core-image-minimal and core-image-sato images. @@ -625,18 +625,18 @@ Future Development and Limitations - As of this Yocto Project release, the x32 psABI kernel and library interfaces + As of this Yocto Project release, the x32 psABI kernel and library interfaces specifications are not finalized. Future Plans for the x32 psABI in the Yocto Project include the following: - Enhance and fix the few remaining recipes so they + Enhance and fix the few remaining recipes so they work with and support x32 toolchains. Enhance RPM Package Manager (RPM) support for x32 binaries. Support larger images. - Integrate x32 recipes, toolchain, and kernel changes from + Integrate x32 recipes, toolchain, and kernel changes from experimental/meta-x32 into OE-core. @@ -650,7 +650,7 @@ Yocto Project, you can follow these steps to use the x32 spABI: Add the experimental/meta-x32 layer to your local - Build Directory. + Build Directory. You can find the experimental/meta-x32 source repository at . Edit your conf/bblayers.conf file so that it includes @@ -677,8 +677,8 @@ or 'INVALID'), True) or 'lib'}" #MACHINE = "atom-pc" #DEFAULTTUNE = "core2-64-x32" - - As usual, use BitBake to build an image that supports the x32 psABI. + + As usual, use BitBake to build an image that supports the x32 psABI. Here is an example: $ bitake core-image-sato @@ -696,15 +696,15 @@ Licenses - This section describes the mechanism by which the OpenEmbedded build system + This section describes the mechanism by which the OpenEmbedded build system tracks changes to licensing text. - The section also describes how to enable commercially licensed recipes, + The section also describes how to enable commercially licensed recipes, which by default are disabled. - For information that can help you maintain compliance with various open - source licensing during the lifecycle of the product, see the + For information that can help you maintain compliance with various open + source licensing during the lifecycle of the product, see the "Maintaining Open Source License Compliance During Your Project's Lifecycle" section in the Yocto Project Development Manual. @@ -713,8 +713,8 @@ Tracking License Changes - The license of an upstream project might change in the future. - In order to prevent these changes going unnoticed, the + The license of an upstream project might change in the future. + In order to prevent these changes going unnoticed, the LIC_FILES_CHKSUM variable tracks changes to the license text. The checksums are validated at the end of the configure step, and if the checksums do not match, the build will fail. @@ -736,15 +736,15 @@ - The build system uses the - S variable as the - default directory used when searching files listed in + The build system uses the + S variable as the + default directory used when searching files listed in LIC_FILES_CHKSUM. The previous example employs the default directory. - You can also use relative paths as shown in the following example: + You can also use relative paths as shown in the following example: LIC_FILES_CHKSUM = "file://src/ls.c;startline=5;endline=16;\ md5=bb14ed3c4cda583abc85401304b5cd4e" @@ -753,14 +753,14 @@ - In this example, the first line locates a file in - ${S}/src/ls.c. - The second line refers to a file in + In this example, the first line locates a file in + ${S}/src/ls.c. + The second line refers to a file in WORKDIR, which is the parent of S. - Note that this variable is mandatory for all recipes, unless the + Note that this variable is mandatory for all recipes, unless the LICENSE variable is set to "CLOSED".
@@ -768,48 +768,48 @@
Explanation of Syntax - As mentioned in the previous section, the - LIC_FILES_CHKSUM variable lists all the - important files that contain the license text for the source code. + As mentioned in the previous section, the + LIC_FILES_CHKSUM variable lists all the + important files that contain the license text for the source code. It is possible to specify a checksum for an entire file, or a specific section of a file (specified by beginning and ending line numbers with the "beginline" and "endline" - parameters, respectively). + parameters, respectively). The latter is useful for source files with a license notice header, README documents, and so forth. - If you do not use the "beginline" parameter, then it is assumed that the text begins on the - first line of the file. - Similarly, if you do not use the "endline" parameter, it is assumed that the license text - ends with the last line of the file. + If you do not use the "beginline" parameter, then it is assumed that the text begins on the + first line of the file. + Similarly, if you do not use the "endline" parameter, it is assumed that the license text + ends with the last line of the file. - The "md5" parameter stores the md5 checksum of the license text. + The "md5" parameter stores the md5 checksum of the license text. If the license text changes in any way as compared to this parameter then a mismatch occurs. This mismatch triggers a build failure and notifies the developer. Notification allows the developer to review and address the license text changes. - Also note that if a mismatch occurs during the build, the correct md5 + Also note that if a mismatch occurs during the build, the correct md5 checksum is placed in the build log and can be easily copied to the recipe. - There is no limit to how many files you can specify using the + There is no limit to how many files you can specify using the LIC_FILES_CHKSUM variable. - Generally, however, every project requires a few specifications for license tracking. - Many projects have a "COPYING" file that stores the license information for all the source + Generally, however, every project requires a few specifications for license tracking. + Many projects have a "COPYING" file that stores the license information for all the source code files. - This practice allows you to just track the "COPYING" file as long as it is kept up to date. + This practice allows you to just track the "COPYING" file as long as it is kept up to date. - If you specify an empty or invalid "md5" parameter, BitBake returns an md5 mis-match - error and displays the correct "md5" parameter value during the build. - The correct parameter is also captured in the build log. + If you specify an empty or invalid "md5" parameter, BitBake returns an md5 mis-match + error and displays the correct "md5" parameter value during the build. + The correct parameter is also captured in the build log. - If the whole file contains only license text, you do not need to use the "beginline" and - "endline" parameters. + If the whole file contains only license text, you do not need to use the "beginline" and + "endline" parameters.
@@ -820,10 +820,10 @@ By default, the OpenEmbedded build system disables components that have commercial or other special licensing - requirements. + requirements. Such requirements are defined on a recipe-by-recipe basis through the LICENSE_FLAGS variable - definition in the affected recipe. + definition in the affected recipe. For instance, the $HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly recipe contains the following statement: @@ -839,7 +839,7 @@ definition to be enabled and included in an image, it needs to have a matching entry in the global LICENSE_FLAGS_WHITELIST variable, which is a variable - typically defined in your local.conf file. + typically defined in your local.conf file. For example, to enable the $HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly package, you could add either the string @@ -867,7 +867,7 @@ the initial underscore character or characters. A partial string will match any license that contains the given string as the first - portion of its license. + portion of its license. For example, the following whitelist string will also match both of the packages previously mentioned as well as any other packages that have @@ -879,7 +879,7 @@
License Flag Matching - + The definition of 'matching' in reference to a recipe's LICENSE_FLAGS setting is simple. @@ -891,7 +891,7 @@ Before a flag defined by a particular recipe is tested against the contents of the LICENSE_FLAGS_WHITELIST variable, the - string _${PN} (with + string _${PN} (with PN expanded of course) is appended to the flag, thus automatically making each LICENSE_FLAGS value recipe-specific. @@ -907,7 +907,7 @@ You can broaden the match by putting any "_"-separated beginning subset of a LICENSE_FLAGS flag in the whitelist, which will also - match. + match. For example, simply specifying "commercial" in the whitelist would match any expanded LICENSE_FLAGS definition starting with "commercial" such as @@ -923,7 +923,7 @@ Broadening the match allows for a range of specificity for the items in the whitelist, from more general to perfectly - specific. + specific. So you have the choice of exhaustively enumerating each license flag in the whitelist to allow only those specific recipes into the image, or @@ -935,7 +935,7 @@ This scheme works even if the flag already has _${PN} appended - the extra _${PN} is - redundant, but does not affect the outcome. + redundant, but does not affect the outcome. For example, a license flag of "commercial_1.2_foo" would turn into "commercial_1.2_foo_foo" and would match both the general "commercial" and the specific @@ -944,8 +944,8 @@ "commercial_1.2_foo_foo" and "commercial_1.2", which does not make much sense regarding use in the whitelist. - - + + For a versioned string, you could instead specify "commercial_foo_1.2", which would turn into "commercial_foo_1.2_foo". @@ -993,8 +993,8 @@ - Specifying audio and video plug-ins as part of the - COMMERCIAL_AUDIO_PLUGINS and + Specifying audio and video plug-ins as part of the + COMMERCIAL_AUDIO_PLUGINS and COMMERCIAL_VIDEO_PLUGINS statements or commercial qt components as part of the COMMERCIAL_QT statement (along @@ -1006,6 +1006,6 @@
- diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index e5b5edb846..286b5fa783 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml @@ -17,8 +17,8 @@ This section provides a summary of the build process and provides information for less obvious aspects of the build process. - For general information on how to build an image using the OpenEmbedded build - system, see the + For general information on how to build an image using the OpenEmbedded build + system, see the "Building an Image" section of the Yocto Project Quick Start. @@ -35,12 +35,12 @@ - The build_dir is optional and specifies the directory the - OpenEmbedded build system uses for the build - + The build_dir is optional and specifies the directory the + OpenEmbedded build system uses for the build - the Build Directory. If you do not specify a Build Directory it defaults to build in your current working directory. - A common practice is to use a different Build Directory for different targets. + A common practice is to use a different Build Directory for different targets. For example, ~/build/x86 for a qemux86 target, and ~/build/arm for a qemuarm target. See &OE_INIT_FILE; @@ -55,13 +55,13 @@ - The target is the name of the recipe you want to build. + The target is the name of the recipe you want to build. Common targets are the images in meta/recipes-core/images, - /meta/recipes-sato/images, etc. all found in the + /meta/recipes-sato/images, etc. all found in the Source Directory. - Or, the target can be the name of a recipe for a specific piece of software such as - busybox. - For more details about the images the OpenEmbedded build system supports, see the + Or, the target can be the name of a recipe for a specific piece of software such as + busybox. + For more details about the images the OpenEmbedded build system supports, see the "Images" chapter. @@ -76,9 +76,9 @@ Building an Image Using GPL Components - When building an image using GPL components, you need to maintain your original + When building an image using GPL components, you need to maintain your original settings and not switch back and forth applying different versions of the GNU - General Public License. + General Public License. If you rebuild using different versions of GPL, dependency errors might occur due to some components not being rebuilt. @@ -89,11 +89,11 @@ Installing and Using the Result - Once an image has been built, it often needs to be installed. - The images and kernels built by the OpenEmbedded build system are placed in the - Build Directory in - tmp/deploy/images. - For information on how to run pre-built images such as qemux86 + Once an image has been built, it often needs to be installed. + The images and kernels built by the OpenEmbedded build system are placed in the + Build Directory in + tmp/deploy/images. + For information on how to run pre-built images such as qemux86 and qemuarm, see the "Using Pre-Built Binaries and QEMU" section in the Yocto Project Quick Start. @@ -106,25 +106,25 @@ Debugging Build Failures - The exact method for debugging build failures depends on the nature of the - problem and on the system's area from which the bug originates. - Standard debugging practices such as comparison against the last - known working version with examination of the changes and the re-application of steps + The exact method for debugging build failures depends on the nature of the + problem and on the system's area from which the bug originates. + Standard debugging practices such as comparison against the last + known working version with examination of the changes and the re-application of steps to identify the one causing the problem are - valid for the Yocto Project just as they are for any other system. - Even though it is impossible to detail every possible potential failure, + valid for the Yocto Project just as they are for any other system. + Even though it is impossible to detail every possible potential failure, this section provides some general tips to aid in debugging.
Task Failures - The log file for shell tasks is available in - ${WORKDIR}/temp/log.do_taskname.pid. + The log file for shell tasks is available in + ${WORKDIR}/temp/log.do_taskname.pid. For example, the compile task for the QEMU minimal image for the x86 - machine (qemux86) might be + machine (qemux86) might be tmp/work/qemux86-poky-linux/core-image-minimal-1.0-r0/temp/log.do_compile.20830. - To see what BitBake runs to generate that log, look at the corresponding + To see what BitBake runs to generate that log, look at the corresponding run.do_taskname.pid file located in the same directory. @@ -137,17 +137,17 @@ Running Specific Tasks - Any given package consists of a set of tasks. - The standard BitBake behavior in most cases is: fetch, - unpack, + Any given package consists of a set of tasks. + The standard BitBake behavior in most cases is: fetch, + unpack, patch, configure, compile, install, package, - package_write, and build. - The default task is build and any tasks on which it depends + package_write, and build. + The default task is build and any tasks on which it depends build first. Some tasks exist, such as devshell, that are not part of the - default build chain. - If you wish to run a task that is not part of the default build chain, you can use the + default build chain. + If you wish to run a task that is not part of the default build chain, you can use the -c option in BitBake as follows: $ bitbake matchbox-desktop -c devshell @@ -155,8 +155,8 @@ - If you wish to rerun a task, use the -f force option. - For example, the following sequence forces recompilation after changing files in the + If you wish to rerun a task, use the -f force option. + For example, the following sequence forces recompilation after changing files in the working directory. $ bitbake matchbox-desktop @@ -173,7 +173,7 @@ This sequence first builds matchbox-desktop and then recompiles it. The last command reruns all tasks (basically the packaging tasks) after the compile. - BitBake recognizes that the compile task was rerun and therefore + BitBake recognizes that the compile task was rerun and therefore understands that the other tasks also need to be run again. @@ -191,13 +191,13 @@ Dependency Graphs - Sometimes it can be hard to see why BitBake wants to build some other packages before a given + Sometimes it can be hard to see why BitBake wants to build some other packages before a given package you have specified. - The bitbake -g targetname command creates the + The bitbake -g targetname command creates the depends.dot, package-depends.dot, - and task-depends.dot files in the current directory. + and task-depends.dot files in the current directory. These files show the package and task dependencies and are useful for debugging problems. - You can use the bitbake -g -u depexp targetname command to + You can use the bitbake -g -u depexp targetname command to display the results in a more human-readable form.
@@ -208,7 +208,7 @@ You can see debug output from BitBake by using the -D option. The debug output gives more information about what BitBake - is doing and the reason behind it. + is doing and the reason behind it. Each -D option you use increases the logging level. The most common usage is -DDD. @@ -217,7 +217,7 @@ The output from bitbake -DDD -v targetname can reveal why BitBake chose a certain version of a package or why BitBake picked a certain provider. - This command could also help you in a situation where you think BitBake did something + This command could also help you in a situation where you think BitBake did something unexpected. @@ -226,9 +226,9 @@ Building with No Dependencies If you really want to build a specific .bb file, you can use - the command form bitbake -b <somepath/somefile.bb>. + the command form bitbake -b <somepath/somefile.bb>. This command form does not check for dependencies so you should use it - only when you know its dependencies already exist. + only when you know its dependencies already exist. You can also specify fragments of the filename. In this case, BitBake checks for a unique match. @@ -243,31 +243,31 @@ to show the environment from parsing a single recipe file only. - +
Recipe Logging Mechanisms - Best practices exist while writing recipes that both log build progress and - act on build conditions such as warnings and errors. + Best practices exist while writing recipes that both log build progress and + act on build conditions such as warnings and errors. Both Python and Bash language bindings exist for the logging mechanism: Python: For Python functions, BitBake - supports several loglevels: bb.fatal, + supports several loglevels: bb.fatal, bb.error, bb.warn, bb.note, bb.plain, and bb.debug. - Bash: For Bash functions, the same set + Bash: For Bash functions, the same set of loglevels exist and are accessed with a similar syntax: - bbfatal, bberror, - bbwarn, bbnote, + bbfatal, bberror, + bbwarn, bbnote, bbplain, and bbdebug. - For guidance on how logging is handled in both Python and Bash recipes, see the - logging.bbclass file in the - meta/classes folder of the + For guidance on how logging is handled in both Python and Bash recipes, see the + logging.bbclass file in the + meta/classes folder of the Source Directory. @@ -275,14 +275,14 @@ Logging With Python When creating recipes using Python and inserting code that handles build logs - keep in mind the goal is to have informative logs while keeping the console as - "silent" as possible. + keep in mind the goal is to have informative logs while keeping the console as + "silent" as possible. Also, if you want status messages in the log use the "debug" loglevel. Following is an example written in Python. - The code handles logging for a function that determines the number of tasks + The code handles logging for a function that determines the number of tasks needed to be run: python do_listtasks() { @@ -307,8 +307,8 @@ Logging With Bash When creating recipes using Bash and inserting code that handles build - logs you have the same goals - informative with minimal console output. - The syntax you use for recipes written in Bash is similar to that of + logs you have the same goals - informative with minimal console output. + The syntax you use for recipes written in Bash is similar to that of recipes written in Python described in the previous section. @@ -337,22 +337,22 @@
- +
Other Tips Here are some other tips that you might find useful: - When adding new packages, it is worth watching for + When adding new packages, it is worth watching for undesirable items making their way into compiler command lines. - For example, you do not want references to local system files like + For example, you do not want references to local system files like /usr/lib/ or /usr/include/. - If you want to remove the psplash boot splashscreen, + If you want to remove the psplash boot splashscreen, add psplash=false to the kernel command line. Doing so prevents psplash from loading and thus allows you to see the console. - It is also possible to switch out of the splashscreen by + It is also possible to switch out of the splashscreen by switching the virtual console (e.g. Fn+Left or Fn+Right on a Zaurus). @@ -365,25 +365,25 @@ A build's quality can be influenced by many things. - For example, if you upgrade a recipe to use a new version of an upstream software + For example, if you upgrade a recipe to use a new version of an upstream software package or you experiment with some new configuration options, subtle changes - can occur that you might not detect until later. + can occur that you might not detect until later. Consider the case where your recipe is using a newer version of an upstream package. - In this case, a new version of a piece of software might introduce an optional + In this case, a new version of a piece of software might introduce an optional dependency on another library, which is auto-detected. - If that library has already been built when the software is building, - then the software will link to the built library and that library will be pulled - into your image along with the new software even if you did not want the + If that library has already been built when the software is building, + then the software will link to the built library and that library will be pulled + into your image along with the new software even if you did not want the library. The buildhistory class exists to help you maintain the quality of your build output. - You can use the class to highlight unexpected and possibly unwanted + You can use the class to highlight unexpected and possibly unwanted changes in the build output. - When you enable build history it records information about the contents of - each package and image and then commits that information to a local Git + When you enable build history it records information about the contents of + each package and image and then commits that information to a local Git repository where you can examine the information. @@ -396,7 +396,7 @@ How to limit the information used for build history - How to examine the build history from both a + How to examine the build history from both a command-line and web interface @@ -406,41 +406,41 @@ Build history is disabled by default. - To enable it, add the following statements to the end of your - conf/local.conf file found in the + To enable it, add the following statements to the end of your + conf/local.conf file found in the Build Directory: INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "1" - Enabling build history as previously described + Enabling build history as previously described causes the build process to collect build - output information and commit it to a local + output information and commit it to a local Git repository. - Enabling build history increases your build times slightly, + Enabling build history increases your build times slightly, particularly for images, and increases the amount of disk space used during the build. - + You can disable build history by removing the previous statements from your conf/local.conf file. - However, you should realize that enabling and disabling - build history in this manner can change the - do_package task checksums, which if you - are using the OEBasicHash signature generator (the default + However, you should realize that enabling and disabling + build history in this manner can change the + do_package task checksums, which if you + are using the OEBasicHash signature generator (the default for many current distro configurations including - DISTRO = "poky" and - DISTRO = "") will result in the packaging + DISTRO = "poky" and + DISTRO = "") will result in the packaging tasks being re-run during the subsequent build. - To disable the build history functionality without causing the - packaging tasks to be re-run, add just this statement to your - conf/local.conf file: + To disable the build history functionality without causing the + packaging tasks to be re-run, add just this statement to your + conf/local.conf file: BUILDHISTORY_FEATURES = "" @@ -451,19 +451,19 @@ Understanding What the Build History Contains - Build history information is kept in + Build history information is kept in $TMPDIR/buildhistory in the Build Directory. The following is an example abbreviated listing: - +
Build History Package Information The history for each package contains a text file that has - name-value pairs with information about the package. + name-value pairs with information about the package. For example, buildhistory/packages/core2-poky-linux/busybox/busybox/latest contains the following: @@ -474,21 +474,21 @@ PKGSIZE = 564701 FILES = /usr/bin/* /usr/sbin/* /usr/libexec/* /usr/lib/lib*.so.* \ /etc /com /var /bin/* /sbin/* /lib/*.so.* /usr/share/busybox \ - /usr/lib/busybox/* /usr/share/pixmaps /usr/share/applications \ + /usr/lib/busybox/* /usr/share/pixmaps /usr/share/applications \ /usr/share/idl /usr/share/omf /usr/share/sounds /usr/lib/bonobo/servers FILELIST = /etc/busybox.links /etc/init.d/hwclock.sh /bin/busybox /bin/sh - Most of these name-value pairs corresponds to variables used + Most of these name-value pairs corresponds to variables used to produce the package. - The exceptions are FILELIST, which is the - actual list of files in the package, and - PKGSIZE, which is the total size of files + The exceptions are FILELIST, which is the + actual list of files in the package, and + PKGSIZE, which is the total size of files in the package in bytes. - There is also a file corresponding to the recipe from which the - package came (e.g. + There is also a file corresponding to the recipe from which the + package came (e.g. buildhistory/packages/core2-poky-linux/busybox/latest): PV = 1.19.3 @@ -509,18 +509,18 @@ The files produced for each image are as follows: build-id: - Human-readable information about the build configuration + Human-readable information about the build configuration and metadata source revisions. *.dot: - Dependency graphs for the image that are + Dependency graphs for the image that are compatible with graphviz. files-in-image.txt: - A list of files in the image with permissions, + A list of files in the image with permissions, owner, group, size, and symlink information. image-info.txt: - A text file containing name-value pairs with information + A text file containing name-value pairs with information about the image. See the following listing example for more information. @@ -535,7 +535,7 @@ Installed package information is able to be gathered and - produced even if package management is disabled for the final + produced even if package management is disabled for the final image. @@ -551,15 +551,15 @@ package-management ssh-server-dropbear package-management IMAGE_LINGUAS = en-us en-gb IMAGE_INSTALL = task-core-boot task-base-extended - BAD_RECOMMENDATIONS = - ROOTFS_POSTPROCESS_COMMAND = buildhistory_get_image_installed ; rootfs_update_timestamp ; - IMAGE_POSTPROCESS_COMMAND = buildhistory_get_imageinfo ; + BAD_RECOMMENDATIONS = + ROOTFS_POSTPROCESS_COMMAND = buildhistory_get_image_installed ; rootfs_update_timestamp ; + IMAGE_POSTPROCESS_COMMAND = buildhistory_get_imageinfo ; IMAGESIZE = 171816 Other than IMAGESIZE, which is the - total size of the files in the image in Kbytes, the - name-value pairs are variables that may have influenced the - content of the image. + total size of the files in the image in Kbytes, the + name-value pairs are variables that may have influenced the + content of the image. This information is often useful when you are trying to determine why a change in the package or file listings has occurred. @@ -568,15 +568,15 @@
Using Build History to Gather Image Information Only - - As you can see, build history produces image information, + + As you can see, build history produces image information, including dependency graphs, so you can see why something - was pulled into the image. - If you are just interested in this information and not - interested in collecting history or any package information, - you can enable writing only image information without - any history by adding the following - to your conf/local.conf file found in the + was pulled into the image. + If you are just interested in this information and not + interested in collecting history or any package information, + you can enable writing only image information without + any history by adding the following + to your conf/local.conf file found in the Build Directory: INHERIT += "buildhistory" @@ -590,28 +590,28 @@ Examining Build History Information - You can examine build history output from the command line or + You can examine build history output from the command line or from a web interface. - To see any changes that have occurred (assuming you have - BUILDHISTORY_COMMIT = "1"), you can simply - use any Git command that allows you to view the history of - a repository. + To see any changes that have occurred (assuming you have + BUILDHISTORY_COMMIT = "1"), you can simply + use any Git command that allows you to view the history of + a repository. Here is one method: - $ git log -p + $ git log -p - You need to realize, however, that this method does show - changes that are not significant (e.g. a package's size + You need to realize, however, that this method does show + changes that are not significant (e.g. a package's size changing by a few bytes). A command-line tool called buildhistory-diff - does exist though that queries the Git repository and prints just - the differences that might be significant in human-readable form. + does exist though that queries the Git repository and prints just + the differences that might be significant in human-readable form. Here is an example: $ ~/poky/poky/scripts/buildhistory-diff . HEAD^ @@ -632,7 +632,7 @@ - To see changes to the build history using a web interface, follow + To see changes to the build history using a web interface, follow the instruction in the README file here. . @@ -646,6 +646,6 @@
- -- cgit v1.2.3-54-g00ecf