summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-local-configuration.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-recipes.html29
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-image-information.html80
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-package-information.html58
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html61
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/building-an-image-using-gpl-components.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/centos-packages.html69
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/checksums.html164
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html43
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/detailed-supported-distros.html45
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-and-disabling-build-history.html62
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-commercially-licensed-recipes.html85
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html70
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/faq.html791
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/fedora-packages.html62
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/future-development-and-limitations.html33
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/handbook.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/index.html327
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/index.xml2
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit-dev.html26
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit.html35
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/intro-manualoverview.html73
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/intro-requirements.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/intro-welcome.html30
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/intro.html30
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/invalidating-shared-state.html53
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/license-flag-matching.html91
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/licenses.html28
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-bash.html47
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html45
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html53
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-bblayers-conf.html27
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-image-features.html26
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-nativesdk.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-proto=-in-src-uri.html32
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-python-function-whitespace.html29
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-removed-recipes.html64
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-sstate-mirrors.html36
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-task-recipes.html39
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/migration.html31
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/moving-to-the-yocto-project-1.3-release.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/opensuse-packages.html60
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html60
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html31
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html41
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-commandline.html79
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-dependencies.html34
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-fetchers.html43
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-parsing.html93
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html63
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-runtask.html86
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html54
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake.html48
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-autotools.html52
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-base.html28
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-binconfig.html30
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-debian.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-devshell.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-distutils.html31
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-externalsrc.html72
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-image.html31
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-insane.html105
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-kernel.html36
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-others.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html73
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-packagegroup.html33
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-perl.html31
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-pkgconfig.html27
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-sanity.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-siteinfo.html39
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-src-distribute.html43
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-alternatives.html48
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-rc.d.html28
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-useradd.html28
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes.html61
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-backfill.html88
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-distro.html68
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-image.html73
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-machine.html63
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features.html60
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html137
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-structure.html98
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-variables-glos.html2800
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-distro.html40
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-local.html42
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-machine.html41
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-configuration.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-build.html33
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-dependencies.html33
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-paths.html29
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-required.html30
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipes.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality.html41
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/required-packages-for-the-host-development-system.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources-bugtracker.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources-contributions.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources-intro.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources-irc.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources-links.html42
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources-mailinglist.html39
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/resources.html27
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state-cache.html60
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state.html134
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-basic-top-level.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-bblayers.conf.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-local.conf.html37
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-sanity_info.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-downloads.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-pseudodone.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-sstate-cache.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-buildstats.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-cache.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-deb.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html44
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-ipk.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-licenses.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-rpm.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-log.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-pkgdata.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-stamps.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-sysroots.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html52
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp.html26
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build.html15
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-bitbake.html40
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-build.html33
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto-bsp.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html53
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-scripts.html28
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core.html14
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-classes.html30
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-distro.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-machine.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf.html27
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-hob.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-bsp.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-connectivity.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-core.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-devtools.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-extended.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-gnome.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-graphics.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-kernel.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-multimedia.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-qt.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-rt.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-sato.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-support.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-txt.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-site.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-skeleton.html20
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta.html21
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/support.html34
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/technical-details.html50
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/tips-and-tricks.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/ubuntu-packages.html60
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/understanding-what-the-build-history-contains.html25
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/using-build-history-to-gather-image-information-only.html34
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/using-x32-right-now.html70
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html58
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-build.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html66
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-classes.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-configuration.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-metadata.html29
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components.html52
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-configuring-LIC_FILES_CHKSUM.html23
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-bitbake.html30
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-buildfile.html24
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-dependencies.html26
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-others.html34
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskfailures.html27
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html68
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-variables.html22
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html26
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-install.html28
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-specifying-LIC_FILES_CHKSUM.html57
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky.html48
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/x32.html35
-rw-r--r--documentation/ref-manual/eclipse/poky-ref-manual-toc.xml217
-rw-r--r--documentation/ref-manual/ref-manual.xml2
184 files changed, 1 insertions, 11127 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-local-configuration.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-local-configuration.html
deleted file mode 100644
index d4a9f0875d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-local-configuration.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.1. Local Configuration</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="moving-to-the-yocto-project-1.3-release.html" title="4.1. Moving to the Yocto Project 1.3 Release">
9<link rel="prev" href="moving-to-the-yocto-project-1.3-release.html" title="4.1. Moving to the Yocto Project 1.3 Release">
10<link rel="next" href="migration-1.3-sstate-mirrors.html" title="4.1.1.1. SSTATE_MIRRORS">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.1. Local Configuration">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="1.3-local-configuration"></a>4.1.1. Local Configuration</h3></div></div></div>
15<p>
16 Differences include changes for
17 <a class="link" href="ref-variables-glos.html#var-SSTATE_MIRRORS" title="SSTATE_MIRRORS"><code class="filename">SSTATE_MIRRORS</code></a>
18 and <code class="filename">bblayers.conf</code>.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-recipes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-recipes.html
deleted file mode 100644
index 69966945f2..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/1.3-recipes.html
+++ /dev/null
@@ -1,29 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2. Recipes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="moving-to-the-yocto-project-1.3-release.html" title="4.1. Moving to the Yocto Project 1.3 Release">
9<link rel="prev" href="migration-1.3-bblayers-conf.html" title="4.1.1.2. bblayers.conf">
10<link rel="next" href="migration-1.3-python-function-whitespace.html" title="4.1.2.1. Python Function Whitespace">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2. Recipes">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="1.3-recipes"></a>4.1.2. Recipes</h3></div></div></div>
15<p>
16 Differences include changes for the following:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p>Python function whitespace</p></li>
20<li class="listitem"><p><code class="filename">proto=</code> in <code class="filename">SRC_URI</code></p></li>
21<li class="listitem"><p><code class="filename">nativesdk</code></p></li>
22<li class="listitem"><p>Task recipes</p></li>
23<li class="listitem"><p><code class="filename">IMAGE_FEATURES</code></p></li>
24<li class="listitem"><p>Removed recipes</p></li>
25</ul></div>
26<p>
27 </p>
28</div></body>
29</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-image-information.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-image-information.html
deleted file mode 100644
index f1b0f9e2ad..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-image-information.html
+++ /dev/null
@@ -1,80 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.2.2. Build History Image Information</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
9<link rel="prev" href="build-history-package-information.html" title="2.4.2.1. Build History Package Information">
10<link rel="next" href="using-build-history-to-gather-image-information-only.html" title="2.4.2.3. Using Build History to Gather Image Information Only">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.2.2. Build History Image Information">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="build-history-image-information"></a>2.4.2.2. Build History Image Information</h4></div></div></div>
15<p>
16 The files produced for each image are as follows:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><span class="emphasis"><em>build-id:</em></span>
20 Human-readable information about the build configuration
21 and metadata source revisions.</p></li>
22<li class="listitem"><p><span class="emphasis"><em>*.dot:</em></span>
23 Dependency graphs for the image that are
24 compatible with <code class="filename">graphviz</code>.
25 </p></li>
26<li class="listitem"><p><span class="emphasis"><em>files-in-image.txt:</em></span>
27 A list of files in the image with permissions,
28 owner, group, size, and symlink information.
29 </p></li>
30<li class="listitem"><p><span class="emphasis"><em>image-info.txt:</em></span>
31 A text file containing name-value pairs with information
32 about the image.
33 See the following listing example for more information.
34 </p></li>
35<li class="listitem"><p><span class="emphasis"><em>installed-package-names.txt:</em></span>
36 A list of installed packages by name only.</p></li>
37<li class="listitem"><p><span class="emphasis"><em>installed-package-sizes.txt:</em></span>
38 A list of installed packages ordered by size.
39 </p></li>
40<li class="listitem"><p><span class="emphasis"><em>installed-packages.txt:</em></span>
41 A list of installed packages with fuill package
42 filenames.</p></li>
43</ul></div>
44<p>
45 </p>
46<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
47<h3 class="title">Note</h3>
48 Installed package information is able to be gathered and
49 produced even if package management is disabled for the final
50 image.
51 </div>
52<p>
53 </p>
54<p>
55 Here is an example of <code class="filename">image-info.txt</code>:
56 </p>
57<pre class="literallayout">
58 DISTRO = poky
59 DISTRO_VERSION = 1.1+snapshot-20120207
60 USER_CLASSES = image-mklibs image-prelink
61 IMAGE_CLASSES = image_types
62 IMAGE_FEATURES = debug-tweaks x11-base apps-x11-core \
63 package-management ssh-server-dropbear package-management
64 IMAGE_LINGUAS = en-us en-gb
65 IMAGE_INSTALL = task-core-boot task-base-extended
66 BAD_RECOMMENDATIONS =
67 ROOTFS_POSTPROCESS_COMMAND = buildhistory_get_image_installed ; rootfs_update_timestamp ;
68 IMAGE_POSTPROCESS_COMMAND = buildhistory_get_imageinfo ;
69 IMAGESIZE = 171816
70 </pre>
71<p>
72 Other than <code class="filename">IMAGESIZE</code>, which is the
73 total size of the files in the image in Kbytes, the
74 name-value pairs are variables that may have influenced the
75 content of the image.
76 This information is often useful when you are trying to determine
77 why a change in the package or file listings has occurred.
78 </p>
79</div></body>
80</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-package-information.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-package-information.html
deleted file mode 100644
index 370481da75..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-history-package-information.html
+++ /dev/null
@@ -1,58 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.2.1. Build History Package Information</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
9<link rel="prev" href="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
10<link rel="next" href="build-history-image-information.html" title="2.4.2.2. Build History Image Information">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.2.1. Build History Package Information">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="build-history-package-information"></a>2.4.2.1. Build History Package Information</h4></div></div></div>
15<p>
16 The history for each package contains a text file that has
17 name-value pairs with information about the package.
18 For example, <code class="filename">buildhistory/packages/core2-poky-linux/busybox/busybox/latest</code>
19 contains the following:
20 </p>
21<pre class="literallayout">
22 PV = 1.19.3
23 PR = r3
24 RDEPENDS = update-rc.d eglibc (&gt;= 2.13)
25 RRECOMMENDS = busybox-syslog busybox-udhcpc
26 PKGSIZE = 564701
27 FILES = /usr/bin/* /usr/sbin/* /usr/libexec/* /usr/lib/lib*.so.* \
28 /etc /com /var /bin/* /sbin/* /lib/*.so.* /usr/share/busybox \
29 /usr/lib/busybox/* /usr/share/pixmaps /usr/share/applications \
30 /usr/share/idl /usr/share/omf /usr/share/sounds /usr/lib/bonobo/servers
31 FILELIST = /etc/busybox.links /etc/init.d/hwclock.sh /bin/busybox /bin/sh
32 </pre>
33<p>
34 Most of these name-value pairs corresponds to variables used
35 to produce the package.
36 The exceptions are <code class="filename">FILELIST</code>, which is the
37 actual list of files in the package, and
38 <code class="filename">PKGSIZE</code>, which is the total size of files
39 in the package in bytes.
40 </p>
41<p>
42 There is also a file corresponding to the recipe from which the
43 package came (e.g.
44 <code class="filename">buildhistory/packages/core2-poky-linux/busybox/latest</code>):
45 </p>
46<pre class="literallayout">
47 PV = 1.19.3
48 PR = r3
49 DEPENDS = virtual/i586-poky-linux-gcc virtual/i586-poky-linux-compilerlibs \
50 virtual/libc update-rc.d-native
51 PACKAGES = busybox-httpd busybox-udhcpd busybox-udhcpc busybox-syslog \
52 busybox-mdev busybox-dbg busybox busybox-doc busybox-dev \
53 busybox-staticdev busybox-locale
54 </pre>
55<p>
56 </p>
57</div></body>
58</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html
deleted file mode 100644
index 4ee4185ba9..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html
+++ /dev/null
@@ -1,61 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.1.1. Build Overview</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-build.html" title="2.1. Running a Build">
9<link rel="prev" href="usingpoky-build.html" title="2.1. Running a Build">
10<link rel="next" href="building-an-image-using-gpl-components.html" title="2.1.2. Building an Image Using GPL Components">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.1. Build Overview">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="build-overview"></a>2.1.1. Build Overview</h3></div></div></div>
15<p>
16 The first thing you need to do is set up the OpenEmbedded build environment by sourcing
17 the <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">environment setup script</a> as follows:
18 </p>
19<pre class="literallayout">
20 $ source oe-init-build-env [build_dir]
21 </pre>
22<p>
23 </p>
24<p>
25 The <code class="filename">build_dir</code> is optional and specifies the directory the
26 OpenEmbedded build system uses for the build -
27 the <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
28 If you do not specify a Build Directory it defaults to <code class="filename">build</code>
29 in your current working directory.
30 A common practice is to use a different Build Directory for different targets.
31 For example, <code class="filename">~/build/x86</code> for a <code class="filename">qemux86</code>
32 target, and <code class="filename">~/build/arm</code> for a <code class="filename">qemuarm</code> target.
33 See <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a>
34 for more information on this script.
35 </p>
36<p>
37 Once the build environment is set up, you can build a target using:
38 </p>
39<pre class="literallayout">
40 $ bitbake &lt;target&gt;
41 </pre>
42<p>
43 </p>
44<p>
45 The <code class="filename">target</code> is the name of the recipe you want to build.
46 Common targets are the images in <code class="filename">meta/recipes-core/images</code>,
47 <code class="filename">/meta/recipes-sato/images</code>, etc. all found in the
48 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
49 Or, the target can be the name of a recipe for a specific piece of software such as
50 <span class="application">busybox</span>.
51 For more details about the images the OpenEmbedded build system supports, see the
52 "<a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>" chapter.
53 </p>
54<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
55<h3 class="title">Note</h3>
56 Building an image without GNU General Public License Version 3 (GPLv3) components
57 is only supported for minimal and base images.
58 See the "<a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>" chapter for more information.
59 </div>
60</div></body>
61</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/building-an-image-using-gpl-components.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/building-an-image-using-gpl-components.html
deleted file mode 100644
index 12073d58d8..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/building-an-image-using-gpl-components.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.1.2. Building an Image Using GPL Components</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-build.html" title="2.1. Running a Build">
9<link rel="prev" href="build-overview.html" title="2.1.1. Build Overview">
10<link rel="next" href="usingpoky-install.html" title="2.2. Installing and Using the Result">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.2. Building an Image Using GPL Components">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="building-an-image-using-gpl-components"></a>2.1.2. Building an Image Using GPL Components</h3></div></div></div>
15<p>
16 When building an image using GPL components, you need to maintain your original
17 settings and not switch back and forth applying different versions of the GNU
18 General Public License.
19 If you rebuild using different versions of GPL, dependency errors might occur
20 due to some components not being rebuilt.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/centos-packages.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/centos-packages.html
deleted file mode 100644
index 05463bc93a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/centos-packages.html
+++ /dev/null
@@ -1,69 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3.2.4. CentOS Packages</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="required-packages-for-the-host-development-system.html" title="1.3.2. Required Packages for the Host Development System">
9<link rel="prev" href="opensuse-packages.html" title="1.3.2.3. OpenSUSE Packages">
10<link rel="next" href="intro-getit.html" title="1.4. Obtaining the Yocto Project">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.2.4. CentOS Packages">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="centos-packages"></a>1.3.2.4. CentOS Packages</h4></div></div></div>
15<p>
16 The following list shows the required packages by function
17 given a supported CentOS Linux distribution:
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem">
21<p><span class="emphasis"><em>Essentials:</em></span>
22 Packages needed to build an image for a headless
23 system:
24 </p>
25<pre class="literallayout">
26 $ sudo yum -y install gawk make wget tar bzip2 gzip python unzip perl patch \
27 diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath
28 </pre>
29</li>
30<li class="listitem">
31<p><span class="emphasis"><em>Graphical Extras:</em></span>
32 Packages recommended if the host system has graphics support:
33 </p>
34<pre class="literallayout">
35 $ sudo yum -y install SDL-devel xterm
36 </pre>
37</li>
38<li class="listitem">
39<p><span class="emphasis"><em>Documentation:</em></span>
40 Packages needed if you are going to build out the
41 Yocto Project documentation manuals:
42 </p>
43<pre class="literallayout">
44 $ sudo yum -y install make docbook-style-dsssl docbook-style-xsl \
45 docbook-dtds docbook-utils fop libxslt
46 </pre>
47</li>
48<li class="listitem">
49<p><span class="emphasis"><em>ADT Installer Extras:</em></span>
50 Packages needed if you are going to be using the
51 <a class="link" href="../adt-manual/using-the-adt-installer.html" target="_self">Application Development Toolkit (ADT) Installer</a>:
52 </p>
53<pre class="literallayout">
54 $ sudo yum -y install autoconf automake libtool glib2-devel
55 </pre>
56</li>
57</ul></div>
58<p>
59 </p>
60<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
61<h3 class="title">Note</h3>Depending on the CentOS version you are using, other requirements
62 and dependencies might exist.
63 For details, you should look at the CentOS sections on the
64 <a class="ulink" href="https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies" target="_self">Poky/GettingStarted/Dependencies</a>
65 wiki page.</div>
66<p>
67 </p>
68</div></body>
69</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/checksums.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/checksums.html
deleted file mode 100644
index 5dccce93b9..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/checksums.html
+++ /dev/null
@@ -1,164 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.2. Checksums (Signatures)</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="shared-state-cache.html" title="3.2. Shared State Cache">
9<link rel="prev" href="overall-architecture.html" title="3.2.1. Overall Architecture">
10<link rel="next" href="shared-state.html" title="3.2.3. Shared State">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.2. Checksums (Signatures)">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="checksums"></a>3.2.2. Checksums (Signatures)</h3></div></div></div>
15<p>
16 The shared state code uses a checksum, which is a unique signature of a task's
17 inputs, to determine if a task needs to be run again.
18 Because it is a change in a task's inputs that triggers a rerun, the process
19 needs to detect all the inputs to a given task.
20 For shell tasks, this turns out to be fairly easy because
21 the build process generates a "run" shell script for each task and
22 it is possible to create a checksum that gives you a good idea of when
23 the task's data changes.
24 </p>
25<p>
26 To complicate the problem, there are things that should not be included in
27 the checksum.
28 First, there is the actual specific build path of a given task -
29 the <code class="filename">WORKDIR</code>.
30 It does not matter if the working directory changes because it should not
31 affect the output for target packages.
32 Also, the build process has the objective of making native/cross packages relocatable.
33 The checksum therefore needs to exclude <code class="filename">WORKDIR</code>.
34 The simplistic approach for excluding the working directory is to set
35 <code class="filename">WORKDIR</code> to some fixed value and create the checksum
36 for the "run" script.
37 </p>
38<p>
39 Another problem results from the "run" scripts containing functions that
40 might or might not get called.
41 The incremental build solution contains code that figures out dependencies
42 between shell functions.
43 This code is used to prune the "run" scripts down to the minimum set,
44 thereby alleviating this problem and making the "run" scripts much more
45 readable as a bonus.
46 </p>
47<p>
48 So far we have solutions for shell scripts.
49 What about python tasks?
50 The same approach applies even though these tasks are more difficult.
51 The process needs to figure out what variables a python function accesses
52 and what functions it calls.
53 Again, the incremental build solution contains code that first figures out
54 the variable and function dependencies, and then creates a checksum for the data
55 used as the input to the task.
56 </p>
57<p>
58 Like the <code class="filename">WORKDIR</code> case, situations exist where dependencies
59 should be ignored.
60 For these cases, you can instruct the build process to ignore a dependency
61 by using a line like the following:
62 </p>
63<pre class="literallayout">
64 PACKAGE_ARCHS[vardepsexclude] = "MACHINE"
65 </pre>
66<p>
67 This example ensures that the <code class="filename">PACKAGE_ARCHS</code> variable does not
68 depend on the value of <code class="filename">MACHINE</code>, even if it does reference it.
69 </p>
70<p>
71 Equally, there are cases where we need to add dependencies BitBake is not able to find.
72 You can accomplish this by using a line like the following:
73 </p>
74<pre class="literallayout">
75 PACKAGE_ARCHS[vardeps] = "MACHINE"
76 </pre>
77<p>
78 This example explicitly adds the <code class="filename">MACHINE</code> variable as a
79 dependency for <code class="filename">PACKAGE_ARCHS</code>.
80 </p>
81<p>
82 Consider a case with inline python, for example, where BitBake is not
83 able to figure out dependencies.
84 When running in debug mode (i.e. using <code class="filename">-DDD</code>), BitBake
85 produces output when it discovers something for which it cannot figure out
86 dependencies.
87 The Yocto Project team has currently not managed to cover those dependencies
88 in detail and is aware of the need to fix this situation.
89 </p>
90<p>
91 Thus far, this section has limited discussion to the direct inputs into a task.
92 Information based on direct inputs is referred to as the "basehash" in the
93 code.
94 However, there is still the question of a task's indirect inputs - the
95 things that were already built and present in the Build Directory.
96 The checksum (or signature) for a particular task needs to add the hashes
97 of all the tasks on which the particular task depends.
98 Choosing which dependencies to add is a policy decision.
99 However, the effect is to generate a master checksum that combines the basehash
100 and the hashes of the task's dependencies.
101 </p>
102<p>
103 At the code level, there are a variety of ways both the basehash and the
104 dependent task hashes can be influenced.
105 Within the BitBake configuration file, we can give BitBake some extra information
106 to help it construct the basehash.
107 The following statements effectively result in a list of global variable
108 dependency excludes - variables never included in any checksum:
109 </p>
110<pre class="literallayout">
111 BB_HASHBASE_WHITELIST ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH"
112 BB_HASHBASE_WHITELIST += "DL_DIR SSTATE_DIR THISDIR FILESEXTRAPATHS"
113 BB_HASHBASE_WHITELIST += "FILE_DIRNAME HOME LOGNAME SHELL TERM USER"
114 BB_HASHBASE_WHITELIST += "FILESPATH USERNAME STAGING_DIR_HOST STAGING_DIR_TARGET"
115 </pre>
116<p>
117 The previous example actually excludes
118 <a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR"><code class="filename">WORKDIR</code></a>
119 since it is actually constructed as a path within
120 <a class="link" href="ref-variables-glos.html#var-TMPDIR" title="TMPDIR"><code class="filename">TMPDIR</code></a>, which is on
121 the whitelist.
122 </p>
123<p>
124 The rules for deciding which hashes of dependent tasks to include through
125 dependency chains are more complex and are generally accomplished with a
126 python function.
127 The code in <code class="filename">meta/lib/oe/sstatesig.py</code> shows two examples
128 of this and also illustrates how you can insert your own policy into the system
129 if so desired.
130 This file defines the two basic signature generators <code class="filename">OE-Core</code>
131 uses: "OEBasic" and "OEBasicHash".
132 By default, there is a dummy "noop" signature handler enabled in BitBake.
133 This means that behavior is unchanged from previous versions.
134 <code class="filename">OE-Core</code> uses the "OEBasic" signature handler by default
135 through this setting in the <code class="filename">bitbake.conf</code> file:
136 </p>
137<pre class="literallayout">
138 BB_SIGNATURE_HANDLER ?= "OEBasic"
139 </pre>
140<p>
141 The "OEBasicHash" <code class="filename">BB_SIGNATURE_HANDLER</code> is the same as the
142 "OEBasic" version but adds the task hash to the stamp files.
143 This results in any metadata change that changes the task hash, automatically
144 causing the task to be run again.
145 This removes the need to bump <a class="link" href="ref-variables-glos.html#var-PR" title="PR"><code class="filename">PR</code></a>
146 values and changes to metadata automatically ripple across the build.
147 Currently, this behavior is not the default behavior for <code class="filename">OE-Core</code>
148 but is the default in <code class="filename">poky</code>.
149 </p>
150<p>
151 It is also worth noting that the end result of these signature generators is to
152 make some dependency and hash information available to the build.
153 This information includes:
154 </p>
155<pre class="literallayout">
156 BB_BASEHASH_task-&lt;taskname&gt; - the base hashes for each task in the recipe
157 BB_BASEHASH_&lt;filename:taskname&gt; - the base hashes for each dependent task
158 BBHASHDEPS_&lt;filename:taskname&gt; - The task dependencies for each task
159 BB_TASKHASH - the hash of the currently running task
160 </pre>
161<p>
162 </p>
163</div></body>
164</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html
deleted file mode 100644
index 80a19f98a4..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html
+++ /dev/null
@@ -1,43 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.4.1. Debugging</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="tips-and-tricks.html" title="3.2.4. Tips and Tricks">
9<link rel="prev" href="tips-and-tricks.html" title="3.2.4. Tips and Tricks">
10<link rel="next" href="invalidating-shared-state.html" title="3.2.4.2. Invalidating Shared State">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.4.1. Debugging">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="debugging"></a>3.2.4.1. Debugging</h4></div></div></div>
15<p>
16 When things go wrong, debugging needs to be straightforward.
17 Because of this, the Yocto Project team included strong debugging
18 tools:
19 </p>
20<div class="itemizedlist"><ul class="itemizedlist" type="disc">
21<li class="listitem"><p>Whenever a shared state package is written out, so is a
22 corresponding <code class="filename">.siginfo</code> file.
23 This practice results in a pickled python database of all
24 the metadata that went into creating the hash for a given shared state
25 package.</p></li>
26<li class="listitem"><p>If BitBake is run with the <code class="filename">--dump-signatures</code>
27 (or <code class="filename">-S</code>) option, BitBake dumps out
28 <code class="filename">.siginfo</code> files in
29 the stamp directory for every task it would have executed instead of
30 building the specified target package.</p></li>
31<li class="listitem"><p>There is a <code class="filename">bitbake-diffsigs</code> command that
32 can process these <code class="filename">.siginfo</code> files.
33 If one file is specified, it will dump out the dependency
34 information in the file.
35 If two files are specified, it will compare the two files and dump out
36 the differences between the two.
37 This allows the question of "What changed between X and Y?" to be
38 answered easily.</p></li>
39</ul></div>
40<p>
41 </p>
42</div></body>
43</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/detailed-supported-distros.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/detailed-supported-distros.html
deleted file mode 100644
index 6222ae54cf..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/detailed-supported-distros.html
+++ /dev/null
@@ -1,45 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3.1. Supported Linux Distributions</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro-requirements.html" title="1.3. System Requirements">
9<link rel="prev" href="intro-requirements.html" title="1.3. System Requirements">
10<link rel="next" href="required-packages-for-the-host-development-system.html" title="1.3.2. Required Packages for the Host Development System">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.1. Supported Linux Distributions">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="detailed-supported-distros"></a>1.3.1. Supported Linux Distributions</h3></div></div></div>
15<p>
16 Currently, the Yocto Project is supported on the following distributions:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p>Ubuntu 10.04.4 LTS</p></li>
20<li class="listitem"><p>Ubuntu 11.10</p></li>
21<li class="listitem"><p>Ubuntu 12.04.1 LTS</p></li>
22<li class="listitem"><p>Ubuntu 12.04.1 LTS</p></li>
23<li class="listitem"><p>Ubuntu 12.10</p></li>
24<li class="listitem"><p>Fedora release 16 (Verne)</p></li>
25<li class="listitem"><p>Fedora release 17 (Beefy Miracle)</p></li>
26<li class="listitem"><p>Fedora release 18 (Spherical Cow)</p></li>
27<li class="listitem"><p>CentOS release 5.6 (Final)</p></li>
28<li class="listitem"><p>CentOS release 5.7 (Final)</p></li>
29<li class="listitem"><p>CentOS release 5.8 (Final)</p></li>
30<li class="listitem"><p>CentOS release 6.3 (Final)</p></li>
31<li class="listitem"><p>Debian GNU/Linux 6.0.6 (squeeze)</p></li>
32<li class="listitem"><p>openSUSE 11.4</p></li>
33<li class="listitem"><p>openSUSE 12.1</p></li>
34<li class="listitem"><p>openSUSE 12.2</p></li>
35</ul></div>
36<p>
37 </p>
38<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
39<h3 class="title">Note</h3>
40 For additional information on distributions that support the
41 Yocto Project, see the
42 <a class="ulink" href="https://wiki.yoctoproject.org/wiki/Distribution_Support" target="_self">Distribution Support</a> wiki page.
43 </div>
44</div></body>
45</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-and-disabling-build-history.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-and-disabling-build-history.html
deleted file mode 100644
index 06be8f5332..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-and-disabling-build-history.html
+++ /dev/null
@@ -1,62 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.1. Enabling and Disabling Build History</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="maintaining-build-output-quality.html" title="2.4. Maintaining Build Output Quality">
9<link rel="prev" href="maintaining-build-output-quality.html" title="2.4. Maintaining Build Output Quality">
10<link rel="next" href="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.1. Enabling and Disabling Build History">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="enabling-and-disabling-build-history"></a>2.4.1. Enabling and Disabling Build History</h3></div></div></div>
15<p>
16 Build history is disabled by default.
17 To enable it, add the following statements to the end of your
18 <code class="filename">conf/local.conf</code> file found in the
19 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>:
20 </p>
21<pre class="literallayout">
22 INHERIT += "buildhistory"
23 BUILDHISTORY_COMMIT = "1"
24 </pre>
25<p>
26 Enabling build history as previously described
27 causes the build process to collect build
28 output information and commit it to a local
29 <a class="link" href="../dev-manual/git.html" target="_self">Git</a> repository.
30 </p>
31<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
32<h3 class="title">Note</h3>
33 Enabling build history increases your build times slightly,
34 particularly for images, and increases the amount of disk
35 space used during the build.
36 </div>
37<p>
38 </p>
39<p>
40 You can disable build history by removing the previous statements
41 from your <code class="filename">conf/local.conf</code> file.
42 However, you should realize that enabling and disabling
43 build history in this manner can change the
44 <code class="filename">do_package</code> task checksums, which if you
45 are using the OEBasicHash signature generator (the default
46 for many current distro configurations including
47 <code class="filename">DISTRO = "poky"</code> and
48 <code class="filename">DISTRO = ""</code>) will result in the packaging
49 tasks being re-run during the subsequent build.
50 </p>
51<p>
52 To disable the build history functionality without causing the
53 packaging tasks to be re-run, add just this statement to your
54 <code class="filename">conf/local.conf</code> file:
55 </p>
56<pre class="literallayout">
57 BUILDHISTORY_FEATURES = ""
58 </pre>
59<p>
60 </p>
61</div></body>
62</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-commercially-licensed-recipes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-commercially-licensed-recipes.html
deleted file mode 100644
index 9ecf3cc128..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/enabling-commercially-licensed-recipes.html
+++ /dev/null
@@ -1,85 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4.2. Enabling Commercially Licensed Recipes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="licenses.html" title="3.4. Licenses">
9<link rel="prev" href="usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html" title="3.4.1.2. Explanation of Syntax">
10<link rel="next" href="license-flag-matching.html" title="3.4.2.1. License Flag Matching">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.2. Enabling Commercially Licensed Recipes">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="enabling-commercially-licensed-recipes"></a>3.4.2. Enabling Commercially Licensed Recipes</h3></div></div></div>
15<p>
16 By default, the OpenEmbedded build system disables
17 components that have commercial or other special licensing
18 requirements.
19 Such requirements are defined on a
20 recipe-by-recipe basis through the <code class="filename">LICENSE_FLAGS</code> variable
21 definition in the affected recipe.
22 For instance, the
23 <code class="filename">$HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</code>
24 recipe contains the following statement:
25 </p>
26<pre class="literallayout">
27 LICENSE_FLAGS = "commercial"
28 </pre>
29<p>
30 Here is a slightly more complicated example that contains both an
31 explicit recipe name and version (after variable expansion):
32 </p>
33<pre class="literallayout">
34 LICENSE_FLAGS = "license_${PN}_${PV}"
35 </pre>
36<p>
37 In order for a component restricted by a <code class="filename">LICENSE_FLAGS</code>
38 definition to be enabled and included in an image, it
39 needs to have a matching entry in the global
40 <code class="filename">LICENSE_FLAGS_WHITELIST</code> variable, which is a variable
41 typically defined in your <code class="filename">local.conf</code> file.
42 For example, to enable
43 the <code class="filename">$HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</code>
44 package, you could add either the string
45 "commercial_gst-plugins-ugly" or the more general string
46 "commercial" to <code class="filename">LICENSE_FLAGS_WHITELIST</code>.
47 See the
48 "<a class="link" href="license-flag-matching.html" title="3.4.2.1. License Flag Matching">License Flag Matching</a>" section
49 for a full explanation of how <code class="filename">LICENSE_FLAGS</code> matching works.
50 Here is the example:
51 </p>
52<pre class="literallayout">
53 LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly"
54 </pre>
55<p>
56 Likewise, to additionally enable the package built from the recipe containing
57 <code class="filename">LICENSE_FLAGS = "license_${PN}_${PV}"</code>, and assuming
58 that the actual recipe name was <code class="filename">emgd_1.10.bb</code>,
59 the following string would enable that package as well as
60 the original <code class="filename">gst-plugins-ugly</code> package:
61 </p>
62<pre class="literallayout">
63 LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly license_emgd_1.10"
64 </pre>
65<p>
66 As a convenience, you do not need to specify the complete license string
67 in the whitelist for every package.
68 you can use an abbreviated form, which consists
69 of just the first portion or portions of the license string before
70 the initial underscore character or characters.
71 A partial string will match
72 any license that contains the given string as the first
73 portion of its license.
74 For example, the following
75 whitelist string will also match both of the packages
76 previously mentioned as well as any other packages that have
77 licenses starting with "commercial" or "license".
78 </p>
79<pre class="literallayout">
80 LICENSE_FLAGS_WHITELIST = "commercial license"
81 </pre>
82<p>
83 </p>
84</div></body>
85</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html
deleted file mode 100644
index 0fa3f74545..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/examining-build-history-information.html
+++ /dev/null
@@ -1,70 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.2.4. Examining Build History Information</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
9<link rel="prev" href="using-build-history-to-gather-image-information-only.html" title="2.4.2.3. Using Build History to Gather Image Information Only">
10<link rel="next" href="technical-details.html" title="Chapter 3. Technical Details">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.2.4. Examining Build History Information">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="examining-build-history-information"></a>2.4.2.4. Examining Build History Information</h4></div></div></div>
15<p>
16 You can examine build history output from the command line or
17 from a web interface.
18 </p>
19<p>
20 To see any changes that have occurred (assuming you have
21 <code class="filename">BUILDHISTORY_COMMIT = "1"</code>), you can simply
22 use any Git command that allows you to view the history of
23 a repository.
24 Here is one method:
25 </p>
26<pre class="literallayout">
27 $ git log -p
28 </pre>
29<p>
30 You need to realize, however, that this method does show
31 changes that are not significant (e.g. a package's size
32 changing by a few bytes).
33 </p>
34<p>
35 A command-line tool called <code class="filename">buildhistory-diff</code>
36 does exist though that queries the Git repository and prints just
37 the differences that might be significant in human-readable form.
38 Here is an example:
39 </p>
40<pre class="literallayout">
41 $ ~/poky/poky/scripts/buildhistory-diff . HEAD^
42 Changes to images/qemux86_64/eglibc/core-image-minimal (files-in-image.txt):
43 /etc/anotherpkg.conf was added
44 /sbin/anotherpkg was added
45 * (installed-package-names.txt):
46 * anotherpkg was added
47 Changes to images/qemux86_64/eglibc/core-image-minimal (installed-package-names.txt):
48 anotherpkg was added
49 packages/qemux86_64-poky-linux/v86d: PACKAGES: added "v86d-extras"
50 * PR changed from "r0" to "r1"
51 * PV changed from "0.1.10" to "0.1.12"
52 packages/qemux86_64-poky-linux/v86d/v86d: PKGSIZE changed from 110579 to 144381 (+30%)
53 * PR changed from "r0" to "r1"
54 * PV changed from "0.1.10" to "0.1.12"
55 </pre>
56<p>
57 </p>
58<p>
59 To see changes to the build history using a web interface, follow
60 the instruction in the <code class="filename">README</code> file here.
61 <a class="ulink" href="http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/" target="_self">http://git.yoctoproject.org/cgit/cgit.cgi/buildhistory-web/</a>.
62 </p>
63<p>
64 Here is a sample screenshot of the interface:
65 </p>
66<table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="130%"><tr><td align="center"><img src="figures/buildhistory-web.png" align="middle" height="468"></td></tr></table>
67<p>
68 </p>
69</div></body>
70</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/faq.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/faq.html
deleted file mode 100644
index 8b8cafbc3a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/faq.html
+++ /dev/null
@@ -1,791 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 12. FAQ</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="ref-varlocality-recipe-build.html" title="11.2.4. Extra Build Information">
10<link rel="next" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 12. FAQ">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="faq"></a>Chapter 12. FAQ</h2></div></div></div>
15<div class="qandaset" title="Frequently Asked Questions">
16<a name="idm1966160"></a><dl>
17<dt>12.1. <a href="faq.html#idm1965696">
18 How does Poky differ from OpenEmbedded?
19 </a>
20</dt>
21<dt>12.2. <a href="faq.html#idm1961792">
22 I only have Python 2.4 or 2.5 but BitBake requires Python 2.6 or 2.7.
23 Can I still use the Yocto Project?
24 </a>
25</dt>
26<dt>12.3. <a href="faq.html#idm2605168">
27 How can you claim Poky / OpenEmbedded-Core is stable?
28 </a>
29</dt>
30<dt>12.4. <a href="faq.html#idm3232752">
31 How do I get support for my board added to the Yocto Project?
32 </a>
33</dt>
34<dt>12.5. <a href="faq.html#idm3230416">
35 Are there any products built using the OpenEmbedded build system?
36 </a>
37</dt>
38<dt>12.6. <a href="faq.html#idm3227696">
39 What does the OpenEmbedded build system produce as output?
40 </a>
41</dt>
42<dt>12.7. <a href="faq.html#idm5359408">
43 How do I add my package to the Yocto Project?
44 </a>
45</dt>
46<dt>12.8. <a href="faq.html#idm5357680">
47 Do I have to reflash my entire board with a new Yocto Project image when recompiling
48 a package?
49 </a>
50</dt>
51<dt>12.9. <a href="faq.html#idm5354224">
52 What is GNOME Mobile and what is the difference between GNOME Mobile and GNOME?
53 </a>
54</dt>
55<dt>12.10. <a href="faq.html#idm2088960">
56 I see the error 'chmod: XXXXX new permissions are r-xrwxrwx, not r-xr-xr-x'.
57 What is wrong?
58 </a>
59</dt>
60<dt>12.11. <a href="faq.html#idm2085168">
61 How do I make the Yocto Project work in RHEL/CentOS?
62 </a>
63</dt>
64<dt>12.12. <a href="faq.html#idm3829808">
65 I see lots of 404 responses for files on
66 http://www.yoctoproject.org/sources/*. Is something wrong?
67 </a>
68</dt>
69<dt>12.13. <a href="faq.html#idm3827408">
70 I have machine-specific data in a package for one machine only but the package is
71 being marked as machine-specific in all cases, how do I prevent this?
72 </a>
73</dt>
74<dt>12.14. <a href="faq.html#idm5331776">
75 I'm behind a firewall and need to use a proxy server. How do I do that?
76 </a>
77</dt>
78<dt>12.15. <a href="faq.html#idm1524432">
79 What&#8217;s the difference between foo and foo-native?
80 </a>
81</dt>
82<dt>12.16. <a href="faq.html#idm1520336">
83 I'm seeing random build failures. Help?!
84 </a>
85</dt>
86<dt>12.17. <a href="faq.html#idm4636672">
87 What do we need to ship for license compliance?
88 </a>
89</dt>
90<dt>12.18. <a href="faq.html#idm4635216">
91 How do I disable the cursor on my touchscreen device?
92 </a>
93</dt>
94<dt>12.19. <a href="faq.html#idm4631744">
95 How do I make sure connected network interfaces are brought up by default?
96 </a>
97</dt>
98<dt>12.20. <a href="faq.html#idm3888832">
99 How do I create images with more free space?
100 </a>
101</dt>
102<dt>12.21. <a href="faq.html#idm619504">
103 Why don't you support directories with spaces in the pathnames?
104 </a>
105</dt>
106<dt>12.22. <a href="faq.html#idm617456">
107 How do I use an external toolchain?
108 </a>
109</dt>
110<dt>12.23. <a href="faq.html#idm4577168">
111 How does the OpenEmbedded build system obtain source code and will it work behind my
112 firewall or proxy server?
113 </a>
114</dt>
115<dt>12.24. <a href="faq.html#idm3953616">
116 Can I get rid of build output so I can start over?
117 </a>
118</dt>
119</dl>
120<table border="0" width="100%" summary="Q and A Set">
121<col align="left" width="1%">
122<col>
123<tbody>
124<tr class="question" title="12.1.">
125<td align="left" valign="top">
126<a name="idm1965696"></a><a name="idm1965568"></a><p><b>12.1.</b></p>
127</td>
128<td align="left" valign="top"><p>
129 How does Poky differ from <a class="ulink" href="http://www.openembedded.org" target="_self">OpenEmbedded</a>?
130 </p></td>
131</tr>
132<tr class="answer">
133<td align="left" valign="top"></td>
134<td align="left" valign="top"><p>
135 The term "Poky" refers to the specific reference build system that
136 the Yocto Project provides.
137 Poky is based on <a class="link" href="../dev-manual/oe-core.html" target="_self">OE-Core</a>
138 and BitBake.
139 Thus, the generic term used here for the build system is
140 the "OpenEmbedded build system."
141 Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with
142 changes always being merged to OE-Core or BitBake first before being pulled back
143 into Poky.
144 This practice benefits both projects immediately.
145 For a fuller description of the term "Poky", see the
146 <a class="link" href="../dev-manual/poky.html" target="_self">poky</a> term in the Yocto Project
147 Development Manual.
148 </p></td>
149</tr>
150<tr class="question" title="12.2.">
151<td align="left" valign="top">
152<a name="idm1961792"></a><a name="idm1961664"></a><p><b>12.2.</b></p>
153</td>
154<td align="left" valign="top"><p>
155 I only have Python 2.4 or 2.5 but BitBake requires Python 2.6 or 2.7.
156 Can I still use the Yocto Project?
157 </p></td>
158</tr>
159<tr class="answer">
160<td align="left" valign="top"></td>
161<td align="left" valign="top">
162<p>
163 You can use a stand-alone tarball to provide Python 2.6.
164 You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations:
165 </p>
166<div class="itemizedlist"><ul class="itemizedlist" type="disc">
167<li class="listitem"><p><a class="ulink" href="http://downloads.yoctoproject.org/releases/miscsupport/python-nativesdk-standalone-i686.tar.bz2" target="_self">32-bit tarball</a></p></li>
168<li class="listitem"><p><a class="ulink" href="http://downloads.yoctoproject.org/releases/miscsupport/python-nativesdk-standalone-x86_64.tar.bz2" target="_self">64-bit tarball</a></p></li>
169</ul></div>
170<p>
171 </p>
172<p>
173 These tarballs are self-contained with all required libraries and should work
174 on most Linux systems.
175 To use the tarballs extract them into the root
176 directory and run the appropriate command:
177 </p>
178<pre class="literallayout">
179 $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH
180 $ export PATH=/opt/poky/sysroots/x86_64-pokysdk-linux/usr/bin/:$PATH
181 </pre>
182<p>
183 </p>
184<p>
185 Once you run the command, BitBake uses Python 2.6.
186 </p>
187</td>
188</tr>
189<tr class="question" title="12.3.">
190<td align="left" valign="top">
191<a name="idm2605168"></a><a name="idm2605040"></a><p><b>12.3.</b></p>
192</td>
193<td align="left" valign="top"><p>
194 How can you claim Poky / OpenEmbedded-Core is stable?
195 </p></td>
196</tr>
197<tr class="answer">
198<td align="left" valign="top"></td>
199<td align="left" valign="top">
200<p>
201 There are three areas that help with stability;
202 </p>
203<div class="itemizedlist"><ul class="itemizedlist" type="disc">
204<li class="listitem"><p>The Yocto Project team keeps
205 <a class="link" href="../dev-manual/oe-core.html" target="_self">OE-Core</a> small
206 and focused, containing around 830 recipes as opposed to the thousands
207 available in other OpenEmbedded community layers.
208 Keeping it small makes it easy to test and maintain.</p></li>
209<li class="listitem"><p>The Yocto Project team runs manual and automated tests
210 using a small, fixed set of reference hardware as well as emulated
211 targets.</p></li>
212<li class="listitem"><p>The Yocto Project uses an an autobuilder,
213 which provides continuous build and integration tests.</p></li>
214</ul></div>
215<p>
216 </p>
217</td>
218</tr>
219<tr class="question" title="12.4.">
220<td align="left" valign="top">
221<a name="idm3232752"></a><a name="idm3232624"></a><p><b>12.4.</b></p>
222</td>
223<td align="left" valign="top"><p>
224 How do I get support for my board added to the Yocto Project?
225 </p></td>
226</tr>
227<tr class="answer">
228<td align="left" valign="top"></td>
229<td align="left" valign="top">
230<p>
231 Support for an additional board is added by creating a BSP layer for it.
232 For more information on how to create a BSP layer, see the
233 <a class="link" href="../bsp-guide/index.html" target="_self">Yocto Project Board Support Package (BSP) Developer's Guide</a>.
234 </p>
235<p>
236 Usually, if the board is not completely exotic, adding support in
237 the Yocto Project is fairly straightforward.
238 </p>
239</td>
240</tr>
241<tr class="question" title="12.5.">
242<td align="left" valign="top">
243<a name="idm3230416"></a><a name="idm3230288"></a><p><b>12.5.</b></p>
244</td>
245<td align="left" valign="top"><p>
246 Are there any products built using the OpenEmbedded build system?
247 </p></td>
248</tr>
249<tr class="answer">
250<td align="left" valign="top"></td>
251<td align="left" valign="top"><p>
252 The software running on the <a class="ulink" href="http://vernier.com/labquest/" target="_self">Vernier LabQuest</a>
253 is built using the OpenEmbedded build system.
254 See the <a class="ulink" href="http://www.vernier.com/products/interfaces/labq/" target="_self">Vernier LabQuest</a>
255 website for more information.
256 There are a number of pre-production devices using the OpenEmbedded build system
257 and the Yocto Project team
258 announces them as soon as they are released.
259 </p></td>
260</tr>
261<tr class="question" title="12.6.">
262<td align="left" valign="top">
263<a name="idm3227696"></a><a name="idm3227568"></a><p><b>12.6.</b></p>
264</td>
265<td align="left" valign="top"><p>
266 What does the OpenEmbedded build system produce as output?
267 </p></td>
268</tr>
269<tr class="answer">
270<td align="left" valign="top"></td>
271<td align="left" valign="top"><p>
272 Because the same set of recipes can be used to create output of various formats, the
273 output of an OpenEmbedded build depends on how it was started.
274 Usually, the output is a flashable image ready for the target device.
275 </p></td>
276</tr>
277<tr class="question" title="12.7.">
278<td align="left" valign="top">
279<a name="idm5359408"></a><a name="idm5359280"></a><p><b>12.7.</b></p>
280</td>
281<td align="left" valign="top"><p>
282 How do I add my package to the Yocto Project?
283 </p></td>
284</tr>
285<tr class="answer">
286<td align="left" valign="top"></td>
287<td align="left" valign="top"><p>
288 To add a package, you need to create a BitBake recipe.
289 For information on how to add a package, see the section
290 "<a class="link" href="../dev-manual/usingpoky-extend-addpkg.html" target="_self">Adding a Package</a>"
291 in the Yocto Project Development Manual.
292 </p></td>
293</tr>
294<tr class="question" title="12.8.">
295<td align="left" valign="top">
296<a name="idm5357680"></a><a name="idm5357552"></a><p><b>12.8.</b></p>
297</td>
298<td align="left" valign="top"><p>
299 Do I have to reflash my entire board with a new Yocto Project image when recompiling
300 a package?
301 </p></td>
302</tr>
303<tr class="answer">
304<td align="left" valign="top"></td>
305<td align="left" valign="top"><p>
306 The OpenEmbedded build system can build packages in various formats such as
307 <code class="filename">ipk</code> for <code class="filename">opkg</code>,
308 Debian package (<code class="filename">.deb</code>), or RPM.
309 The packages can then be upgraded using the package tools on the device, much like
310 on a desktop distribution such as Ubuntu or Fedora.
311 </p></td>
312</tr>
313<tr class="question" title="12.9.">
314<td align="left" valign="top">
315<a name="idm5354224"></a><a name="idm5354096"></a><p><b>12.9.</b></p>
316</td>
317<td align="left" valign="top"><p>
318 What is GNOME Mobile and what is the difference between GNOME Mobile and GNOME?
319 </p></td>
320</tr>
321<tr class="answer">
322<td align="left" valign="top"></td>
323<td align="left" valign="top"><p>
324 GNOME Mobile is a subset of the <a class="ulink" href="http://www.gnome.org" target="_self">GNOME</a>
325 platform targeted at mobile and embedded devices.
326 The the main difference between GNOME Mobile and standard GNOME is that
327 desktop-orientated libraries have been removed, along with deprecated libraries,
328 creating a much smaller footprint.
329 </p></td>
330</tr>
331<tr class="question" title="12.10.">
332<td align="left" valign="top">
333<a name="idm2088960"></a><a name="idm2088832"></a><p><b>12.10.</b></p>
334</td>
335<td align="left" valign="top"><p>
336 I see the error '<code class="filename">chmod: XXXXX new permissions are r-xrwxrwx, not r-xr-xr-x</code>'.
337 What is wrong?
338 </p></td>
339</tr>
340<tr class="answer">
341<td align="left" valign="top"></td>
342<td align="left" valign="top"><p>
343 You are probably running the build on an NTFS filesystem.
344 Use <code class="filename">ext2</code>, <code class="filename">ext3</code>, or <code class="filename">ext4</code> instead.
345 </p></td>
346</tr>
347<tr class="question" title="12.11.">
348<td align="left" valign="top">
349<a name="idm2085168"></a><a name="idm2085040"></a><p><b>12.11.</b></p>
350</td>
351<td align="left" valign="top"><p>
352 How do I make the Yocto Project work in RHEL/CentOS?
353 </p></td>
354</tr>
355<tr class="answer">
356<td align="left" valign="top"></td>
357<td align="left" valign="top">
358<p>
359 To get the Yocto Project working under RHEL/CentOS 5.1 you need to first
360 install some required packages.
361 The standard CentOS packages needed are:
362 </p>
363<div class="itemizedlist"><ul class="itemizedlist" type="disc">
364<li class="listitem"><p>"Development tools" (selected during installation)</p></li>
365<li class="listitem"><p><code class="filename">texi2html</code></p></li>
366<li class="listitem"><p><code class="filename">compat-gcc-34</code></p></li>
367</ul></div>
368<p>
369 On top of these, you need the following external packages:
370 </p>
371<div class="itemizedlist"><ul class="itemizedlist" type="disc">
372<li class="listitem"><p><code class="filename">python-sqlite2</code> from
373 <a class="ulink" href="http://dag.wieers.com/rpm/packages/python-sqlite2/" target="_self">DAG repository</a>
374 </p></li>
375<li class="listitem"><p><code class="filename">help2man</code> from
376 <a class="ulink" href="http://centos.karan.org/el4/extras/stable/x86_64/RPMS/repodata/repoview/help2man-0-1.33.1-2.html" target="_self">Karan repository</a></p></li>
377</ul></div>
378<p>
379 </p>
380<p>
381 Once these packages are installed, the OpenEmbedded build system will be able
382 to build standard images.
383 However, there might be a problem with the QEMU emulator segfaulting.
384 You can either disable the generation of binary locales by setting
385 <code class="filename"><a class="link" href="ref-variables-glos.html#var-ENABLE_BINARY_LOCALE_GENERATION" title="ENABLE_BINARY_LOCALE_GENERATION">ENABLE_BINARY_LOCALE_GENERATION</a>
386 </code> to "0" or by removing the <code class="filename">linux-2.6-execshield.patch</code>
387 from the kernel and rebuilding it since that is the patch that causes the problems with QEMU.
388 </p>
389</td>
390</tr>
391<tr class="question" title="12.12.">
392<td align="left" valign="top">
393<a name="idm3829808"></a><a name="idm3829680"></a><p><b>12.12.</b></p>
394</td>
395<td align="left" valign="top"><p>
396 I see lots of 404 responses for files on
397 <code class="filename">http://www.yoctoproject.org/sources/*</code>. Is something wrong?
398 </p></td>
399</tr>
400<tr class="answer">
401<td align="left" valign="top"></td>
402<td align="left" valign="top"><p>
403 Nothing is wrong.
404 The OpenEmbedded build system checks any configured source mirrors before downloading
405 from the upstream sources.
406 The build system does this searching for both source archives and
407 pre-checked out versions of SCM managed software.
408 These checks help in large installations because it can reduce load on the SCM servers
409 themselves.
410 The address above is one of the default mirrors configured into the
411 build system.
412 Consequently, if an upstream source disappears, the team
413 can place sources there so builds continue to work.
414 </p></td>
415</tr>
416<tr class="question" title="12.13.">
417<td align="left" valign="top">
418<a name="idm3827408"></a><a name="idm3827280"></a><p><b>12.13.</b></p>
419</td>
420<td align="left" valign="top"><p>
421 I have machine-specific data in a package for one machine only but the package is
422 being marked as machine-specific in all cases, how do I prevent this?
423 </p></td>
424</tr>
425<tr class="answer">
426<td align="left" valign="top"></td>
427<td align="left" valign="top"><p>
428 Set <code class="filename"><a class="link" href="ref-variables-glos.html#var-SRC_URI_OVERRIDES_PACKAGE_ARCH" title="SRC_URI_OVERRIDES_PACKAGE_ARCH">SRC_URI_OVERRIDES_PACKAGE_ARCH</a>
429 </code> = "0" in the <code class="filename">.bb</code> file but make sure the package is
430 manually marked as
431 machine-specific in the case that needs it.
432 The code that handles <code class="filename">SRC_URI_OVERRIDES_PACKAGE_ARCH</code> is in <code class="filename">base.bbclass</code>.
433 </p></td>
434</tr>
435<tr class="question" title="12.14.">
436<td align="left" valign="top">
437<a name="idm5331776"></a><a name="idm5331648"></a><p><b>12.14.</b></p>
438</td>
439<td align="left" valign="top"><p>
440 I'm behind a firewall and need to use a proxy server. How do I do that?
441 </p></td>
442</tr>
443<tr class="answer">
444<td align="left" valign="top"></td>
445<td align="left" valign="top">
446<p>
447 Most source fetching by the OpenEmbedded build system is done by <code class="filename">wget</code>
448 and you therefore need to specify the proxy settings in a
449 <code class="filename">.wgetrc</code> file in your home directory.
450 Example settings in that file would be
451 </p>
452<pre class="literallayout">
453 http_proxy = http://proxy.yoyodyne.com:18023/
454 ftp_proxy = http://proxy.yoyodyne.com:18023/
455 </pre>
456<p>
457 The Yocto Project also includes a <code class="filename">site.conf.sample</code>
458 file that shows how to configure CVS and Git proxy servers
459 if needed.
460 </p>
461</td>
462</tr>
463<tr class="question" title="12.15.">
464<td align="left" valign="top">
465<a name="idm1524432"></a><a name="idm1524304"></a><p><b>12.15.</b></p>
466</td>
467<td align="left" valign="top"><p>
468 What&#8217;s the difference between <code class="filename">foo</code> and <code class="filename">foo-native</code>?
469 </p></td>
470</tr>
471<tr class="answer">
472<td align="left" valign="top"></td>
473<td align="left" valign="top"><p>
474 The <code class="filename">*-native</code> targets are designed to run on the system
475 being used for the build.
476 These are usually tools that are needed to assist the build in some way such as
477 <code class="filename">quilt-native</code>, which is used to apply patches.
478 The non-native version is the one that runs on the target device.
479 </p></td>
480</tr>
481<tr class="question" title="12.16.">
482<td align="left" valign="top">
483<a name="idm1520336"></a><a name="idm1520208"></a><p><b>12.16.</b></p>
484</td>
485<td align="left" valign="top"><p>
486 I'm seeing random build failures. Help?!
487 </p></td>
488</tr>
489<tr class="answer">
490<td align="left" valign="top"></td>
491<td align="left" valign="top"><p>
492 If the same build is failing in totally different and random ways,
493 the most likely explanation is that either the hardware you're running the
494 build on has some problem, or, if you are running the build under virtualisation,
495 the virtualisation probably has bugs.
496 The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and
497 CPU activity and is sensitive to even single bit failures in any of these areas.
498 True random failures have always been traced back to hardware or virtualisation issues.
499 </p></td>
500</tr>
501<tr class="question" title="12.17.">
502<td align="left" valign="top">
503<a name="idm4636672"></a><a name="idm4636544"></a><p><b>12.17.</b></p>
504</td>
505<td align="left" valign="top"><p>
506 What do we need to ship for license compliance?
507 </p></td>
508</tr>
509<tr class="answer">
510<td align="left" valign="top"></td>
511<td align="left" valign="top"><p>
512 This is a difficult question and you need to consult your lawyer for the answer
513 for your specific case.
514 It is worth bearing in mind that for GPL compliance there needs to be enough
515 information shipped to allow someone else to rebuild the same end result
516 you are shipping.
517 This means sharing the source code, any patches applied to it, and also any
518 configuration information about how that package was configured and built.
519 </p></td>
520</tr>
521<tr class="question" title="12.18.">
522<td align="left" valign="top">
523<a name="idm4635216"></a><a name="idm4635088"></a><p><b>12.18.</b></p>
524</td>
525<td align="left" valign="top"><p>
526 How do I disable the cursor on my touchscreen device?
527 </p></td>
528</tr>
529<tr class="answer">
530<td align="left" valign="top"></td>
531<td align="left" valign="top">
532<p>
533 You need to create a form factor file as described in the
534 "<a class="link" href="../bsp-guide/bsp-filelayout-misc-recipes.html" target="_self">Miscellaneous Recipe Files</a>"
535 section and set the <code class="filename">HAVE_TOUCHSCREEN</code> variable equal to one as follows:
536 </p>
537<pre class="literallayout">
538 HAVE_TOUCHSCREEN=1
539 </pre>
540<p>
541 </p>
542</td>
543</tr>
544<tr class="question" title="12.19.">
545<td align="left" valign="top">
546<a name="idm4631744"></a><a name="idm4631616"></a><p><b>12.19.</b></p>
547</td>
548<td align="left" valign="top"><p>
549 How do I make sure connected network interfaces are brought up by default?
550 </p></td>
551</tr>
552<tr class="answer">
553<td align="left" valign="top"></td>
554<td align="left" valign="top">
555<p>
556 The default interfaces file provided by the netbase recipe does not
557 automatically bring up network interfaces.
558 Therefore, you will need to add a BSP-specific netbase that includes an interfaces
559 file.
560 See the "<a class="link" href="../bsp-guide/bsp-filelayout-misc-recipes.html" target="_self">Miscellaneous Recipe Files</a>"
561 section for information on creating these types of miscellaneous recipe files.
562 </p>
563<p>
564 For example, add the following files to your layer:
565 </p>
566<pre class="literallayout">
567 meta-MACHINE/recipes-bsp/netbase/netbase/MACHINE/interfaces
568 meta-MACHINE/recipes-bsp/netbase/netbase_5.0.bbappend
569 </pre>
570<p>
571 </p>
572</td>
573</tr>
574<tr class="question" title="12.20.">
575<td align="left" valign="top">
576<a name="idm3888832"></a><a name="idm3888704"></a><p><b>12.20.</b></p>
577</td>
578<td align="left" valign="top"><p>
579 How do I create images with more free space?
580 </p></td>
581</tr>
582<tr class="answer">
583<td align="left" valign="top"></td>
584<td align="left" valign="top">
585<p>
586 Images are created to be 1.2 times the size of the populated root filesystem.
587 To modify this ratio so that there is more free space available, you need to
588 set the configuration value <code class="filename">IMAGE_OVERHEAD_FACTOR</code>.
589 For example, setting <code class="filename">IMAGE_OVERHEAD_FACTOR</code> to 1.5 sets
590 the image size ratio to one and a half times the size of the populated
591 root filesystem.
592 </p>
593<pre class="literallayout">
594 IMAGE_OVERHEAD_FACTOR = "1.5"
595 </pre>
596<p>
597 </p>
598</td>
599</tr>
600<tr class="question" title="12.21.">
601<td align="left" valign="top">
602<a name="idm619504"></a><a name="idm619376"></a><p><b>12.21.</b></p>
603</td>
604<td align="left" valign="top"><p>
605 Why don't you support directories with spaces in the pathnames?
606 </p></td>
607</tr>
608<tr class="answer">
609<td align="left" valign="top"></td>
610<td align="left" valign="top"><p>
611 The Yocto Project team has tried to do this before but too many of the tools
612 the OpenEmbedded build system depends on such as <code class="filename">autoconf</code>
613 break when they find spaces in pathnames.
614 Until that situation changes, the team will not support spaces in pathnames.
615 </p></td>
616</tr>
617<tr class="question" title="12.22.">
618<td align="left" valign="top">
619<a name="idm617456"></a><a name="idm617328"></a><p><b>12.22.</b></p>
620</td>
621<td align="left" valign="top"><p>
622 How do I use an external toolchain?
623 </p></td>
624</tr>
625<tr class="answer">
626<td align="left" valign="top"></td>
627<td align="left" valign="top">
628<p>
629 The toolchain configuration is very flexible and customizable.
630 It is primarily controlled with the
631 <code class="filename"><a class="link" href="ref-variables-glos.html#var-TCMODE" title="TCMODE">TCMODE</a></code> variable.
632 This variable controls which <code class="filename">tcmode-*.inc</code> file to include
633 from the <code class="filename">meta/conf/distro/include</code> directory within the
634 <a class="link" href="../dev-manual/source-directory.html" target="_self">source directory</a>.
635 </p>
636<p>
637 The default value of <code class="filename">TCMODE</code> is "default"
638 (i.e. <code class="filename">tcmode-default.inc</code>).
639 However, other patterns are accepted.
640 In particular, "external-*" refers to external toolchains of which there are some
641 basic examples included in the OpenEmbedded Core (<code class="filename">meta</code>).
642 You can use your own custom toolchain definition in your own layer
643 (or as defined in the <code class="filename">local.conf</code> file) at the location
644 <code class="filename">conf/distro/include/tcmode-*.inc</code>.
645 </p>
646<p>
647 In addition to the toolchain configuration, you also need a corresponding toolchain recipe file.
648 This recipe file needs to package up any pre-built objects in the toolchain such as
649 <code class="filename">libgcc</code>, <code class="filename">libstdcc++</code>,
650 any locales, and <code class="filename">libc</code>.
651 An example is the <code class="filename">external-sourcery-toolchain.bb</code>, which is located
652 in <code class="filename">meta/recipes-core/meta/</code> within the source directory.
653 </p>
654</td>
655</tr>
656<tr class="question" title="12.23.">
657<td align="left" valign="top">
658<a name="idm4577168"></a><a name="idm5139136"></a><p><b>12.23.</b></p>
659</td>
660<td align="left" valign="top"><p><a name="how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server"></a>
661 How does the OpenEmbedded build system obtain source code and will it work behind my
662 firewall or proxy server?
663 </p></td>
664</tr>
665<tr class="answer">
666<td align="left" valign="top"></td>
667<td align="left" valign="top">
668<p>
669 The way the build system obtains source code is highly configurable.
670 You can setup the build system to get source code in most environments if
671 HTTP transport is available.
672 </p>
673<p>
674 When the build system searches for source code, it first tries the local download directory.
675 If that location fails, Poky tries PREMIRRORS, the upstream source,
676 and then MIRRORS in that order.
677 </p>
678<p>
679 By default, the OpenEmbedded build system uses the Yocto Project source PREMIRRORS
680 for SCM-based sources,
681 upstreams for normal tarballs, and then falls back to a number of other mirrors
682 including the Yocto Project source mirror if those fail.
683 </p>
684<p>
685 As an example, you could add a specific server for Poky to attempt before any
686 others by adding something like the following to the <code class="filename">local.conf</code>
687 configuration file:
688 </p>
689<pre class="literallayout">
690 PREMIRRORS_prepend = "\
691 git://.*/.* http://www.yoctoproject.org/sources/ \n \
692 ftp://.*/.* http://www.yoctoproject.org/sources/ \n \
693 http://.*/.* http://www.yoctoproject.org/sources/ \n \
694 https://.*/.* http://www.yoctoproject.org/sources/ \n"
695 </pre>
696<p>
697 </p>
698<p>
699 These changes cause Poky to intercept Git, FTP, HTTP, and HTTPS
700 requests and direct them to the <code class="filename">http://</code> sources mirror.
701 You can use <code class="filename">file://</code> URLs to point to local directories
702 or network shares as well.
703 </p>
704<p>
705 Aside from the previous technique, these options also exist:
706 </p>
707<pre class="literallayout">
708 BB_NO_NETWORK = "1"
709 </pre>
710<p>
711 This statement tells BitBake to throw an error instead of trying to access the
712 Internet.
713 This technique is useful if you want to ensure code builds only from local sources.
714 </p>
715<p>
716 Here is another technique:
717 </p>
718<pre class="literallayout">
719 BB_FETCH_PREMIRRORONLY = "1"
720 </pre>
721<p>
722 This statement limits Poky to pulling source from the PREMIRRORS only.
723 Again, this technique is useful for reproducing builds.
724 </p>
725<p>
726 Here is another technique:
727 </p>
728<pre class="literallayout">
729 BB_GENERATE_MIRROR_TARBALLS = "1"
730 </pre>
731<p>
732 This statement tells Poky to generate mirror tarballs.
733 This technique is useful if you want to create a mirror server.
734 If not, however, the technique can simply waste time during the build.
735 </p>
736<p>
737 Finally, consider an example where you are behind an HTTP-only firewall.
738 You could make the following changes to the <code class="filename">local.conf</code>
739 configuration file as long as the PREMIRROR server is up to date:
740 </p>
741<pre class="literallayout">
742 PREMIRRORS_prepend = "\
743 ftp://.*/.* http://www.yoctoproject.org/sources/ \n \
744 http://.*/.* http://www.yoctoproject.org/sources/ \n \
745 https://.*/.* http://www.yoctoproject.org/sources/ \n"
746 BB_FETCH_PREMIRRORONLY = "1"
747 </pre>
748<p>
749 These changes would cause Poky to successfully fetch source over HTTP and
750 any network accesses to anything other than the PREMIRROR would fail.
751 </p>
752<p>
753 The build system also honors the standard shell environment variables
754 <code class="filename">http_proxy</code>, <code class="filename">ftp_proxy</code>,
755 <code class="filename">https_proxy</code>, and <code class="filename">all_proxy</code>
756 to redirect requests through proxy servers.
757 </p>
758</td>
759</tr>
760<tr class="question" title="12.24.">
761<td align="left" valign="top">
762<a name="idm3953616"></a><a name="idm3685632"></a><p><b>12.24.</b></p>
763</td>
764<td align="left" valign="top"><p>
765 Can I get rid of build output so I can start over?
766 </p></td>
767</tr>
768<tr class="answer">
769<td align="left" valign="top"></td>
770<td align="left" valign="top">
771<p>
772 Yes - you can easily do this.
773 When you use BitBake to build an image, all the build output goes into the
774 directory created when you source the <code class="filename">oe-init-build-env</code>
775 setup file.
776 By default, this <a class="link" href="../dev-manual/build-directory.html" target="_self">build directory</a>
777 is named <code class="filename">build</code> but can be named
778 anything you want.
779 </p>
780<p>
781 Within the build directory is the <code class="filename">tmp</code> directory.
782 To remove all the build output yet preserve any source code or downloaded files
783 from previous builds, simply remove the <code class="filename">tmp</code> directory.
784 </p>
785</td>
786</tr>
787</tbody>
788</table>
789</div>
790</div></body>
791</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/fedora-packages.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/fedora-packages.html
deleted file mode 100644
index d1dc7d1f33..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/fedora-packages.html
+++ /dev/null
@@ -1,62 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3.2.2. Fedora Packages</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="required-packages-for-the-host-development-system.html" title="1.3.2. Required Packages for the Host Development System">
9<link rel="prev" href="ubuntu-packages.html" title="1.3.2.1. Ubuntu">
10<link rel="next" href="opensuse-packages.html" title="1.3.2.3. OpenSUSE Packages">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.2.2. Fedora Packages">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="fedora-packages"></a>1.3.2.2. Fedora Packages</h4></div></div></div>
15<p>
16 The following list shows the required packages by function
17 given a supported Fedora Linux distribution:
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem">
21<p><span class="emphasis"><em>Essentials:</em></span>
22 Packages needed to build an image for a headless
23 system:
24 </p>
25<pre class="literallayout">
26 $ sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
27 diffutils diffstat git cpp gcc gcc-c++ eglibc-devel texinfo chrpath \
28 ccache
29 </pre>
30</li>
31<li class="listitem">
32<p><span class="emphasis"><em>Graphical Extras:</em></span>
33 Packages recommended if the host system has graphics support:
34 </p>
35<pre class="literallayout">
36 $ sudo yum install SDL-devel xterm
37 </pre>
38</li>
39<li class="listitem">
40<p><span class="emphasis"><em>Documentation:</em></span>
41 Packages needed if you are going to build out the
42 Yocto Project documentation manuals:
43 </p>
44<pre class="literallayout">
45 $ sudo yum install make docbook-style-dsssl docbook-style-xsl \
46 docbook-dtds docbook-utils fop libxslt
47 </pre>
48</li>
49<li class="listitem">
50<p><span class="emphasis"><em>ADT Installer Extras:</em></span>
51 Packages needed if you are going to be using the
52 <a class="link" href="../adt-manual/using-the-adt-installer.html" target="_self">Application Development Toolkit (ADT) Installer</a>:
53 </p>
54<pre class="literallayout">
55 $ sudo yum install autoconf automake libtool glib2-devel
56 </pre>
57</li>
58</ul></div>
59<p>
60 </p>
61</div></body>
62</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/future-development-and-limitations.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/future-development-and-limitations.html
deleted file mode 100644
index cd09ff8193..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/future-development-and-limitations.html
+++ /dev/null
@@ -1,33 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.3.2. Future Development and Limitations</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="x32.html" title="3.3. x32">
9<link rel="prev" href="support.html" title="3.3.1. Support">
10<link rel="next" href="using-x32-right-now.html" title="3.3.3. Using x32 Right Now">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.3.2. Future Development and Limitations">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="future-development-and-limitations"></a>3.3.2. Future Development and Limitations</h3></div></div></div>
15<p>
16 As of this Yocto Project release, the x32 psABI kernel and library interfaces
17 specifications are not finalized.
18 </p>
19<p>
20 Future Plans for the x32 psABI in the Yocto Project include the following:
21 </p>
22<div class="itemizedlist"><ul class="itemizedlist" type="disc">
23<li class="listitem"><p>Enhance and fix the few remaining recipes so they
24 work with and support x32 toolchains.</p></li>
25<li class="listitem"><p>Enhance RPM Package Manager (RPM) support for x32 binaries.</p></li>
26<li class="listitem"><p>Support larger images.</p></li>
27<li class="listitem"><p>Integrate x32 recipes, toolchain, and kernel changes from
28 <code class="filename">experimental/meta-x32</code> into OE-core.</p></li>
29</ul></div>
30<p>
31 </p>
32</div></body>
33</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/handbook.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/handbook.html
deleted file mode 100644
index 9588191dbe..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/handbook.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.3. documentation</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-build.html" title="5.1.2. build/">
10<link rel="next" href="structure-core-meta.html" title="5.1.4. meta/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.3. documentation">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="handbook"></a>5.1.3. <code class="filename">documentation</code>
15</h3></div></div></div>
16<p>
17 This directory holds the source for the Yocto Project documentation
18 as well as templates and tools that allow you to generate PDF and HTML
19 versions of the manuals.
20 Each manual is contained in a sub-folder.
21 For example, the files for this manual reside in
22 <code class="filename">poky-ref-manual</code>.
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/index.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/index.html
deleted file mode 100644
index 70ef00544c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/index.html
+++ /dev/null
@@ -1,327 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>The Yocto Project Reference Manual</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="next" href="intro.html" title="Chapter 1. Introduction">
9</head>
10<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div lang="en" class="book" title="The Yocto Project Reference Manual">
11<div class="titlepage">
12<div>
13<div><h1 class="title">
14<a name="poky-ref-manual"></a>
15 The Yocto Project Reference Manual
16 </h1></div>
17<div><div class="authorgroup">
18 <div class="author">
19<h3 class="author">
20<span class="firstname">Richard</span> <span class="surname">Purdie</span>
21</h3>
22<div class="affiliation">
23 <span class="orgname">Linux Foundation<br></span>
24 </div>
25<code class="email">&lt;<a class="email" href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>&gt;</code>
26</div>
27
28 </div></div>
29<div><p class="copyright">Copyright © 2010-2013 Linux Foundation</p></div>
30<div><div class="legalnotice" title="Legal Notice">
31<a name="idm3374608"></a>
32 <p>
33 Permission is granted to copy, distribute and/or modify this document under
34 the terms of the <a class="ulink" href="http://creativecommons.org/licenses/by-sa/2.0/uk/" target="_self">Creative Commons Attribution-Share Alike 2.0 UK: England &amp; Wales</a> as published by Creative Commons.
35 </p>
36 <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
37<h3 class="title">Note</h3>
38 Due to production processes, there could be differences between the Yocto Project
39 documentation bundled in the release tarball and the
40 <a class="link" href="../poky-ref-manual/index.html" target="_self">Yocto Project Reference Manual</a> on
41 the <a class="ulink" href="http://www.yoctoproject.org" target="_self">Yocto Project</a> website.
42 For the latest version of this manual, see the manual on the website.
43 </div>
44 </div></div>
45<div><div class="revhistory"><table border="1" width="100%" summary="Revision history">
46<tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr>
47 <tr>
48<td align="left">Revision 4.0+git</td>
49<td align="left">24 November 2010</td>
50</tr>
51<tr><td align="left" colspan="2">Released with the Yocto Project 0.9 Release</td></tr>
52 <tr>
53<td align="left">Revision 1.0</td>
54<td align="left">6 April 2011</td>
55</tr>
56<tr><td align="left" colspan="2">Released with the Yocto Project 1.0 Release.</td></tr>
57 <tr>
58<td align="left">Revision 1.0.1</td>
59<td align="left">23 May 2011</td>
60</tr>
61<tr><td align="left" colspan="2">Released with the Yocto Project 1.0.1 Release.</td></tr>
62 <tr>
63<td align="left">Revision 1.1</td>
64<td align="left">6 October 2011</td>
65</tr>
66<tr><td align="left" colspan="2">Released with the Yocto Project 1.1 Release.</td></tr>
67 <tr>
68<td align="left">Revision 1.2</td>
69<td align="left">April 2012</td>
70</tr>
71<tr><td align="left" colspan="2">Released with the Yocto Project 1.2 Release.</td></tr>
72 <tr>
73<td align="left">Revision 1.3</td>
74<td align="left">October 2012</td>
75</tr>
76<tr><td align="left" colspan="2">Released with the Yocto Project 1.3 Release.</td></tr>
77 <tr>
78<td align="left">Revision 1.4</td>
79<td align="left">Sometime in 2013</td>
80</tr>
81<tr><td align="left" colspan="2">Released with the Yocto Project 1.4 Release.</td></tr>
82 </table></div></div>
83</div>
84<hr>
85</div>
86<div class="toc">
87<p><b>Table of Contents</b></p>
88<dl>
89<dt><span class="chapter"><a href="intro.html">1. Introduction</a></span></dt>
90<dd><dl>
91<dt><span class="section"><a href="intro-welcome.html">1.1. Introduction</a></span></dt>
92<dt><span class="section"><a href="intro-manualoverview.html">1.2. Documentation Overview</a></span></dt>
93<dt><span class="section"><a href="intro-requirements.html">1.3. System Requirements</a></span></dt>
94<dd><dl>
95<dt><span class="section"><a href="detailed-supported-distros.html">1.3.1. Supported Linux Distributions</a></span></dt>
96<dt><span class="section"><a href="required-packages-for-the-host-development-system.html">1.3.2. Required Packages for the Host Development System</a></span></dt>
97</dl></dd>
98<dt><span class="section"><a href="intro-getit.html">1.4. Obtaining the Yocto Project</a></span></dt>
99<dt><span class="section"><a href="intro-getit-dev.html">1.5. Development Checkouts</a></span></dt>
100</dl></dd>
101<dt><span class="chapter"><a href="usingpoky.html">2. Using the Yocto Project</a></span></dt>
102<dd><dl>
103<dt><span class="section"><a href="usingpoky-build.html">2.1. Running a Build</a></span></dt>
104<dd><dl>
105<dt><span class="section"><a href="build-overview.html">2.1.1. Build Overview</a></span></dt>
106<dt><span class="section"><a href="building-an-image-using-gpl-components.html">2.1.2. Building an Image Using GPL Components</a></span></dt>
107</dl></dd>
108<dt><span class="section"><a href="usingpoky-install.html">2.2. Installing and Using the Result</a></span></dt>
109<dt><span class="section"><a href="usingpoky-debugging.html">2.3. Debugging Build Failures</a></span></dt>
110<dd><dl>
111<dt><span class="section"><a href="usingpoky-debugging-taskfailures.html">2.3.1. Task Failures</a></span></dt>
112<dt><span class="section"><a href="usingpoky-debugging-taskrunning.html">2.3.2. Running Specific Tasks</a></span></dt>
113<dt><span class="section"><a href="usingpoky-debugging-dependencies.html">2.3.3. Dependency Graphs</a></span></dt>
114<dt><span class="section"><a href="usingpoky-debugging-bitbake.html">2.3.4. General BitBake Problems</a></span></dt>
115<dt><span class="section"><a href="usingpoky-debugging-buildfile.html">2.3.5. Building with No Dependencies</a></span></dt>
116<dt><span class="section"><a href="usingpoky-debugging-variables.html">2.3.6. Variables</a></span></dt>
117<dt><span class="section"><a href="recipe-logging-mechanisms.html">2.3.7. Recipe Logging Mechanisms</a></span></dt>
118<dt><span class="section"><a href="usingpoky-debugging-others.html">2.3.8. Other Tips</a></span></dt>
119</dl></dd>
120<dt><span class="section"><a href="maintaining-build-output-quality.html">2.4. Maintaining Build Output Quality</a></span></dt>
121<dd><dl>
122<dt><span class="section"><a href="enabling-and-disabling-build-history.html">2.4.1. Enabling and Disabling Build History</a></span></dt>
123<dt><span class="section"><a href="understanding-what-the-build-history-contains.html">2.4.2. Understanding What the Build History Contains</a></span></dt>
124</dl></dd>
125</dl></dd>
126<dt><span class="chapter"><a href="technical-details.html">3. Technical Details</a></span></dt>
127<dd><dl>
128<dt><span class="section"><a href="usingpoky-components.html">3.1. Yocto Project Components</a></span></dt>
129<dd><dl>
130<dt><span class="section"><a href="usingpoky-components-bitbake.html">3.1.1. BitBake</a></span></dt>
131<dt><span class="section"><a href="usingpoky-components-metadata.html">3.1.2. Metadata (Recipes)</a></span></dt>
132<dt><span class="section"><a href="usingpoky-components-classes.html">3.1.3. Classes</a></span></dt>
133<dt><span class="section"><a href="usingpoky-components-configuration.html">3.1.4. Configuration</a></span></dt>
134</dl></dd>
135<dt><span class="section"><a href="shared-state-cache.html">3.2. Shared State Cache</a></span></dt>
136<dd><dl>
137<dt><span class="section"><a href="overall-architecture.html">3.2.1. Overall Architecture</a></span></dt>
138<dt><span class="section"><a href="checksums.html">3.2.2. Checksums (Signatures)</a></span></dt>
139<dt><span class="section"><a href="shared-state.html">3.2.3. Shared State</a></span></dt>
140<dt><span class="section"><a href="tips-and-tricks.html">3.2.4. Tips and Tricks</a></span></dt>
141</dl></dd>
142<dt><span class="section"><a href="x32.html">3.3. x32</a></span></dt>
143<dd><dl>
144<dt><span class="section"><a href="support.html">3.3.1. Support</a></span></dt>
145<dt><span class="section"><a href="future-development-and-limitations.html">3.3.2. Future Development and Limitations</a></span></dt>
146<dt><span class="section"><a href="using-x32-right-now.html">3.3.3. Using x32 Right Now</a></span></dt>
147</dl></dd>
148<dt><span class="section"><a href="licenses.html">3.4. Licenses</a></span></dt>
149<dd><dl>
150<dt><span class="section"><a href="usingpoky-configuring-LIC_FILES_CHKSUM.html">3.4.1. Tracking License Changes</a></span></dt>
151<dt><span class="section"><a href="enabling-commercially-licensed-recipes.html">3.4.2. Enabling Commercially Licensed Recipes</a></span></dt>
152</dl></dd>
153</dl></dd>
154<dt><span class="chapter"><a href="migration.html">4. Migrating to a Newer Yocto Project Release</a></span></dt>
155<dd><dl>
156<dt><span class="section"><a href="moving-to-the-yocto-project-1.3-release.html">4.1. Moving to the Yocto Project 1.3 Release</a></span></dt>
157<dd><dl>
158<dt><span class="section"><a href="1.3-local-configuration.html">4.1.1. Local Configuration</a></span></dt>
159<dt><span class="section"><a href="1.3-recipes.html">4.1.2. Recipes</a></span></dt>
160</dl></dd>
161</dl></dd>
162<dt><span class="chapter"><a href="ref-structure.html">5. Source Directory Structure</a></span></dt>
163<dd><dl>
164<dt><span class="section"><a href="structure-core.html">5.1. Top level core components</a></span></dt>
165<dd><dl>
166<dt><span class="section"><a href="structure-core-bitbake.html">5.1.1. <code class="filename">bitbake/</code></a></span></dt>
167<dt><span class="section"><a href="structure-core-build.html">5.1.2. <code class="filename">build/</code></a></span></dt>
168<dt><span class="section"><a href="handbook.html">5.1.3. <code class="filename">documentation</code></a></span></dt>
169<dt><span class="section"><a href="structure-core-meta.html">5.1.4. <code class="filename">meta/</code></a></span></dt>
170<dt><span class="section"><a href="structure-core-meta-yocto.html">5.1.5. <code class="filename">meta-yocto/</code></a></span></dt>
171<dt><span class="section"><a href="structure-core-meta-yocto-bsp.html">5.1.6. <code class="filename">meta-yocto-bsp/</code></a></span></dt>
172<dt><span class="section"><a href="structure-meta-hob.html">5.1.7. <code class="filename">meta-hob/</code></a></span></dt>
173<dt><span class="section"><a href="structure-meta-skeleton.html">5.1.8. <code class="filename">meta-skeleton/</code></a></span></dt>
174<dt><span class="section"><a href="structure-core-scripts.html">5.1.9. <code class="filename">scripts/</code></a></span></dt>
175<dt><span class="section"><a href="structure-core-script.html">5.1.10. <code class="filename">oe-init-build-env</code></a></span></dt>
176<dt><span class="section"><a href="structure-basic-top-level.html">5.1.11. <code class="filename">LICENSE, README, and README.hardware</code></a></span></dt>
177</dl></dd>
178<dt><span class="section"><a href="structure-build.html">5.2. The Build Directory - <code class="filename">build/</code></a></span></dt>
179<dd><dl>
180<dt><span class="section"><a href="structure-build-pseudodone.html">5.2.1. <code class="filename">build/pseudodone</code></a></span></dt>
181<dt><span class="section"><a href="structure-build-conf-local.conf.html">5.2.2. <code class="filename">build/conf/local.conf</code></a></span></dt>
182<dt><span class="section"><a href="structure-build-conf-bblayers.conf.html">5.2.3. <code class="filename">build/conf/bblayers.conf</code></a></span></dt>
183<dt><span class="section"><a href="structure-build-conf-sanity_info.html">5.2.4. <code class="filename">build/conf/sanity_info</code></a></span></dt>
184<dt><span class="section"><a href="structure-build-downloads.html">5.2.5. <code class="filename">build/downloads/</code></a></span></dt>
185<dt><span class="section"><a href="structure-build-sstate-cache.html">5.2.6. <code class="filename">build/sstate-cache/</code></a></span></dt>
186<dt><span class="section"><a href="structure-build-tmp.html">5.2.7. <code class="filename">build/tmp/</code></a></span></dt>
187<dt><span class="section"><a href="structure-build-tmp-buildstats.html">5.2.8. <code class="filename">build/tmp/buildstats/</code></a></span></dt>
188<dt><span class="section"><a href="structure-build-tmp-cache.html">5.2.9. <code class="filename">build/tmp/cache/</code></a></span></dt>
189<dt><span class="section"><a href="structure-build-tmp-deploy.html">5.2.10. <code class="filename">build/tmp/deploy/</code></a></span></dt>
190<dt><span class="section"><a href="structure-build-tmp-deploy-deb.html">5.2.11. <code class="filename">build/tmp/deploy/deb/</code></a></span></dt>
191<dt><span class="section"><a href="structure-build-tmp-deploy-rpm.html">5.2.12. <code class="filename">build/tmp/deploy/rpm/</code></a></span></dt>
192<dt><span class="section"><a href="structure-build-tmp-deploy-licenses.html">5.2.13. <code class="filename">build/tmp/deploy/licenses/</code></a></span></dt>
193<dt><span class="section"><a href="structure-build-tmp-deploy-images.html">5.2.14. <code class="filename">build/tmp/deploy/images/</code></a></span></dt>
194<dt><span class="section"><a href="structure-build-tmp-deploy-ipk.html">5.2.15. <code class="filename">build/tmp/deploy/ipk/</code></a></span></dt>
195<dt><span class="section"><a href="structure-build-tmp-sysroots.html">5.2.16. <code class="filename">build/tmp/sysroots/</code></a></span></dt>
196<dt><span class="section"><a href="structure-build-tmp-stamps.html">5.2.17. <code class="filename">build/tmp/stamps/</code></a></span></dt>
197<dt><span class="section"><a href="structure-build-tmp-log.html">5.2.18. <code class="filename">build/tmp/log/</code></a></span></dt>
198<dt><span class="section"><a href="structure-build-tmp-pkgdata.html">5.2.19. <code class="filename">build/tmp/pkgdata/</code></a></span></dt>
199<dt><span class="section"><a href="structure-build-tmp-work.html">5.2.20. <code class="filename">build/tmp/work/</code></a></span></dt>
200</dl></dd>
201<dt><span class="section"><a href="structure-meta.html">5.3. The Metadata - <code class="filename">meta/</code></a></span></dt>
202<dd><dl>
203<dt><span class="section"><a href="structure-meta-classes.html">5.3.1. <code class="filename">meta/classes/</code></a></span></dt>
204<dt><span class="section"><a href="structure-meta-conf.html">5.3.2. <code class="filename">meta/conf/</code></a></span></dt>
205<dt><span class="section"><a href="structure-meta-conf-machine.html">5.3.3. <code class="filename">meta/conf/machine/</code></a></span></dt>
206<dt><span class="section"><a href="structure-meta-conf-distro.html">5.3.4. <code class="filename">meta/conf/distro/</code></a></span></dt>
207<dt><span class="section"><a href="structure-meta-recipes-bsp.html">5.3.5. <code class="filename">meta/recipes-bsp/</code></a></span></dt>
208<dt><span class="section"><a href="structure-meta-recipes-connectivity.html">5.3.6. <code class="filename">meta/recipes-connectivity/</code></a></span></dt>
209<dt><span class="section"><a href="structure-meta-recipes-core.html">5.3.7. <code class="filename">meta/recipes-core/</code></a></span></dt>
210<dt><span class="section"><a href="structure-meta-recipes-devtools.html">5.3.8. <code class="filename">meta/recipes-devtools/</code></a></span></dt>
211<dt><span class="section"><a href="structure-meta-recipes-extended.html">5.3.9. <code class="filename">meta/recipes-extended/</code></a></span></dt>
212<dt><span class="section"><a href="structure-meta-recipes-gnome.html">5.3.10. <code class="filename">meta/recipes-gnome/</code></a></span></dt>
213<dt><span class="section"><a href="structure-meta-recipes-graphics.html">5.3.11. <code class="filename">meta/recipes-graphics/</code></a></span></dt>
214<dt><span class="section"><a href="structure-meta-recipes-kernel.html">5.3.12. <code class="filename">meta/recipes-kernel/</code></a></span></dt>
215<dt><span class="section"><a href="structure-meta-recipes-multimedia.html">5.3.13. <code class="filename">meta/recipes-multimedia/</code></a></span></dt>
216<dt><span class="section"><a href="structure-meta-recipes-qt.html">5.3.14. <code class="filename">meta/recipes-qt/</code></a></span></dt>
217<dt><span class="section"><a href="structure-meta-recipes-rt.html">5.3.15. <code class="filename">meta/recipes-rt/</code></a></span></dt>
218<dt><span class="section"><a href="structure-meta-recipes-sato.html">5.3.16. <code class="filename">meta/recipes-sato/</code></a></span></dt>
219<dt><span class="section"><a href="structure-meta-recipes-support.html">5.3.17. <code class="filename">meta/recipes-support/</code></a></span></dt>
220<dt><span class="section"><a href="structure-meta-site.html">5.3.18. <code class="filename">meta/site/</code></a></span></dt>
221<dt><span class="section"><a href="structure-meta-recipes-txt.html">5.3.19. <code class="filename">meta/recipes.txt</code></a></span></dt>
222</dl></dd>
223</dl></dd>
224<dt><span class="chapter"><a href="ref-bitbake.html">6. BitBake</a></span></dt>
225<dd><dl>
226<dt><span class="section"><a href="ref-bitbake-parsing.html">6.1. Parsing</a></span></dt>
227<dt><span class="section"><a href="ref-bitbake-providers.html">6.2. Preferences and Providers</a></span></dt>
228<dt><span class="section"><a href="ref-bitbake-dependencies.html">6.3. Dependencies</a></span></dt>
229<dt><span class="section"><a href="ref-bitbake-tasklist.html">6.4. The Task List</a></span></dt>
230<dt><span class="section"><a href="ref-bitbake-runtask.html">6.5. Running a Task</a></span></dt>
231<dt><span class="section"><a href="ref-bitbake-commandline.html">6.6. BitBake Command Line</a></span></dt>
232<dt><span class="section"><a href="ref-bitbake-fetchers.html">6.7. Fetchers</a></span></dt>
233</dl></dd>
234<dt><span class="chapter"><a href="ref-classes.html">7. Classes</a></span></dt>
235<dd><dl>
236<dt><span class="section"><a href="ref-classes-base.html">7.1. The base class - <code class="filename">base.bbclass</code></a></span></dt>
237<dt><span class="section"><a href="ref-classes-autotools.html">7.2. Autotooled Packages - <code class="filename">autotools.bbclass</code></a></span></dt>
238<dt><span class="section"><a href="ref-classes-update-alternatives.html">7.3. Alternatives - <code class="filename">update-alternatives.bbclass</code></a></span></dt>
239<dt><span class="section"><a href="ref-classes-update-rc.d.html">7.4. Initscripts - <code class="filename">update-rc.d.bbclass</code></a></span></dt>
240<dt><span class="section"><a href="ref-classes-binconfig.html">7.5. Binary config scripts - <code class="filename">binconfig.bbclass</code></a></span></dt>
241<dt><span class="section"><a href="ref-classes-debian.html">7.6. Debian renaming - <code class="filename">debian.bbclass</code></a></span></dt>
242<dt><span class="section"><a href="ref-classes-pkgconfig.html">7.7. Pkg-config - <code class="filename">pkgconfig.bbclass</code></a></span></dt>
243<dt><span class="section"><a href="ref-classes-src-distribute.html">7.8. Distribution of sources - <code class="filename">src_distribute_local.bbclass</code></a></span></dt>
244<dt><span class="section"><a href="ref-classes-perl.html">7.9. Perl modules - <code class="filename">cpan.bbclass</code></a></span></dt>
245<dt><span class="section"><a href="ref-classes-distutils.html">7.10. Python extensions - <code class="filename">distutils.bbclass</code></a></span></dt>
246<dt><span class="section"><a href="ref-classes-devshell.html">7.11. Developer Shell - <code class="filename">devshell.bbclass</code></a></span></dt>
247<dt><span class="section"><a href="ref-classes-packagegroup.html">7.12. Package Groups - <code class="filename">packagegroup.bbclass</code></a></span></dt>
248<dt><span class="section"><a href="ref-classes-package.html">7.13. Packaging - <code class="filename">package*.bbclass</code></a></span></dt>
249<dt><span class="section"><a href="ref-classes-kernel.html">7.14. Building kernels - <code class="filename">kernel.bbclass</code></a></span></dt>
250<dt><span class="section"><a href="ref-classes-image.html">7.15. Creating images - <code class="filename">image.bbclass</code> and <code class="filename">rootfs*.bbclass</code></a></span></dt>
251<dt><span class="section"><a href="ref-classes-sanity.html">7.16. Host System sanity checks - <code class="filename">sanity.bbclass</code></a></span></dt>
252<dt><span class="section"><a href="ref-classes-insane.html">7.17. Generated output quality assurance checks - <code class="filename">insane.bbclass</code></a></span></dt>
253<dt><span class="section"><a href="ref-classes-siteinfo.html">7.18. Autotools configuration data cache - <code class="filename">siteinfo.bbclass</code></a></span></dt>
254<dt><span class="section"><a href="ref-classes-useradd.html">7.19. Adding Users - <code class="filename">useradd.bbclass</code></a></span></dt>
255<dt><span class="section"><a href="ref-classes-externalsrc.html">7.20. Using External Source - <code class="filename">externalsrc.bbclass</code></a></span></dt>
256<dt><span class="section"><a href="ref-classes-others.html">7.21. Other Classes</a></span></dt>
257</dl></dd>
258<dt><span class="chapter"><a href="ref-images.html">8. Images</a></span></dt>
259<dt><span class="chapter"><a href="ref-features.html">9. Reference: Features</a></span></dt>
260<dd><dl>
261<dt><span class="section"><a href="ref-features-distro.html">9.1. Distro</a></span></dt>
262<dt><span class="section"><a href="ref-features-machine.html">9.2. Machine</a></span></dt>
263<dt><span class="section"><a href="ref-features-image.html">9.3. Images</a></span></dt>
264<dt><span class="section"><a href="ref-features-backfill.html">9.4. Feature Backfilling</a></span></dt>
265</dl></dd>
266<dt><span class="chapter"><a href="ref-variables-glos.html">10. Variables Glossary</a></span></dt>
267<dd><dl><dt><span class="glossary"><a href="ref-variables-glos.html#ref-variables-glossary">Glossary</a></span></dt></dl></dd>
268<dt><span class="chapter"><a href="ref-varlocality.html">11. Variable Context</a></span></dt>
269<dd><dl>
270<dt><span class="section"><a href="ref-varlocality-configuration.html">11.1. Configuration</a></span></dt>
271<dd><dl>
272<dt><span class="section"><a href="ref-varlocality-config-distro.html">11.1.1. Distribution (Distro)</a></span></dt>
273<dt><span class="section"><a href="ref-varlocality-config-machine.html">11.1.2. Machine</a></span></dt>
274<dt><span class="section"><a href="ref-varlocality-config-local.html">11.1.3. Local</a></span></dt>
275</dl></dd>
276<dt><span class="section"><a href="ref-varlocality-recipes.html">11.2. Recipes</a></span></dt>
277<dd><dl>
278<dt><span class="section"><a href="ref-varlocality-recipe-required.html">11.2.1. Required</a></span></dt>
279<dt><span class="section"><a href="ref-varlocality-recipe-dependencies.html">11.2.2. Dependencies</a></span></dt>
280<dt><span class="section"><a href="ref-varlocality-recipe-paths.html">11.2.3. Paths</a></span></dt>
281<dt><span class="section"><a href="ref-varlocality-recipe-build.html">11.2.4. Extra Build Information</a></span></dt>
282</dl></dd>
283</dl></dd>
284<dt><span class="chapter"><a href="faq.html">12. FAQ</a></span></dt>
285<dt><span class="chapter"><a href="resources.html">13. Contributing to the Yocto Project</a></span></dt>
286<dd><dl>
287<dt><span class="section"><a href="resources-intro.html">13.1. Introduction</a></span></dt>
288<dt><span class="section"><a href="resources-bugtracker.html">13.2. Tracking Bugs</a></span></dt>
289<dt><span class="section"><a href="resources-mailinglist.html">13.3. Mailing lists</a></span></dt>
290<dt><span class="section"><a href="resources-irc.html">13.4. Internet Relay Chat (IRC)</a></span></dt>
291<dt><span class="section"><a href="resources-links.html">13.5. Links</a></span></dt>
292<dt><span class="section"><a href="resources-contributions.html">13.6. Contributions</a></span></dt>
293</dl></dd>
294</dl>
295</div>
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326</div></body>
327</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/index.xml b/documentation/ref-manual/eclipse/html/poky-ref-manual/index.xml
deleted file mode 100644
index 9edb4b92ac..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/index.xml
+++ /dev/null
@@ -1,2 +0,0 @@
1<?xml version="1.0" encoding="utf-8" standalone="no"?>
2<index/>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit-dev.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit-dev.html
deleted file mode 100644
index 0a2590314f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit-dev.html
+++ /dev/null
@@ -1,26 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.5. Development Checkouts</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro.html" title="Chapter 1. Introduction">
9<link rel="prev" href="intro-getit.html" title="1.4. Obtaining the Yocto Project">
10<link rel="next" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.5. Development Checkouts">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="intro-getit-dev"></a>1.5. Development Checkouts</h2></div></div></div>
15<p>
16 Development using the Yocto Project requires a local
17 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
18 You can set up the source directory by downloading a Yocto Project release tarball and unpacking it,
19 or by cloning a copy of the upstream
20 <a class="link" href="../dev-manual/poky.html" target="_self">Poky</a> Git repository.
21 For information on both these methods, see the
22 "<a class="link" href="../dev-manual/getting-setup.html" target="_self">Getting Setup</a>"
23 section in the Yocto Project Development Manual.
24 </p>
25</div></body>
26</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit.html
deleted file mode 100644
index 56fa85f771..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-getit.html
+++ /dev/null
@@ -1,35 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.4. Obtaining the Yocto Project</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro.html" title="Chapter 1. Introduction">
9<link rel="prev" href="centos-packages.html" title="1.3.2.4. CentOS Packages">
10<link rel="next" href="intro-getit-dev.html" title="1.5. Development Checkouts">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.4. Obtaining the Yocto Project">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="intro-getit"></a>1.4. Obtaining the Yocto Project</h2></div></div></div>
15<p>
16 The Yocto Project development team makes the Yocto Project available through a number
17 of methods:
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem"><p><span class="emphasis"><em>Releases:</em></span> Stable, tested releases are available through
21 <a class="ulink" href="http://downloads.yoctoproject.org/releases/yocto/" target="_self">http://downloads.yoctoproject.org/releases/yocto/</a>.</p></li>
22<li class="listitem"><p><span class="emphasis"><em>Nightly Builds:</em></span> These releases are available at
23 <a class="ulink" href="http://autobuilder.yoctoproject.org/nightly" target="_self">http://autobuilder.yoctoproject.org/nightly</a>.
24 These builds include Yocto Project releases, meta-toolchain tarball installation scripts, and
25 experimental builds.</p></li>
26<li class="listitem"><p><span class="emphasis"><em>Yocto Project Website:</em></span> You can find releases
27 of the Yocto Project and supported BSPs at the
28 <a class="ulink" href="http://www.yoctoproject.org" target="_self">Yocto Project website</a>.
29 Along with these downloads, you can find lots of other information at this site.
30 </p></li>
31</ul></div>
32<p>
33 </p>
34</div></body>
35</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-manualoverview.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-manualoverview.html
deleted file mode 100644
index 7f8e368e6d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-manualoverview.html
+++ /dev/null
@@ -1,73 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.2. Documentation Overview</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro.html" title="Chapter 1. Introduction">
9<link rel="prev" href="intro-welcome.html" title="1.1. Introduction">
10<link rel="next" href="intro-requirements.html" title="1.3. System Requirements">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.2. Documentation Overview">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="intro-manualoverview"></a>1.2. Documentation Overview</h2></div></div></div>
15<p>
16 This reference manual consists of the following:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><span class="emphasis"><em>
20 <a class="link" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">Using the Yocto Project</a>:</em></span> This chapter
21 provides an overview of the components that make up the Yocto Project
22 followed by information about debugging images created in the Yocto Project.
23 </p></li>
24<li class="listitem"><p><span class="emphasis"><em>
25 <a class="link" href="technical-details.html" title="Chapter 3. Technical Details">Technical Details</a>:</em></span>
26 This chapter describes fundamental Yocto Project components as well as an explanation
27 behind how the Yocto Project uses shared state (sstate) cache to speed build time.
28 </p></li>
29<li class="listitem"><p><span class="emphasis"><em>
30 <a class="link" href="ref-structure.html" title="Chapter 5. Source Directory Structure">Directory Structure</a>:</em></span>
31 This chapter describes the
32 <a class="link" href="../dev-manual/source-directory.html" target="_self">source directory</a> created
33 either by unpacking a released Yocto Project tarball on your host development system,
34 or by cloning the upstream
35 <a class="link" href="../dev-manual/poky.html" target="_self">Poky</a> Git repository.
36 </p></li>
37<li class="listitem"><p><span class="emphasis"><em>
38 <a class="link" href="ref-bitbake.html" title="Chapter 6. BitBake">BitBake</a>:</em></span>
39 This chapter provides an overview of the BitBake tool and its role within
40 the Yocto Project.</p></li>
41<li class="listitem"><p><span class="emphasis"><em>
42 <a class="link" href="ref-classes.html" title="Chapter 7. Classes">Classes</a>:</em></span>
43 This chapter describes the classes used in the Yocto Project.</p></li>
44<li class="listitem"><p><span class="emphasis"><em>
45 <a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>:</em></span>
46 This chapter describes the standard images that the Yocto Project supports.
47 </p></li>
48<li class="listitem"><p><span class="emphasis"><em>
49 <a class="link" href="ref-features.html" title="Chapter 9. Reference: Features">Features</a>:</em></span>
50 This chapter describes mechanisms for creating distribution, machine, and image
51 features during the build process using the OpenEmbedded build system.</p></li>
52<li class="listitem"><p><span class="emphasis"><em>
53 <a class="link" href="ref-variables-glos.html" title="Chapter 10. Variables Glossary">Variables Glossary</a>:</em></span>
54 This chapter presents most variables used by the OpenEmbedded build system, which
55 using BitBake.
56 Entries describe the function of the variable and how to apply them.
57 </p></li>
58<li class="listitem"><p><span class="emphasis"><em>
59 <a class="link" href="ref-varlocality.html" title="Chapter 11. Variable Context">Variable Context</a>:</em></span>
60 This chapter provides variable locality or context.</p></li>
61<li class="listitem"><p><span class="emphasis"><em>
62 <a class="link" href="faq.html" title="Chapter 12. FAQ">FAQ</a>:</em></span>
63 This chapter provides answers for commonly asked questions in the Yocto Project
64 development environment.</p></li>
65<li class="listitem"><p><span class="emphasis"><em>
66 <a class="link" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">Contributing to the Yocto Project</a>:</em></span>
67 This chapter provides guidance on how you can contribute back to the Yocto
68 Project.</p></li>
69</ul></div>
70<p>
71 </p>
72</div></body>
73</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-requirements.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-requirements.html
deleted file mode 100644
index 3cab8ac66c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-requirements.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3. System Requirements</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro.html" title="Chapter 1. Introduction">
9<link rel="prev" href="intro-manualoverview.html" title="1.2. Documentation Overview">
10<link rel="next" href="detailed-supported-distros.html" title="1.3.1. Supported Linux Distributions">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3. System Requirements">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="intro-requirements"></a>1.3. System Requirements</h2></div></div></div>
15<p>
16 For general Yocto Project system requirements, see the
17 "<a class="link" href="../yocto-project-qs/yp-resources.html" target="_self">What You Need and How You Get It</a>" section
18 in the Yocto Project Quick Start.
19 The remainder of this section provides details on system requirements
20 not covered in the Yocto Project Quick Start.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-welcome.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-welcome.html
deleted file mode 100644
index 378b87f2ed..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro-welcome.html
+++ /dev/null
@@ -1,30 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.1. Introduction</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro.html" title="Chapter 1. Introduction">
9<link rel="prev" href="intro.html" title="Chapter 1. Introduction">
10<link rel="next" href="intro-manualoverview.html" title="1.2. Documentation Overview">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.1. Introduction">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="intro-welcome"></a>1.1. Introduction</h2></div></div></div>
15<p>
16 This manual provides reference information for the current release of the Yocto Project.
17 The Yocto Project is an open-source collaboration project focused on embedded Linux
18 developers.
19 Amongst other things, the Yocto Project uses the OpenEmbedded build system, which
20 is based on the Poky project, to construct complete Linux images.
21 You can find complete introductory and getting started information on the Yocto Project
22 by reading the
23 <a class="link" href="../yocto-project-qs/index.html" target="_self">Yocto Project Quick Start</a>.
24 For task-based information using the Yocto Project, see the
25 <a class="link" href="../dev-manual/index.html" target="_self">Yocto Project Development Manual</a>.
26 You can also find lots of information on the Yocto Project on the
27 <a class="ulink" href="http://www.yoctoproject.org" target="_self">Yocto Project website</a>.
28 </p>
29</div></body>
30</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/intro.html
deleted file mode 100644
index 1ff7cdcd05..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/intro.html
+++ /dev/null
@@ -1,30 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 1. Introduction</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="index.html" title="The Yocto Project Reference Manual">
10<link rel="next" href="intro-welcome.html" title="1.1. Introduction">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 1. Introduction">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="intro"></a>Chapter 1. Introduction</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="intro-welcome.html">1.1. Introduction</a></span></dt>
19<dt><span class="section"><a href="intro-manualoverview.html">1.2. Documentation Overview</a></span></dt>
20<dt><span class="section"><a href="intro-requirements.html">1.3. System Requirements</a></span></dt>
21<dd><dl>
22<dt><span class="section"><a href="detailed-supported-distros.html">1.3.1. Supported Linux Distributions</a></span></dt>
23<dt><span class="section"><a href="required-packages-for-the-host-development-system.html">1.3.2. Required Packages for the Host Development System</a></span></dt>
24</dl></dd>
25<dt><span class="section"><a href="intro-getit.html">1.4. Obtaining the Yocto Project</a></span></dt>
26<dt><span class="section"><a href="intro-getit-dev.html">1.5. Development Checkouts</a></span></dt>
27</dl>
28</div>
29</div></body>
30</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/invalidating-shared-state.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/invalidating-shared-state.html
deleted file mode 100644
index 425f17953d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/invalidating-shared-state.html
+++ /dev/null
@@ -1,53 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.4.2. Invalidating Shared State</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="tips-and-tricks.html" title="3.2.4. Tips and Tricks">
9<link rel="prev" href="debugging.html" title="3.2.4.1. Debugging">
10<link rel="next" href="x32.html" title="3.3. x32">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.4.2. Invalidating Shared State">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="invalidating-shared-state"></a>3.2.4.2. Invalidating Shared State</h4></div></div></div>
15<p>
16 The shared state code uses checksums and shared state
17 cache to avoid unnecessarily rebuilding tasks.
18 As with all schemes, this one has some drawbacks.
19 It is possible that you could make implicit changes that are not factored
20 into the checksum calculation, but do affect a task's output.
21 A good example is perhaps when a tool changes its output.
22 Let's say that the output of <code class="filename">rpmdeps</code> needed to change.
23 The result of the change should be that all the "package", "package_write_rpm",
24 and "package_deploy-rpm" shared state cache items would become invalid.
25 But, because this is a change that is external to the code and therefore implicit,
26 the associated shared state cache items do not become invalidated.
27 In this case, the build process would use the cached items rather than running the
28 task again.
29 Obviously, these types of implicit changes can cause problems.
30 </p>
31<p>
32 To avoid these problems during the build, you need to understand the effects of any
33 change you make.
34 Note that any changes you make directly to a function automatically are factored into
35 the checksum calculation and thus, will invalidate the associated area of sstate cache.
36 You need to be aware of any implicit changes that are not obvious changes to the
37 code and could affect the output of a given task.
38 Once you are aware of such a change, you can take steps to invalidate the cache
39 and force the task to run.
40 The step to take is as simple as changing a function's comments in the source code.
41 For example, to invalidate package shared state files, change the comment statements
42 of <code class="filename">do_package</code> or the comments of one of the functions it calls.
43 The change is purely cosmetic, but it causes the checksum to be recalculated and
44 forces the task to be run again.
45 </p>
46<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
47<h3 class="title">Note</h3>
48 For an example of a commit that makes a cosmetic change to invalidate
49 a shared state, see this
50 <a class="ulink" href="http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/classes/package.bbclass?id=737f8bbb4f27b4837047cb9b4fbfe01dfde36d54" target="_self">commit</a>.
51 </div>
52</div></body>
53</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/license-flag-matching.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/license-flag-matching.html
deleted file mode 100644
index 8909689399..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/license-flag-matching.html
+++ /dev/null
@@ -1,91 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4.2.1. License Flag Matching</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes">
9<link rel="prev" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes">
10<link rel="next" href="other-variables-related-to-commercial-licenses.html" title="3.4.2.2. Other Variables Related to Commercial Licenses">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.2.1. License Flag Matching">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="license-flag-matching"></a>3.4.2.1. License Flag Matching</h4></div></div></div>
15<p>
16 The definition of 'matching' in reference to a
17 recipe's <code class="filename">LICENSE_FLAGS</code> setting is simple.
18 However, some things exist that you should know about in order to
19 correctly and effectively use it.
20 </p>
21<p>
22 Before a flag
23 defined by a particular recipe is tested against the
24 contents of the <code class="filename">LICENSE_FLAGS_WHITELIST</code> variable, the
25 string <code class="filename">_${PN}</code> (with
26 <a class="link" href="ref-variables-glos.html#var-PN" title="PN"><code class="filename">PN</code></a> expanded of course) is
27 appended to the flag, thus automatically making each
28 <code class="filename">LICENSE_FLAGS</code> value recipe-specific.
29 That string is
30 then matched against the whitelist.
31 So if you specify <code class="filename">LICENSE_FLAGS = "commercial"</code> in recipe
32 "foo" for example, the string <code class="filename">"commercial_foo"</code>
33 would normally be what is specified in the whitelist in order for it to
34 match.
35 </p>
36<p>
37 You can broaden the match by
38 putting any "_"-separated beginning subset of a
39 <code class="filename">LICENSE_FLAGS</code> flag in the whitelist, which will also
40 match.
41 For example, simply specifying "commercial" in
42 the whitelist would match any expanded <code class="filename">LICENSE_FLAGS</code>
43 definition starting with "commercial" such as
44 "commercial_foo" and "commercial_bar", which are the
45 strings that would be automatically generated for
46 hypothetical "foo" and "bar" recipes assuming those
47 recipes had simply specified the following:
48 </p>
49<pre class="literallayout">
50 LICENSE_FLAGS = "commercial"
51 </pre>
52<p>
53 </p>
54<p>
55 Broadening the match allows for a range of specificity for the items
56 in the whitelist, from more general to perfectly
57 specific.
58 So you have the choice of exhaustively
59 enumerating each license flag in the whitelist to
60 allow only those specific recipes into the image, or
61 of using a more general string to pick up anything
62 matching just the first component or components of the specified
63 string.
64 </p>
65<p>
66 This scheme works even if the flag already
67 has <code class="filename">_${PN}</code> appended - the extra <code class="filename">_${PN}</code> is
68 redundant, but does not affect the outcome.
69 For example, a license flag of "commercial_1.2_foo" would
70 turn into "commercial_1.2_foo_foo" and would match
71 both the general "commercial" and the specific
72 "commercial_1.2_foo", as expected.
73 The flag would also match
74 "commercial_1.2_foo_foo" and "commercial_1.2", which
75 does not make much sense regarding use in the whitelist.
76 </p>
77<p>
78 For a versioned string, you could instead specify
79 "commercial_foo_1.2", which would turn into
80 "commercial_foo_1.2_foo".
81 And, as expected, this flag allows
82 you to pick up this package along with
83 anything else "commercial" when you specify "commercial"
84 in the whitelist.
85 Or, the flag allows you to pick up this package along with anything "commercial_foo"
86 regardless of version when you use "commercial_foo" in the whitelist.
87 Finally, you can be completely specific about the package and version and specify
88 "commercial_foo_1.2" package and version.
89 </p>
90</div></body>
91</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/licenses.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/licenses.html
deleted file mode 100644
index 3af03e999f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/licenses.html
+++ /dev/null
@@ -1,28 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4. Licenses</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="technical-details.html" title="Chapter 3. Technical Details">
9<link rel="prev" href="using-x32-right-now.html" title="3.3.3. Using x32 Right Now">
10<link rel="next" href="usingpoky-configuring-LIC_FILES_CHKSUM.html" title="3.4.1. Tracking License Changes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4. Licenses">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="licenses"></a>3.4. Licenses</h2></div></div></div>
15<p>
16 This section describes the mechanism by which the OpenEmbedded build system
17 tracks changes to licensing text.
18 The section also describes how to enable commercially licensed recipes,
19 which by default are disabled.
20 </p>
21<p>
22 For information that can help you maintain compliance with various open
23 source licensing during the lifecycle of the product, see the
24 "<a class="link" href="../dev-manual/maintaining-open-source-license-compliance-during-your-products-lifecycle.html" target="_self">Maintaining Open Source License Compliance During Your Project's Lifecycle</a>" section
25 in the Yocto Project Development Manual.
26 </p>
27</div></body>
28</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-bash.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-bash.html
deleted file mode 100644
index 3cea310b1f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-bash.html
+++ /dev/null
@@ -1,47 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.7.2. Logging With Bash</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="recipe-logging-mechanisms.html" title="2.3.7. Recipe Logging Mechanisms">
9<link rel="prev" href="logging-with-python.html" title="2.3.7.1. Logging With Python">
10<link rel="next" href="usingpoky-debugging-others.html" title="2.3.8. Other Tips">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.7.2. Logging With Bash">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="logging-with-bash"></a>2.3.7.2. Logging With Bash</h4></div></div></div>
15<p>
16 When creating recipes using Bash and inserting code that handles build
17 logs you have the same goals - informative with minimal console output.
18 The syntax you use for recipes written in Bash is similar to that of
19 recipes written in Python described in the previous section.
20 </p>
21<p>
22 Following is an example written in Bash.
23 The code logs the progress of the <code class="filename">do_my_function</code> function.
24 </p>
25<pre class="literallayout">
26 do_my_function() {
27 bbdebug 2 "Running do_my_function"
28 if [ exceptional_condition ]; then
29 bbnote "Hit exceptional_condition"
30 fi
31 bbdebug 2 "Got to point xyz"
32 if [ warning_trigger ]; then
33 bbwarn "Detected warning_trigger, this might cause a problem later."
34 fi
35 if [ recoverable_error ]; then
36 bberror "Hit recoverable_error, correcting"
37 fi
38 if [ fatal_error ]; then
39 bbfatal "fatal_error detected"
40 fi
41 bbdebug 2 "Completed do_my_function"
42 }
43 </pre>
44<p>
45 </p>
46</div></body>
47</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html
deleted file mode 100644
index e57b647148..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html
+++ /dev/null
@@ -1,45 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.7.1. Logging With Python</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="recipe-logging-mechanisms.html" title="2.3.7. Recipe Logging Mechanisms">
9<link rel="prev" href="recipe-logging-mechanisms.html" title="2.3.7. Recipe Logging Mechanisms">
10<link rel="next" href="logging-with-bash.html" title="2.3.7.2. Logging With Bash">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.7.1. Logging With Python">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="logging-with-python"></a>2.3.7.1. Logging With Python</h4></div></div></div>
15<p>
16 When creating recipes using Python and inserting code that handles build logs
17 keep in mind the goal is to have informative logs while keeping the console as
18 "silent" as possible.
19 Also, if you want status messages in the log use the "debug" loglevel.
20 </p>
21<p>
22 Following is an example written in Python.
23 The code handles logging for a function that determines the number of tasks
24 needed to be run:
25 </p>
26<pre class="literallayout">
27 python do_listtasks() {
28 bb.debug(2, "Starting to figure out the task list")
29 if noteworthy_condition:
30 bb.note("There are 47 tasks to run")
31 bb.debug(2, "Got to point xyz")
32 if warning_trigger:
33 bb.warn("Detected warning_trigger, this might be a problem later.")
34 if recoverable_error:
35 bb.error("Hit recoverable_error, you really need to fix this!")
36 if fatal_error:
37 bb.fatal("fatal_error detected, unable to print the task list")
38 bb.plain("The tasks present are abc")
39 bb.debug(2, "Finished figuring out the tasklist")
40 }
41 </pre>
42<p>
43 </p>
44</div></body>
45</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html
deleted file mode 100644
index f0896e6c89..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/maintaining-build-output-quality.html
+++ /dev/null
@@ -1,53 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4. Maintaining Build Output Quality</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
9<link rel="prev" href="usingpoky-debugging-others.html" title="2.3.8. Other Tips">
10<link rel="next" href="enabling-and-disabling-build-history.html" title="2.4.1. Enabling and Disabling Build History">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4. Maintaining Build Output Quality">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="maintaining-build-output-quality"></a>2.4. Maintaining Build Output Quality</h2></div></div></div>
15<p>
16 A build's quality can be influenced by many things.
17 For example, if you upgrade a recipe to use a new version of an upstream software
18 package or you experiment with some new configuration options, subtle changes
19 can occur that you might not detect until later.
20 Consider the case where your recipe is using a newer version of an upstream package.
21 In this case, a new version of a piece of software might introduce an optional
22 dependency on another library, which is auto-detected.
23 If that library has already been built when the software is building,
24 then the software will link to the built library and that library will be pulled
25 into your image along with the new software even if you did not want the
26 library.
27 </p>
28<p>
29 The <code class="filename">buildhistory</code> class exists to help you maintain
30 the quality of your build output.
31 You can use the class to highlight unexpected and possibly unwanted
32 changes in the build output.
33 When you enable build history it records information about the contents of
34 each package and image and then commits that information to a local Git
35 repository where you can examine the information.
36 </p>
37<p>
38 The remainder of this section describes the following:
39 </p>
40<div class="itemizedlist"><ul class="itemizedlist" type="disc">
41<li class="listitem"><p>How you can enable and disable
42 build history</p></li>
43<li class="listitem"><p>How to understand what the build history contains
44 </p></li>
45<li class="listitem"><p>How to limit the information used for build history
46 </p></li>
47<li class="listitem"><p>How to examine the build history from both a
48 command-line and web interface</p></li>
49</ul></div>
50<p>
51 </p>
52</div></body>
53</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-bblayers-conf.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-bblayers-conf.html
deleted file mode 100644
index 50cd0caa4b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-bblayers-conf.html
+++ /dev/null
@@ -1,27 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.1.2. bblayers.conf</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-local-configuration.html" title="4.1.1. Local Configuration">
9<link rel="prev" href="migration-1.3-sstate-mirrors.html" title="4.1.1.1. SSTATE_MIRRORS">
10<link rel="next" href="1.3-recipes.html" title="4.1.2. Recipes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.1.2. bblayers.conf">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-bblayers-conf"></a>4.1.1.2. bblayers.conf</h4></div></div></div>
15<p>
16 The <code class="filename">meta-yocto</code> layer has been split into
17 two parts: <code class="filename">meta-yocto</code> and
18 <code class="filename">meta-yocto-bsp</code>, corresponding to the
19 Poky reference distro configuration and the reference
20 hardware Board Support Packages (BSPs), respectively.
21 When running BitBake or Hob for the first time after upgrading,
22 your <code class="filename">conf/bblayers.conf</code> file will be
23 updated to handle this change and you will be asked to
24 re-run/restart for the changes to take effect.
25 </p>
26</div></body>
27</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-image-features.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-image-features.html
deleted file mode 100644
index 48ef697506..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-image-features.html
+++ /dev/null
@@ -1,26 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2.5. IMAGE_FEATURES</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-recipes.html" title="4.1.2. Recipes">
9<link rel="prev" href="migration-1.3-task-recipes.html" title="4.1.2.4. Task Recipes">
10<link rel="next" href="migration-1.3-removed-recipes.html" title="4.1.2.6. Removed Recipes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2.5. IMAGE_FEATURES">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-image-features"></a>4.1.2.5. IMAGE_FEATURES</h4></div></div></div>
15<p>
16 Image recipes that previously included "apps-console-core"
17 in <a class="link" href="ref-variables-glos.html#var-IMAGE_FEATURES" title="IMAGE_FEATURES"><code class="filename">IMAGE_FEATURES</code></a>
18 should now include "splash" instead to enable the boot-up
19 splash screen.
20 Retaining "apps-console-core" will still include the splash
21 screen generates a warning.
22 The "apps-x11-core" and "apps-x11-games"
23 <code class="filename">IMAGE_FEATURES</code> features have been removed.
24 </p>
25</div></body>
26</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-nativesdk.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-nativesdk.html
deleted file mode 100644
index b20f6101e4..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-nativesdk.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2.3. nativesdk</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-recipes.html" title="4.1.2. Recipes">
9<link rel="prev" href="migration-1.3-proto=-in-src-uri.html" title="4.1.2.2. proto= in SRC_URI">
10<link rel="next" href="migration-1.3-task-recipes.html" title="4.1.2.4. Task Recipes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2.3. nativesdk">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-nativesdk"></a>4.1.2.3. nativesdk</h4></div></div></div>
15<p>
16 The suffix <code class="filename">nativesdk</code> is now implemented
17 as a prefix, which simplifies a lot of the packaging code for
18 <code class="filename">nativesdk</code> recipes.
19 All custom <code class="filename">nativesdk</code> recipes and any
20 references need to be updated to use
21 <code class="filename">nativesdk-*</code> instead of
22 <code class="filename">*-nativesdk</code>.
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-proto=-in-src-uri.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-proto=-in-src-uri.html
deleted file mode 100644
index 85702b8479..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-proto=-in-src-uri.html
+++ /dev/null
@@ -1,32 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2.2. proto= in SRC_URI</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-recipes.html" title="4.1.2. Recipes">
9<link rel="prev" href="migration-1.3-python-function-whitespace.html" title="4.1.2.1. Python Function Whitespace">
10<link rel="next" href="migration-1.3-nativesdk.html" title="4.1.2.3. nativesdk">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2.2. proto= in SRC_URI">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-proto=-in-src-uri"></a>4.1.2.2. proto= in SRC_URI</h4></div></div></div>
15<p>
16 Any use of <code class="filename">proto=</code> in
17 <a class="link" href="ref-variables-glos.html#var-SRC_URI" title="SRC_URI"><code class="filename">SRC_URI</code></a>
18 needs to be changed to <code class="filename">protocol=</code>.
19 In particular, this applies to the following URIs:
20 </p>
21<div class="itemizedlist"><ul class="itemizedlist" type="disc">
22<li class="listitem"><p><code class="filename">svn://</code></p></li>
23<li class="listitem"><p><code class="filename">bzr://</code></p></li>
24<li class="listitem"><p><code class="filename">hg://</code></p></li>
25<li class="listitem"><p><code class="filename">osc://</code></p></li>
26</ul></div>
27<p>
28 Other URIs were already using <code class="filename">protocol=</code>.
29 This change improves consistency.
30 </p>
31</div></body>
32</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-python-function-whitespace.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-python-function-whitespace.html
deleted file mode 100644
index 7b7405984c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-python-function-whitespace.html
+++ /dev/null
@@ -1,29 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2.1. Python Function Whitespace</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-recipes.html" title="4.1.2. Recipes">
9<link rel="prev" href="1.3-recipes.html" title="4.1.2. Recipes">
10<link rel="next" href="migration-1.3-proto=-in-src-uri.html" title="4.1.2.2. proto= in SRC_URI">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2.1. Python Function Whitespace">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-python-function-whitespace"></a>4.1.2.1. Python Function Whitespace</h4></div></div></div>
15<p>
16 All Python functions must now use four spaces for indentation.
17 Previously, an inconsistent mix of spaces and tabs existed,
18 which made extending these functions using
19 <code class="filename">_append</code> or <code class="filename">_prepend</code>
20 complicated given that Python treats whitespace as
21 syntactically significant.
22 If you are defining or extending any Python functions (e.g.
23 <code class="filename">populate_packages</code>, <code class="filename">do_unpack</code>,
24 <code class="filename">do_patch</code> and so forth) in custom recipes
25 or classes, you need to ensure you are using consistent
26 four-space indentation.
27 </p>
28</div></body>
29</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-removed-recipes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-removed-recipes.html
deleted file mode 100644
index ff8a213ccf..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-removed-recipes.html
+++ /dev/null
@@ -1,64 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2.6. Removed Recipes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-recipes.html" title="4.1.2. Recipes">
9<link rel="prev" href="migration-1.3-image-features.html" title="4.1.2.5. IMAGE_FEATURES">
10<link rel="next" href="ref-structure.html" title="Chapter 5. Source Directory Structure">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2.6. Removed Recipes">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-removed-recipes"></a>4.1.2.6. Removed Recipes</h4></div></div></div>
15<p>
16 The following recipes have been removed.
17 For most of them, it is unlikely that you would have any
18 references to them in your own metadata.
19 However, you should check your metadata against this list to be sure:
20 </p>
21<div class="itemizedlist"><ul class="itemizedlist" type="disc">
22<li class="listitem"><p><span class="emphasis"><em><code class="filename">libx11-trim</code></em></span>:
23 Replaced by <code class="filename">libx11</code>, which has a negligible
24 size difference with modern Xorg.</p></li>
25<li class="listitem"><p><span class="emphasis"><em><code class="filename">xserver-xorg-lite</code></em></span>:
26 Use <code class="filename">xserver-xorg</code>, which has a negligible
27 size difference when DRI and GLX modules are not installed.</p></li>
28<li class="listitem"><p><span class="emphasis"><em><code class="filename">xserver-kdrive</code></em></span>:
29 Effectively unmaintained for many years.</p></li>
30<li class="listitem"><p><span class="emphasis"><em><code class="filename">mesa-xlib</code></em></span>:
31 No longer serves any purpose.</p></li>
32<li class="listitem"><p><span class="emphasis"><em><code class="filename">galago</code></em></span>:
33 Replaced by telepathy.</p></li>
34<li class="listitem"><p><span class="emphasis"><em><code class="filename">gail</code></em></span>:
35 Functionality was integrated into GTK+ 2.13.</p></li>
36<li class="listitem"><p><span class="emphasis"><em><code class="filename">eggdbus</code></em></span>:
37 No longer needed.</p></li>
38<li class="listitem"><p><span class="emphasis"><em><code class="filename">gcc-*-intermediate</code></em></span>:
39 The build has been restructured to avoid the need for
40 this step.</p></li>
41<li class="listitem"><p><span class="emphasis"><em><code class="filename">libgsmd</code></em></span>:
42 Unmaintained for many years.
43 Functionality now provided by
44 <code class="filename">ofono</code> instead.</p></li>
45<li class="listitem"><p><span class="emphasis"><em>contacts, dates, tasks, eds-tools</em></span>:
46 Largely unmaintained PIM application suite.
47 It has been moved to <code class="filename">meta-gnome</code>
48 in <code class="filename">meta-openembedded</code>.</p></li>
49</ul></div>
50<p>
51 In addition to the previously listed changes, the
52 <code class="filename">meta-demoapps</code> directory has also been removed
53 because the recipes in it were not being maintained and many
54 had become obsolete or broken.
55 Additionally, these recipes were not parsed in the default configuration.
56 Many of these recipes are already provided in an updated and
57 maintained form within OpenEmbedded community layers such as
58 <code class="filename">meta-oe</code> and <code class="filename">meta-gnome</code>.
59 For the remainder, you can now find them in the
60 <code class="filename">meta-extras</code> repository, which is in the
61 Yocto Project source repositories.
62 </p>
63</div></body>
64</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-sstate-mirrors.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-sstate-mirrors.html
deleted file mode 100644
index b2f790649b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-sstate-mirrors.html
+++ /dev/null
@@ -1,36 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.1.1. SSTATE_MIRRORS</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-local-configuration.html" title="4.1.1. Local Configuration">
9<link rel="prev" href="1.3-local-configuration.html" title="4.1.1. Local Configuration">
10<link rel="next" href="migration-1.3-bblayers-conf.html" title="4.1.1.2. bblayers.conf">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.1.1. SSTATE_MIRRORS">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-sstate-mirrors"></a>4.1.1.1. SSTATE_MIRRORS</h4></div></div></div>
15<p>
16 The shared state cache (sstate-cache) as pointed to by
17 <a class="link" href="ref-variables-glos.html#var-SSTATE_DIR" title="SSTATE_DIR"><code class="filename">SSTATE_DIR</code></a> by default
18 now has two-character subdirectories to prevent there being an issue with too
19 many files in the same directory.
20 Also, native sstate-cache packages will go into a subdirectory named using
21 the distro ID string.
22 If you copy the newly structured sstate-cache to a mirror location
23 (either local or remote) and then point to it in
24 <a class="link" href="ref-variables-glos.html#var-SSTATE_MIRRORS" title="SSTATE_MIRRORS"><code class="filename">SSTATE_MIRRORS</code></a>,
25 you need to append "PATH" to the end of the mirror URL so that
26 the path used by BitBake before the mirror substitution is
27 appended to the path used to access the mirror.
28 Here is an example:
29 </p>
30<pre class="literallayout">
31 SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH"
32 </pre>
33<p>
34 </p>
35</div></body>
36</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-task-recipes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-task-recipes.html
deleted file mode 100644
index 1d93d893b1..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration-1.3-task-recipes.html
+++ /dev/null
@@ -1,39 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1.2.4. Task Recipes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="1.3-recipes.html" title="4.1.2. Recipes">
9<link rel="prev" href="migration-1.3-nativesdk.html" title="4.1.2.3. nativesdk">
10<link rel="next" href="migration-1.3-image-features.html" title="4.1.2.5. IMAGE_FEATURES">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1.2.4. Task Recipes">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="migration-1.3-task-recipes"></a>4.1.2.4. Task Recipes</h4></div></div></div>
15<p>
16 "Task" recipes are now known as "Package groups" and have
17 been renamed from <code class="filename">task-*.bb</code> to
18 <code class="filename">packagegroup-*.bb</code>.
19 Existing references to the previous <code class="filename">task-*</code>
20 names should work in most cases as there is an automatic
21 upgrade path for most packages.
22 However, you should update references in your own recipes and
23 configurations as they could be removed in future releases.
24 You should also rename any custom <code class="filename">task-*</code>
25 recipes to <code class="filename">packagegroup-*</code>, and change
26 them to inherit <code class="filename">packagegroup</code> instead of
27 <code class="filename">task</code>, as well as taking the opportunity
28 to remove anything now handled by
29 <code class="filename">packagegroup.bbclass</code>, such as providing
30 <code class="filename">-dev</code> and <code class="filename">-dbg</code>
31 packages, setting
32 <a class="link" href="ref-variables-glos.html#var-LIC_FILES_CHKSUM" title="LIC_FILES_CHKSUM"><code class="filename">LIC_FILES_CHKSUM</code></a>,
33 and so forth.
34 See the
35 "<a class="link" href="ref-classes-packagegroup.html" title="7.12. Package Groups - packagegroup.bbclass">Package Groups - packagegroup.bbclass</a>"
36 section for further details.
37 </p>
38</div></body>
39</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/migration.html
deleted file mode 100644
index f7bb138de9..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/migration.html
+++ /dev/null
@@ -1,31 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 4. Migrating to a Newer Yocto Project Release</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="other-variables-related-to-commercial-licenses.html" title="3.4.2.2. Other Variables Related to Commercial Licenses">
10<link rel="next" href="moving-to-the-yocto-project-1.3-release.html" title="4.1. Moving to the Yocto Project 1.3 Release">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 4. Migrating to a Newer Yocto Project Release">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="migration"></a>Chapter 4. Migrating to a Newer Yocto Project Release</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="moving-to-the-yocto-project-1.3-release.html">4.1. Moving to the Yocto Project 1.3 Release</a></span></dt>
19<dd><dl>
20<dt><span class="section"><a href="1.3-local-configuration.html">4.1.1. Local Configuration</a></span></dt>
21<dt><span class="section"><a href="1.3-recipes.html">4.1.2. Recipes</a></span></dt>
22</dl></dd>
23</dl>
24</div>
25<p>
26 This chapter provides information you can use to migrate work to a
27 newer Yocto Project release. You can find the same information in the
28 release notes for a given release.
29 </p>
30</div></body>
31</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/moving-to-the-yocto-project-1.3-release.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/moving-to-the-yocto-project-1.3-release.html
deleted file mode 100644
index 8afa731200..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/moving-to-the-yocto-project-1.3-release.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>4.1. Moving to the Yocto Project 1.3 Release</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="migration.html" title="Chapter 4. Migrating to a Newer Yocto Project Release">
9<link rel="prev" href="migration.html" title="Chapter 4. Migrating to a Newer Yocto Project Release">
10<link rel="next" href="1.3-local-configuration.html" title="4.1.1. Local Configuration">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="4.1. Moving to the Yocto Project 1.3 Release">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="moving-to-the-yocto-project-1.3-release"></a>4.1. Moving to the Yocto Project 1.3 Release</h2></div></div></div>
15<p>
16 This section provides migration information for moving to the
17 Yocto Project 1.3 Release.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/opensuse-packages.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/opensuse-packages.html
deleted file mode 100644
index 16a1860596..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/opensuse-packages.html
+++ /dev/null
@@ -1,60 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3.2.3. OpenSUSE Packages</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="required-packages-for-the-host-development-system.html" title="1.3.2. Required Packages for the Host Development System">
9<link rel="prev" href="fedora-packages.html" title="1.3.2.2. Fedora Packages">
10<link rel="next" href="centos-packages.html" title="1.3.2.4. CentOS Packages">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.2.3. OpenSUSE Packages">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="opensuse-packages"></a>1.3.2.3. OpenSUSE Packages</h4></div></div></div>
15<p>
16 The following list shows the required packages by function
17 given a supported OpenSUSE Linux distribution:
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem">
21<p><span class="emphasis"><em>Essentials:</em></span>
22 Packages needed to build an image for a headless
23 system:
24 </p>
25<pre class="literallayout">
26 $ sudo zypper install python gcc gcc-c++ git chrpath make wget python-xml \
27 diffstat texinfo python-curses
28 </pre>
29</li>
30<li class="listitem">
31<p><span class="emphasis"><em>Graphical Extras:</em></span>
32 Packages recommended if the host system has graphics support:
33 </p>
34<pre class="literallayout">
35 $ sudo zypper install libSDL-devel xterm
36 </pre>
37</li>
38<li class="listitem">
39<p><span class="emphasis"><em>Documentation:</em></span>
40 Packages needed if you are going to build out the
41 Yocto Project documentation manuals:
42 </p>
43<pre class="literallayout">
44 $ sudo zypper install make fop xsltproc
45 </pre>
46</li>
47<li class="listitem">
48<p><span class="emphasis"><em>ADT Installer Extras:</em></span>
49 Packages needed if you are going to be using the
50 <a class="link" href="../adt-manual/using-the-adt-installer.html" target="_self">Application Development Toolkit (ADT) Installer</a>:
51 </p>
52<pre class="literallayout">
53 $ sudo zypper install autoconf automake libtool glib2-devel
54 </pre>
55</li>
56</ul></div>
57<p>
58 </p>
59</div></body>
60</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html
deleted file mode 100644
index 31b096ec73..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html
+++ /dev/null
@@ -1,60 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4.2.2. Other Variables Related to Commercial Licenses</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes">
9<link rel="prev" href="license-flag-matching.html" title="3.4.2.1. License Flag Matching">
10<link rel="next" href="migration.html" title="Chapter 4. Migrating to a Newer Yocto Project Release">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.2.2. Other Variables Related to Commercial Licenses">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="other-variables-related-to-commercial-licenses"></a>3.4.2.2. Other Variables Related to Commercial Licenses</h4></div></div></div>
15<p>
16 Other helpful variables related to commercial
17 license handling exist and are defined in the
18 <code class="filename">$HOME/poky/meta/conf/distro/include/default-distrovars.inc</code> file:
19 </p>
20<pre class="literallayout">
21 COMMERCIAL_AUDIO_PLUGINS ?= ""
22 COMMERCIAL_VIDEO_PLUGINS ?= ""
23 COMMERCIAL_QT = ""
24 </pre>
25<p>
26 If you want to enable these components, you can do so by making sure you have
27 the following statements in your <code class="filename">local.conf</code> configuration file:
28 </p>
29<pre class="literallayout">
30 COMMERCIAL_AUDIO_PLUGINS = "gst-plugins-ugly-mad \
31 gst-plugins-ugly-mpegaudioparse"
32 COMMERCIAL_VIDEO_PLUGINS = "gst-plugins-ugly-mpeg2dec \
33 gst-plugins-ugly-mpegstream gst-plugins-bad-mpegvideoparse"
34 COMMERCIAL_QT ?= "qmmp"
35 LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly commercial_gst-plugins-bad commercial_qmmp"
36 </pre>
37<p>
38 Of course, you could also create a matching whitelist
39 for those components using the more general "commercial"
40 in the whitelist, but that would also enable all the
41 other packages with <code class="filename">LICENSE_FLAGS</code> containing
42 "commercial", which you may or may not want:
43 </p>
44<pre class="literallayout">
45 LICENSE_FLAGS_WHITELIST = "commercial"
46 </pre>
47<p>
48 </p>
49<p>
50 Specifying audio and video plug-ins as part of the
51 <code class="filename">COMMERCIAL_AUDIO_PLUGINS</code> and
52 <code class="filename">COMMERCIAL_VIDEO_PLUGINS</code> statements
53 or commercial qt components as part of
54 the <code class="filename">COMMERCIAL_QT</code> statement (along
55 with the enabling <code class="filename">LICENSE_FLAGS_WHITELIST</code>) includes the
56 plug-ins or components into built images, thus adding
57 support for media formats or components.
58 </p>
59</div></body>
60</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html
deleted file mode 100644
index 89a6979603..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/overall-architecture.html
+++ /dev/null
@@ -1,31 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.1. Overall Architecture</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="shared-state-cache.html" title="3.2. Shared State Cache">
9<link rel="prev" href="shared-state-cache.html" title="3.2. Shared State Cache">
10<link rel="next" href="checksums.html" title="3.2.2. Checksums (Signatures)">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.1. Overall Architecture">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="overall-architecture"></a>3.2.1. Overall Architecture</h3></div></div></div>
15<p>
16 When determining what parts of the system need to be built, BitBake
17 uses a per-task basis and does not use a per-recipe basis.
18 You might wonder why using a per-task basis is preferred over a per-recipe basis.
19 To help explain, consider having the IPK packaging backend enabled and then switching to DEB.
20 In this case, <code class="filename">do_install</code> and <code class="filename">do_package</code>
21 output are still valid.
22 However, with a per-recipe approach, the build would not include the
23 <code class="filename">.deb</code> files.
24 Consequently, you would have to invalidate the whole build and rerun it.
25 Rerunning everything is not the best situation.
26 Also in this case, the core must be "taught" much about specific tasks.
27 This methodology does not scale well and does not allow users to easily add new tasks
28 in layers or as external recipes without touching the packaged-staging core.
29 </p>
30</div></body>
31</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html
deleted file mode 100644
index add1017473..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/recipe-logging-mechanisms.html
+++ /dev/null
@@ -1,41 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.7. Recipe Logging Mechanisms</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging-variables.html" title="2.3.6. Variables">
10<link rel="next" href="logging-with-python.html" title="2.3.7.1. Logging With Python">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.7. Recipe Logging Mechanisms">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="recipe-logging-mechanisms"></a>2.3.7. Recipe Logging Mechanisms</h3></div></div></div>
15<p>
16 Best practices exist while writing recipes that both log build progress and
17 act on build conditions such as warnings and errors.
18 Both Python and Bash language bindings exist for the logging mechanism:
19 </p>
20<div class="itemizedlist"><ul class="itemizedlist" type="disc">
21<li class="listitem"><p><span class="emphasis"><em>Python:</em></span> For Python functions, BitBake
22 supports several loglevels: <code class="filename">bb.fatal</code>,
23 <code class="filename">bb.error</code>, <code class="filename">bb.warn</code>,
24 <code class="filename">bb.note</code>, <code class="filename">bb.plain</code>,
25 and <code class="filename">bb.debug</code>.</p></li>
26<li class="listitem"><p><span class="emphasis"><em>Bash:</em></span> For Bash functions, the same set
27 of loglevels exist and are accessed with a similar syntax:
28 <code class="filename">bbfatal</code>, <code class="filename">bberror</code>,
29 <code class="filename">bbwarn</code>, <code class="filename">bbnote</code>,
30 <code class="filename">bbplain</code>, and <code class="filename">bbdebug</code>.</p></li>
31</ul></div>
32<p>
33 </p>
34<p>
35 For guidance on how logging is handled in both Python and Bash recipes, see the
36 <code class="filename">logging.bbclass</code> file in the
37 <code class="filename">meta/classes</code> folder of the
38 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
39 </p>
40</div></body>
41</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-commandline.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-commandline.html
deleted file mode 100644
index 34c8394c3f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-commandline.html
+++ /dev/null
@@ -1,79 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.6. BitBake Command Line</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake-runtask.html" title="6.5. Running a Task">
10<link rel="next" href="ref-bitbake-fetchers.html" title="6.7. Fetchers">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.6. BitBake Command Line">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-commandline"></a>6.6. BitBake Command Line</h2></div></div></div>
15<p>
16 Following is the BitBake help output:
17 </p>
18<pre class="screen">
19$ bitbake --help
20Usage: bitbake [options] [package ...]
21
22Executes the specified task (default is 'build') for a given set of BitBake files.
23It expects that BBFILES is defined, which is a space separated list of files to
24be executed. BBFILES does support wildcards.
25Default BBFILES are the .bb files in the current directory.
26
27Options:
28 --version show program's version number and exit
29 -h, --help show this help message and exit
30 -b BUILDFILE, --buildfile=BUILDFILE
31 execute the task against this .bb file, rather than a
32 package from BBFILES. Does not handle any
33 dependencies.
34 -k, --continue continue as much as possible after an error. While the
35 target that failed, and those that depend on it,
36 cannot be remade, the other dependencies of these
37 targets can be processed all the same.
38 -a, --tryaltconfigs continue with builds by trying to use alternative
39 providers where possible.
40 -f, --force force run of specified cmd, regardless of stamp status
41 -c CMD, --cmd=CMD Specify task to execute. Note that this only executes
42 the specified task for the providee and the packages
43 it depends on, i.e. 'compile' does not implicitly call
44 stage for the dependencies (IOW: use only if you know
45 what you are doing). Depending on the base.bbclass a
46 listtasks tasks is defined and will show available
47 tasks
48 -r PREFILE, --read=PREFILE
49 read the specified file before bitbake.conf
50 -R POSTFILE, --postread=POSTFILE
51 read the specified file after bitbake.conf
52 -v, --verbose output more chit-chat to the terminal
53 -D, --debug Increase the debug level. You can specify this more
54 than once.
55 -n, --dry-run don't execute, just go through the motions
56 -S, --dump-signatures
57 don't execute, just dump out the signature
58 construction information
59 -p, --parse-only quit after parsing the BB files (developers only)
60 -s, --show-versions show current and preferred versions of all packages
61 -e, --environment show the global or per-package environment (this is
62 what used to be bbread)
63 -g, --graphviz emit the dependency trees of the specified packages in
64 the dot syntax
65 -I EXTRA_ASSUME_PROVIDED, --ignore-deps=EXTRA_ASSUME_PROVIDED
66 Assume these dependencies don't exist and are already
67 provided (equivalent to ASSUME_PROVIDED). Useful to
68 make dependency graphs more appealing
69 -l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS
70 Show debug logging for the specified logging domains
71 -P, --profile profile the command and print a report
72 -u UI, --ui=UI userinterface to use
73 -t SERVERTYPE, --servertype=SERVERTYPE
74 Choose which server to use, none, process or xmlrpc
75 --revisions-changed Set the exit code depending on whether upstream
76 floating revisions have changed or not
77 </pre>
78</div></body>
79</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-dependencies.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-dependencies.html
deleted file mode 100644
index e7106ca6d2..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-dependencies.html
+++ /dev/null
@@ -1,34 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.3. Dependencies</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake-providers.html" title="6.2. Preferences and Providers">
10<link rel="next" href="ref-bitbake-tasklist.html" title="6.4. The Task List">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.3. Dependencies">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-dependencies"></a>6.3. Dependencies</h2></div></div></div>
15<p>
16 Each target BitBake builds consists of multiple tasks such as
17 <code class="filename">fetch</code>, <code class="filename">unpack</code>,
18 <code class="filename">patch</code>, <code class="filename">configure</code>,
19 and <code class="filename">compile</code>.
20 For best performance on multi-core systems, BitBake considers each task as an independent
21 entity with its own set of dependencies.
22 </p>
23<p>
24 Dependencies are defined through several variables.
25 You can find information about variables BitBake uses in the BitBake documentation,
26 which is found in the <code class="filename">bitbake/doc/manual</code> directory within the
27 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
28 At a basic level, it is sufficient to know that BitBake uses the
29 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEPENDS" title="DEPENDS">DEPENDS</a></code> and
30 <code class="filename"><a class="link" href="ref-variables-glos.html#var-RDEPENDS" title="RDEPENDS">RDEPENDS</a></code> variables when
31 calculating dependencies.
32 </p>
33</div></body>
34</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-fetchers.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-fetchers.html
deleted file mode 100644
index e1bda8b995..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-fetchers.html
+++ /dev/null
@@ -1,43 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.7. Fetchers</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake-commandline.html" title="6.6. BitBake Command Line">
10<link rel="next" href="ref-classes.html" title="Chapter 7. Classes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.7. Fetchers">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-fetchers"></a>6.7. Fetchers</h2></div></div></div>
15<p>
16 BitBake also contains a set of "fetcher" modules that allow
17 retrieval of source code from various types of sources.
18 For example, BitBake can get source code from a disk with the metadata, from websites,
19 from remote shell accounts or from Source Code Management (SCM) systems
20 like <code class="filename">cvs/subversion/git</code>.
21 </p>
22<p>
23 Fetchers are usually triggered by entries in
24 <code class="filename"><a class="link" href="ref-variables-glos.html#var-SRC_URI" title="SRC_URI">SRC_URI</a></code>.
25 You can find information about the options and formats of entries for specific
26 fetchers in the BitBake manual located in the
27 <code class="filename">bitbake/doc/manual</code> directory of the
28 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
29 </p>
30<p>
31 One useful feature for certain Source Code Manager (SCM) fetchers is the ability to
32 "auto-update" when the upstream SCM changes version.
33 Since this ability requires certain functionality from the SCM, not all
34 systems support it.
35 Currently Subversion, Bazaar and to a limited extent, Git support the ability to "auto-update".
36 This feature works using the <code class="filename"><a class="link" href="ref-variables-glos.html#var-SRCREV" title="SRCREV">SRCREV</a></code>
37 variable.
38 See the
39 "<a class="link" href="../dev-manual/platdev-appdev-srcrev.html" target="_self">Using an External SCM</a>" section
40 in the Yocto Project Development Manual for more information.
41 </p>
42</div></body>
43</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-parsing.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-parsing.html
deleted file mode 100644
index c86621eb38..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-parsing.html
+++ /dev/null
@@ -1,93 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.1. Parsing</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake.html" title="Chapter 6. BitBake">
10<link rel="next" href="ref-bitbake-providers.html" title="6.2. Preferences and Providers">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.1. Parsing">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-parsing"></a>6.1. Parsing</h2></div></div></div>
15<p>
16 BitBake parses configuration files, classes, and <code class="filename">.bb</code> files.
17 </p>
18<p>
19 The first thing BitBake does is look for the <code class="filename">bitbake.conf</code> file.
20 This file resides in the
21 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>
22 within the <code class="filename">meta/conf/</code> directory.
23 BitBake finds it by examining its
24 <a class="link" href="ref-variables-glos.html#var-BBPATH" title="BBPATH"><code class="filename">BBPATH</code></a> environment
25 variable and looking for the <code class="filename">meta/conf/</code>
26 directory.
27 </p>
28<p>
29 The <code class="filename">bitbake.conf</code> file lists other configuration
30 files to include from a <code class="filename">conf/</code>
31 directory below the directories listed in <code class="filename">BBPATH</code>.
32 In general, the most important configuration file from a user's perspective
33 is <code class="filename">local.conf</code>, which contains a user's customized
34 settings for the OpenEmbedded build environment.
35 Other notable configuration files are the distribution
36 configuration file (set by the
37 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO" title="DISTRO">DISTRO</a></code> variable)
38 and the machine configuration file
39 (set by the
40 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE">MACHINE</a></code> variable).
41 The <code class="filename">DISTRO</code> and <code class="filename">MACHINE</code> BitBake environment
42 variables are both usually set in
43 the <code class="filename">local.conf</code> file.
44 Valid distribution
45 configuration files are available in the <code class="filename">meta/conf/distro/</code> directory
46 and valid machine configuration
47 files in the <code class="filename">meta/conf/machine/</code> directory.
48 Within the <code class="filename">meta/conf/machine/include/</code>
49 directory are various <code class="filename">tune-*.inc</code> configuration files that provide common
50 "tuning" settings specific to and shared between particular architectures and machines.
51 </p>
52<p>
53 After the parsing of the configuration files, some standard classes are included.
54 The <code class="filename">base.bbclass</code> file is always included.
55 Other classes that are specified in the configuration using the
56 <code class="filename"><a class="link" href="ref-variables-glos.html#var-INHERIT" title="INHERIT">INHERIT</a></code>
57 variable are also included.
58 Class files are searched for in a <code class="filename">classes</code> subdirectory
59 under the paths in <code class="filename">BBPATH</code> in the same way as
60 configuration files.
61 </p>
62<p>
63 After classes are included, the variable
64 <code class="filename"><a class="link" href="ref-variables-glos.html#var-BBFILES" title="BBFILES">BBFILES</a></code>
65 is set, usually in
66 <code class="filename">local.conf</code>, and defines the list of places to search for
67 <code class="filename">.bb</code> files.
68 By default, the <code class="filename">BBFILES</code> variable specifies the
69 <code class="filename">meta/recipes-*/</code> directory within Poky.
70 Adding extra content to <code class="filename">BBFILES</code> is best achieved through the use of
71 BitBake layers as described in the
72 "<a class="link" href="../dev-manual/understanding-and-creating-layers.html" target="_self">Understanding and
73 Creating Layers</a>" section of the Yocto Project Development Manual.
74 </p>
75<p>
76 BitBake parses each <code class="filename">.bb</code> file in <code class="filename">BBFILES</code> and
77 stores the values of various variables.
78 In summary, for each <code class="filename">.bb</code>
79 file the configuration plus the base class of variables are set, followed
80 by the data in the <code class="filename">.bb</code> file
81 itself, followed by any inherit commands that
82 <code class="filename">.bb</code> file might contain.
83 </p>
84<p>
85 Because parsing <code class="filename">.bb</code> files is a time
86 consuming process, a cache is kept to speed up subsequent parsing.
87 This cache is invalid if the timestamp of the <code class="filename">.bb</code>
88 file itself changes, or if the timestamps of any of the include,
89 configuration or class files the <code class="filename">.bb</code>
90 file depends on changes.
91 </p>
92</div></body>
93</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html
deleted file mode 100644
index 37d34a0e70..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-providers.html
+++ /dev/null
@@ -1,63 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.2. Preferences and Providers</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake-parsing.html" title="6.1. Parsing">
10<link rel="next" href="ref-bitbake-dependencies.html" title="6.3. Dependencies">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.2. Preferences and Providers">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-providers"></a>6.2. Preferences and Providers</h2></div></div></div>
15<p>
16 Once all the <code class="filename">.bb</code> files have been
17 parsed, BitBake starts to build the target (<code class="filename">core-image-sato</code>
18 in the previous section's example) and looks for providers of that target.
19 Once a provider is selected, BitBake resolves all the dependencies for
20 the target.
21 In the case of <code class="filename">core-image-sato</code>, it would lead to
22 <code class="filename">packagegroup-core-x11-sato</code>,
23 which in turn leads to recipes like <code class="filename">matchbox-terminal</code>,
24 <code class="filename">pcmanfm</code> and <code class="filename">gthumb</code>.
25 These recipes in turn depend on <code class="filename">eglibc</code> and the toolchain.
26 </p>
27<p>
28 Sometimes a target might have multiple providers.
29 A common example is "virtual/kernel", which is provided by each kernel package.
30 Each machine often selects the best kernel provider by using a line similar to the
31 following in the machine configuration file:
32 </p>
33<pre class="literallayout">
34 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
35 </pre>
36<p>
37 The default <code class="filename"><a class="link" href="ref-variables-glos.html#var-PREFERRED_PROVIDER" title="PREFERRED_PROVIDER">PREFERRED_PROVIDER</a></code>
38 is the provider with the same name as the target.
39 </p>
40<p>
41 Understanding how providers are chosen is made complicated by the fact
42 that multiple versions might exist.
43 BitBake defaults to the highest version of a provider.
44 Version comparisons are made using the same method as Debian.
45 You can use the
46 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PREFERRED_VERSION" title="PREFERRED_VERSION">PREFERRED_VERSION</a></code>
47 variable to specify a particular version (usually in the distro configuration).
48 You can influence the order by using the
49 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEFAULT_PREFERENCE" title="DEFAULT_PREFERENCE">DEFAULT_PREFERENCE</a></code>
50 variable.
51 By default, files have a preference of "0".
52 Setting the <code class="filename">DEFAULT_PREFERENCE</code> to "-1" makes the
53 package unlikely to be used unless it is explicitly referenced.
54 Setting the <code class="filename">DEFAULT_PREFERENCE</code> to "1" makes it likely the package is used.
55 <code class="filename">PREFERRED_VERSION</code> overrides any <code class="filename">DEFAULT_PREFERENCE</code> setting.
56 <code class="filename">DEFAULT_PREFERENCE</code> is often used to mark newer and more experimental package
57 versions until they have undergone sufficient testing to be considered stable.
58 </p>
59<p>
60 In summary, BitBake has created a list of providers, which is prioritized, for each target.
61 </p>
62</div></body>
63</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-runtask.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-runtask.html
deleted file mode 100644
index f653e30561..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-runtask.html
+++ /dev/null
@@ -1,86 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.5. Running a Task</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake-tasklist.html" title="6.4. The Task List">
10<link rel="next" href="ref-bitbake-commandline.html" title="6.6. BitBake Command Line">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.5. Running a Task">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-runtask"></a>6.5. Running a Task</h2></div></div></div>
15<p>
16 Tasks can either be a shell task or a Python task.
17 For shell tasks, BitBake writes a shell script to
18 <code class="filename">${WORKDIR}/temp/run.do_taskname.pid</code> and then executes the script.
19 The generated shell script contains all the exported variables, and the shell functions
20 with all variables expanded.
21 Output from the shell script goes to the file <code class="filename">${WORKDIR}/temp/log.do_taskname.pid</code>.
22 Looking at the expanded shell functions in the run file and the output in the log files
23 is a useful debugging technique.
24 </p>
25<p>
26 For Python tasks, BitBake executes the task internally and logs information to the
27 controlling terminal.
28 Future versions of BitBake will write the functions to files similar to the way
29 shell tasks are handled.
30 Logging will be handled in way similar to shell tasks as well.
31 </p>
32<p>
33 Once all the tasks have been completed BitBake exits.
34 </p>
35<p>
36 When running a task, BitBake tightly controls the execution environment
37 of the build tasks to make sure unwanted contamination from the build machine
38 cannot influence the build.
39 Consequently, if you do want something to get passed into the build
40 task's environment, you must take a few steps:
41 </p>
42<div class="orderedlist"><ol class="orderedlist" type="1">
43<li class="listitem">
44<p>Tell BitBake to load what you want from the environment
45 into the data store.
46 You can do so through the <code class="filename">BB_ENV_EXTRAWHITE</code>
47 variable.
48 For example, assume you want to prevent the build system from
49 accessing your <code class="filename">$HOME/.ccache</code> directory.
50 The following command tells BitBake to load
51 <code class="filename">CCACHE_DIR</code> from the environment into the data
52 store:
53 </p>
54<pre class="literallayout">
55 export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE CCACHE_DIR"
56 </pre>
57</li>
58<li class="listitem">
59<p>Tell BitBake to export what you have loaded into the
60 environment store to the task environment of every running task.
61 Loading something from the environment into the data store
62 (previous step) only makes it available in the datastore.
63 To export it to the task environment of every running task,
64 use a command similar to the following in your
65 <code class="filename">local.conf</code> or distro configuration file:
66 </p>
67<pre class="literallayout">
68 export CCACHE_DIR
69 </pre>
70</li>
71</ol></div>
72<p>
73 </p>
74<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
75<h3 class="title">Note</h3>
76 A side effect of the previous steps is that BitBake records the variable
77 as a dependency of the build process in things like the shared state
78 checksums.
79 If doing so results in unnecessary rebuilds of tasks, you can whitelist the
80 variable so that the shared state code ignores the dependency when it creates
81 checksums.
82 For information on this process, see the <code class="filename">BB_HASHBASE_WHITELIST</code>
83 example in the "<a class="link" href="checksums.html" title="3.2.2. Checksums (Signatures)">Checksums (Signatures)</a>" section.
84 </div>
85</div></body>
86</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html
deleted file mode 100644
index fedbcca285..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake-tasklist.html
+++ /dev/null
@@ -1,54 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>6.4. The Task List</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-bitbake.html" title="Chapter 6. BitBake">
9<link rel="prev" href="ref-bitbake-dependencies.html" title="6.3. Dependencies">
10<link rel="next" href="ref-bitbake-runtask.html" title="6.5. Running a Task">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="6.4. The Task List">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-bitbake-tasklist"></a>6.4. The Task List</h2></div></div></div>
15<p>
16 Based on the generated list of providers and the dependency information,
17 BitBake can now calculate exactly what tasks it needs to run and in what
18 order it needs to run them.
19 The build now starts with BitBake forking off threads up to the limit set in the
20 <code class="filename"><a class="link" href="ref-variables-glos.html#var-BB_NUMBER_THREADS" title="BB_NUMBER_THREADS">BB_NUMBER_THREADS</a></code> variable.
21 BitBake continues to fork threads as long as there are tasks ready to run,
22 those tasks have all their dependencies met, and the thread threshold has not been
23 exceeded.
24 </p>
25<p>
26 It is worth noting that you can greatly speed up the build time by properly setting
27 the <code class="filename">BB_NUMBER_THREADS</code> variable.
28 See the
29 "<a class="link" href="../yocto-project-qs/building-image.html" target="_self">Building an Image</a>"
30 section in the Yocto Project Quick Start for more information.
31 </p>
32<p>
33 As each task completes, a timestamp is written to the directory specified by the
34 <code class="filename"><a class="link" href="ref-variables-glos.html#var-STAMP" title="STAMP">STAMP</a></code> variable (usually
35 <code class="filename">build/tmp/stamps/*/</code>).
36 On subsequent runs, BitBake looks at the <code class="filename">/build/tmp/stamps</code>
37 directory and does not rerun
38 tasks that are already completed unless a timestamp is found to be invalid.
39 Currently, invalid timestamps are only considered on a per
40 <code class="filename">.bb</code> file basis.
41 So, for example, if the configure stamp has a timestamp greater than the
42 compile timestamp for a given target, then the compile task would rerun.
43 Running the compile task again, however, has no effect on other providers
44 that depend on that target.
45 This behavior could change or become configurable in future versions of BitBake.
46 </p>
47<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
48<h3 class="title">Note</h3>
49 Some tasks are marked as "nostamp" tasks.
50 No timestamp file is created when these tasks are run.
51 Consequently, "nostamp" tasks are always rerun.
52 </div>
53</div></body>
54</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake.html
deleted file mode 100644
index c724158b6e..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-bitbake.html
+++ /dev/null
@@ -1,48 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 6. BitBake</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="structure-meta-recipes-txt.html" title="5.3.19. meta/recipes.txt">
10<link rel="next" href="ref-bitbake-parsing.html" title="6.1. Parsing">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 6. BitBake">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-bitbake"></a>Chapter 6. BitBake</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="ref-bitbake-parsing.html">6.1. Parsing</a></span></dt>
19<dt><span class="section"><a href="ref-bitbake-providers.html">6.2. Preferences and Providers</a></span></dt>
20<dt><span class="section"><a href="ref-bitbake-dependencies.html">6.3. Dependencies</a></span></dt>
21<dt><span class="section"><a href="ref-bitbake-tasklist.html">6.4. The Task List</a></span></dt>
22<dt><span class="section"><a href="ref-bitbake-runtask.html">6.5. Running a Task</a></span></dt>
23<dt><span class="section"><a href="ref-bitbake-commandline.html">6.6. BitBake Command Line</a></span></dt>
24<dt><span class="section"><a href="ref-bitbake-fetchers.html">6.7. Fetchers</a></span></dt>
25</dl>
26</div>
27<p>
28 BitBake is a program written in Python that interprets the metadata used by the OpenEmbedded
29 build system.
30 At some point, developers wonder what actually happens when you enter:
31 </p>
32<pre class="literallayout">
33 $ bitbake core-image-sato
34 </pre>
35<p>
36 </p>
37<p>
38 This chapter provides an overview of what happens behind the scenes from BitBake's perspective.
39 </p>
40<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
41<h3 class="title">Note</h3>
42 BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships.
43 As such, it has no real knowledge of what the tasks being executed actually do.
44 BitBake just considers a list of tasks with dependencies and handles metadata
45 that consists of variables in a certain format that get passed to the tasks.
46 </div>
47</div></body>
48</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-autotools.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-autotools.html
deleted file mode 100644
index 36ae47a158..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-autotools.html
+++ /dev/null
@@ -1,52 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.2. Autotooled Packages - autotools.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-base.html" title="7.1. The base class - base.bbclass">
10<link rel="next" href="ref-classes-update-alternatives.html" title="7.3. Alternatives - update-alternatives.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.2. Autotooled Packages - autotools.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-autotools"></a>7.2. Autotooled Packages - <code class="filename">autotools.bbclass</code>
15</h2></div></div></div>
16<p>
17 Autotools (<code class="filename">autoconf</code>, <code class="filename">automake</code>,
18 and <code class="filename">libtool</code>) bring standardization.
19 This class defines a set of tasks (configure, compile etc.) that
20 work for all Autotooled packages.
21 It should usually be enough to define a few standard variables
22 and then simply <code class="filename">inherit autotools</code>.
23 This class can also work with software that emulates Autotools.
24 For more information, see the
25 "<a class="link" href="../dev-manual/usingpoky-extend-addpkg-autotools.html" target="_self">Autotooled Package</a>"
26 section in the Yocto Project Development Manual.
27 </p>
28<p>
29 It's useful to have some idea of how the tasks defined by this class work
30 and what they do behind the scenes.
31 </p>
32<div class="itemizedlist"><ul class="itemizedlist" type="disc">
33<li class="listitem"><p><code class="filename">do_configure</code> &#8208; regenerates the
34 configure script (using <code class="filename">autoreconf</code>) and then launches it
35 with a standard set of arguments used during cross-compilation.
36 You can pass additional parameters to <code class="filename">configure</code> through the
37 <code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OECONF" title="EXTRA_OECONF">EXTRA_OECONF</a></code> variable.
38 </p></li>
39<li class="listitem"><p><code class="filename">do_compile</code> &#8208; runs <code class="filename">make</code> with
40 arguments that specify the compiler and linker.
41 You can pass additional arguments through
42 the <code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OEMAKE" title="EXTRA_OEMAKE">EXTRA_OEMAKE</a></code> variable.
43 </p></li>
44<li class="listitem"><p><code class="filename">do_install</code> &#8208; runs <code class="filename">make install</code>
45 and passes a DESTDIR option, which takes its value from the standard
46 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DESTDIR" title="DESTDIR">DESTDIR</a></code> variable.
47 </p></li>
48</ul></div>
49<p>
50 </p>
51</div></body>
52</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-base.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-base.html
deleted file mode 100644
index a10285bf40..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-base.html
+++ /dev/null
@@ -1,28 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.1. The base class - base.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes.html" title="Chapter 7. Classes">
10<link rel="next" href="ref-classes-autotools.html" title="7.2. Autotooled Packages - autotools.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.1. The base class - base.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-base"></a>7.1. The base class - <code class="filename">base.bbclass</code>
15</h2></div></div></div>
16<p>
17 The base class is special in that every <code class="filename">.bb</code>
18 file inherits it automatically.
19 This class contains definitions for standard basic
20 tasks such as fetching, unpacking, configuring (empty by default), compiling
21 (runs any <code class="filename">Makefile</code> present), installing (empty by default) and packaging
22 (empty by default).
23 These classes are often overridden or extended by other classes
24 such as <code class="filename">autotools.bbclass</code> or <code class="filename">package.bbclass</code>.
25 The class also contains some commonly used functions such as <code class="filename">oe_runmake</code>.
26 </p>
27</div></body>
28</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-binconfig.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-binconfig.html
deleted file mode 100644
index bbf035e950..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-binconfig.html
+++ /dev/null
@@ -1,30 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.5. Binary config scripts - binconfig.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-update-rc.d.html" title="7.4. Initscripts - update-rc.d.bbclass">
10<link rel="next" href="ref-classes-debian.html" title="7.6. Debian renaming - debian.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.5. Binary config scripts - binconfig.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-binconfig"></a>7.5. Binary config scripts - <code class="filename">binconfig.bbclass</code>
15</h2></div></div></div>
16<p>
17 Before <code class="filename">pkg-config</code> had become widespread, libraries shipped shell
18 scripts to give information about the libraries and include paths needed
19 to build software (usually named <code class="filename">LIBNAME-config</code>).
20 This class assists any recipe using such scripts.
21 </p>
22<p>
23 During staging, BitBake installs such scripts into the
24 <code class="filename">sysroots/</code> directory.
25 BitBake also changes all paths to point into the <code class="filename">sysroots/</code>
26 directory so all builds that use the script will use the correct
27 directories for the cross compiling layout.
28 </p>
29</div></body>
30</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-debian.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-debian.html
deleted file mode 100644
index 9d37cbb716..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-debian.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.6. Debian renaming - debian.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-binconfig.html" title="7.5. Binary config scripts - binconfig.bbclass">
10<link rel="next" href="ref-classes-pkgconfig.html" title="7.7. Pkg-config - pkgconfig.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.6. Debian renaming - debian.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-debian"></a>7.6. Debian renaming - <code class="filename">debian.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class renames packages so that they follow the Debian naming
18 policy (i.e. <code class="filename">eglibc</code> becomes <code class="filename">libc6</code>
19 and <code class="filename">eglibc-devel</code> becomes <code class="filename">libc6-dev</code>.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-devshell.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-devshell.html
deleted file mode 100644
index cbbcc4c4c6..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-devshell.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.11. Developer Shell - devshell.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-distutils.html" title="7.10. Python extensions - distutils.bbclass">
10<link rel="next" href="ref-classes-packagegroup.html" title="7.12. Package Groups - packagegroup.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.11. Developer Shell - devshell.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-devshell"></a>7.11. Developer Shell - <code class="filename">devshell.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class adds the <code class="filename">devshell</code> task.
18 Distribution policy dictates whether to include this class.
19 See the
20 "<a class="link" href="../dev-manual/platdev-appdev-devshell.html" target="_self">Using a Development Shell</a>" section
21 in the Yocto Project Development Manual for more information about using <code class="filename">devshell</code>.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-distutils.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-distutils.html
deleted file mode 100644
index d176cb8dc1..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-distutils.html
+++ /dev/null
@@ -1,31 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.10. Python extensions - distutils.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-perl.html" title="7.9. Perl modules - cpan.bbclass">
10<link rel="next" href="ref-classes-devshell.html" title="7.11. Developer Shell - devshell.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.10. Python extensions - distutils.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-distutils"></a>7.10. Python extensions - <code class="filename">distutils.bbclass</code>
15</h2></div></div></div>
16<p>
17 Recipes for Python extensions are simple.
18 These recipes usually only need to point to the source's archive and then inherit
19 the proper <code class="filename">.bbclass</code> file.
20 Building is split into two methods dependling on which method the module authors used.
21 </p>
22<p>
23 Extensions that use an Autotools-based build system require Autotools and
24 <code class="filename">distutils</code>-based <code class="filename">.bbclasse</code> files in their recipes.
25 </p>
26<p>
27 Extensions that use <code class="filename">distutils</code>-based build systems require
28 <code class="filename">distutils.bbclass</code> in their recipes.
29 </p>
30</div></body>
31</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-externalsrc.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-externalsrc.html
deleted file mode 100644
index ead3708607..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-externalsrc.html
+++ /dev/null
@@ -1,72 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.20. Using External Source - externalsrc.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-useradd.html" title="7.19. Adding Users - useradd.bbclass">
10<link rel="next" href="ref-classes-others.html" title="7.21. Other Classes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.20. Using External Source - externalsrc.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-externalsrc"></a>7.20. Using External Source - <code class="filename">externalsrc.bbclass</code>
15</h2></div></div></div>
16<p>
17 You can use this class to build software from source code that is external to the
18 OpenEmbedded build system.
19 In other words, your source code resides in an external tree outside of the Yocto Project.
20 Building software from an external source tree means that the normal fetch, unpack, and
21 patch process is not used.
22 </p>
23<p>
24 To use the class, you need to define the
25 <a class="link" href="ref-variables-glos.html#var-S" title="S"><code class="filename">S</code></a> variable to point to the directory that contains the source files.
26 You also need to have your recipe inherit the <code class="filename">externalsrc.bbclass</code> class.
27 </p>
28<p>
29 This class expects the source code to support recipe builds that use the
30 <a class="link" href="ref-variables-glos.html#var-B" title="B"><code class="filename">B</code></a> variable to point to the directory in
31 which the OpenEmbedded build system places the generated objects built from the recipes.
32 By default, the <code class="filename">B</code> directory is set to the following, which is separate from the
33 Source Directory (<code class="filename">S</code>):
34 </p>
35<pre class="literallayout">
36 ${WORKDIR}/${BPN}-{PV}/
37 </pre>
38<p>
39 See the glossary entries for the
40 <a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR"><code class="filename">WORKDIR</code></a>,
41 <a class="link" href="ref-variables-glos.html#var-BPN" title="BPN"><code class="filename">BPN</code></a>,
42 <a class="link" href="ref-variables-glos.html#var-PV" title="PV"><code class="filename">PV</code></a>,
43 <a class="link" href="ref-variables-glos.html#var-S" title="S"><code class="filename">S</code></a>, and
44 <a class="link" href="ref-variables-glos.html#var-B" title="B"><code class="filename">B</code></a> for more information.
45 </p>
46<p>
47 You can build object files in the external tree by setting the
48 <code class="filename">B</code> variable equal to <code class="filename">"${S}"</code>.
49 However, this practice does not work well if you use the source for more than one variant
50 (i.e., "natives" such as <code class="filename">quilt-native</code>,
51 or "crosses" such as <code class="filename">gcc-cross</code>).
52 So, be sure there are no "native", "cross", or "multilib" variants of the recipe.
53 </p>
54<p>
55 If you do want to build different variants of a recipe, you can use the
56 <a class="link" href="ref-variables-glos.html#var-BBCLASSEXTEND" title="BBCLASSEXTEND"><code class="filename">BBCLASSEXTEND</code></a> variable.
57 When you do, the <a class="link" href="ref-variables-glos.html#var-B" title="B"><code class="filename">B</code></a> variable must support the
58 recipe's ability to build variants in different working directories.
59 Most autotools-based recipes support separating these directories.
60 The OpenEmbedded build system defaults to using separate directories for <code class="filename">gcc</code>
61 and some kernel recipes.
62 Alternatively, you can make sure that separate recipes exist that each
63 use the <code class="filename">BBCLASSEXTEND</code> variable to build each variant.
64 The separate recipes can inherit a single target recipe.
65 </p>
66<p>
67 For information on how to use this class, see the
68 "<a class="link" href="../dev-manual/building-software-from-an-external-source.html" target="_self">Building
69 Software from an External Source</a>" section in the Yocto Project Development Manual.
70 </p>
71</div></body>
72</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-image.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-image.html
deleted file mode 100644
index a8453e97b9..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-image.html
+++ /dev/null
@@ -1,31 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.15. Creating images - image.bbclass and rootfs*.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-kernel.html" title="7.14. Building kernels - kernel.bbclass">
10<link rel="next" href="ref-classes-sanity.html" title="7.16. Host System sanity checks - sanity.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.15. Creating images - image.bbclass and rootfs*.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-image"></a>7.15. Creating images - <code class="filename">image.bbclass</code> and <code class="filename">rootfs*.bbclass</code>
15</h2></div></div></div>
16<p>
17 These classes add support for creating images in several formats.
18 First, the root filesystem is created from packages using
19 one of the <code class="filename">rootfs_*.bbclass</code>
20 files (depending on the package format used) and then the image is created.
21 </p>
22<p>
23 The <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FSTYPES" title="IMAGE_FSTYPES">IMAGE_FSTYPES</a></code>
24 variable controls the types of images to generate.
25 </p>
26<p>
27 The <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_INSTALL" title="IMAGE_INSTALL">IMAGE_INSTALL</a></code>
28 variable controls the list of packages to install into the image.
29 </p>
30</div></body>
31</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-insane.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-insane.html
deleted file mode 100644
index 1cdf589cff..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-insane.html
+++ /dev/null
@@ -1,105 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.17. Generated output quality assurance checks - insane.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-sanity.html" title="7.16. Host System sanity checks - sanity.bbclass">
10<link rel="next" href="ref-classes-siteinfo.html" title="7.18. Autotools configuration data cache - siteinfo.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.17. Generated output quality assurance checks - insane.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-insane"></a>7.17. Generated output quality assurance checks - <code class="filename">insane.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class adds a step to the package generation process that sanity checks the
18 packages generated by the OpenEmbedded build system.
19 A range of checks are performed that check the build's output
20 for common problems that show up during runtime.
21 Distribution policy usually dictates whether to include this class.
22 </p>
23<p>
24 You can configure the sanity checks so that specific test failures either raise a warning or
25 an error message.
26 Typically, failures for new tests generate a warning.
27 Subsequent failures for the same test would then generate an error message
28 once the metadata is in a known and good condition.
29 You use the <code class="filename">WARN_QA</code> variable to specify tests for which you
30 want to generate a warning message on failure.
31 You use the <code class="filename">ERROR_QA</code> variable to specify tests for which you
32 want to generate an error message on failure.
33 </p>
34<p>
35 The following list shows the tests you can list with the <code class="filename">WARN_QA</code>
36 and <code class="filename">ERROR_QA</code> variables:
37 </p>
38<div class="itemizedlist"><ul class="itemizedlist" type="disc">
39<li class="listitem"><p><span class="emphasis"><em><code class="filename">ldflags:</code></em></span>
40 Ensures that the binaries were linked with the
41 <code class="filename">LDFLAGS</code> options provided by the build system.
42 If this test fails, check that the <code class="filename">LDFLAGS</code> variable
43 is being passed to the linker command.</p></li>
44<li class="listitem"><p><span class="emphasis"><em><code class="filename">useless-rpaths:</code></em></span>
45 Checks for dynamic library load paths (rpaths) in the binaries that
46 by default on a standard system are searched by the linker (e.g.
47 <code class="filename">/lib</code> and <code class="filename">/usr/lib</code>).
48 While these paths will not cause any breakage, they do waste space and
49 are unnecessary.</p></li>
50<li class="listitem"><p><span class="emphasis"><em><code class="filename">rpaths:</code></em></span>
51 Checks for rpaths in the binaries that contain build system paths such
52 as <code class="filename">TMPDIR</code>.
53 If this test fails, bad <code class="filename">-rpath</code> options are being
54 passed to the linker commands and your binaries have potential security
55 issues.</p></li>
56<li class="listitem"><p><span class="emphasis"><em><code class="filename">dev-so:</code></em></span>
57 Checks that the <code class="filename">.so</code> symbolic links are in the
58 <code class="filename">-dev</code> package and not in any of the other packages.
59 In general, these symlinks are only useful for development purposes.
60 Thus, the <code class="filename">-dev</code> package is the correct location for
61 them.
62 Some very rare cases do exist for dynamically loaded modules where
63 these symlinks are needed instead in the main package.
64 </p></li>
65<li class="listitem"><p><span class="emphasis"><em><code class="filename">debug-files:</code></em></span>
66 Checks for <code class="filename">.debug</code> directories in anything but the
67 <code class="filename">-dbg</code> package.
68 The debug files should all be in the <code class="filename">-dbg</code> package.
69 Thus, anything packaged elsewhere is incorrect packaging.</p></li>
70<li class="listitem"><p><span class="emphasis"><em><code class="filename">arch:</code></em></span>
71 Checks the Executable and Linkable Format (ELF) type, bit size and endianness
72 of any binaries to ensure it matches the target architecture.
73 This test fails if any binaries don't match the type since there would be an
74 incompatibility.
75 Sometimes software, like bootloaders, might need to bypass this check.
76 </p></li>
77<li class="listitem"><p><span class="emphasis"><em><code class="filename">debug-deps:</code></em></span>
78 Checks that <code class="filename">-dbg</code> packages only depend on other
79 <code class="filename">-dbg</code> packages and not on any other types of packages,
80 which would cause a packaging bug.</p></li>
81<li class="listitem"><p><span class="emphasis"><em><code class="filename">dev-deps:</code></em></span>
82 Checks that <code class="filename">-dev</code> packages only depend on other
83 <code class="filename">-dev</code> packages and not on any other types of packages,
84 which would be a packaging bug.</p></li>
85<li class="listitem"><p><span class="emphasis"><em><code class="filename">pkgconfig:</code></em></span>
86 Checks <code class="filename">.pc</code> files for any
87 <code class="filename">TMPDIR/WORKDIR</code> paths.
88 Any <code class="filename">.pc</code> file containing these paths is incorrect
89 since <code class="filename">pkg-config</code> itself adds the correct sysroot prefix
90 when the files are accessed.</p></li>
91<li class="listitem"><p><span class="emphasis"><em><code class="filename">la:</code></em></span>
92 Checks <code class="filename">.la</code> files for any <code class="filename">TMPDIR</code>
93 paths.
94 Any <code class="filename">.la</code> file continaing these paths is incorrect since
95 <code class="filename">libtool</code> adds the correct sysroot prefix when using the
96 files automatically itself.</p></li>
97<li class="listitem"><p><span class="emphasis"><em><code class="filename">desktop:</code></em></span>
98 Runs the <code class="filename">desktop-file-validate</code> program against any
99 <code class="filename">.desktop</code> files to validate their contents against
100 the specification for <code class="filename">.desktop</code> files.</p></li>
101</ul></div>
102<p>
103 </p>
104</div></body>
105</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-kernel.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-kernel.html
deleted file mode 100644
index 72afff8226..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-kernel.html
+++ /dev/null
@@ -1,36 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.14. Building kernels - kernel.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-package.html" title="7.13. Packaging - package*.bbclass">
10<link rel="next" href="ref-classes-image.html" title="7.15. Creating images - image.bbclass and rootfs*.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.14. Building kernels - kernel.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-kernel"></a>7.14. Building kernels - <code class="filename">kernel.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class handles building Linux kernels.
18 The class contains code to build all kernel trees.
19 All needed headers are staged into the
20 <code class="filename"><a class="link" href="ref-variables-glos.html#var-STAGING_KERNEL_DIR" title="STAGING_KERNEL_DIR">STAGING_KERNEL_DIR</a></code>
21 directory to allow out-of-tree module builds using <code class="filename">module.bbclass</code>.
22 </p>
23<p>
24 This means that each built kernel module is packaged separately and inter-module
25 dependencies are created by parsing the <code class="filename">modinfo</code> output.
26 If all modules are required, then installing the <code class="filename">kernel-modules</code>
27 package installs all packages with modules and various other kernel packages
28 such as <code class="filename">kernel-vmlinux</code>.
29 </p>
30<p>
31 Various other classes are used by the kernel and module classes internally including
32 <code class="filename">kernel-arch.bbclass</code>, <code class="filename">module_strip.bbclass</code>,
33 <code class="filename">module-base.bbclass</code>, and <code class="filename">linux-kernel-base.bbclass</code>.
34 </p>
35</div></body>
36</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-others.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-others.html
deleted file mode 100644
index cafdb13b11..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-others.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.21. Other Classes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-externalsrc.html" title="7.20. Using External Source - externalsrc.bbclass">
10<link rel="next" href="ref-images.html" title="Chapter 8. Images">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.21. Other Classes">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-others"></a>7.21. Other Classes</h2></div></div></div>
15<p>
16 Thus far, this chapter has discussed only the most useful and important
17 classes.
18 However, other classes exist within the <code class="filename">meta/classes</code> directory
19 in the <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
20 You can examine the <code class="filename">.bbclass</code> files directly for more
21 information.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html
deleted file mode 100644
index eb43660f9e..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html
+++ /dev/null
@@ -1,73 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.13. Packaging - package*.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-packagegroup.html" title="7.12. Package Groups - packagegroup.bbclass">
10<link rel="next" href="ref-classes-kernel.html" title="7.14. Building kernels - kernel.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.13. Packaging - package*.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-package"></a>7.13. Packaging - <code class="filename">package*.bbclass</code>
15</h2></div></div></div>
16<p>
17 The packaging classes add support for generating packages from a build's
18 output.
19 The core generic functionality is in <code class="filename">package.bbclass</code>.
20 The code specific to particular package types is contained in various sub-classes such as
21 <code class="filename">package_deb.bbclass</code>, <code class="filename">package_ipk.bbclass</code>,
22 and <code class="filename">package_rpm.bbclass</code>.
23 Most users will want one or more of these classes.
24 </p>
25<p>
26 You can control the list of resulting package formats by using the
27 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_CLASSES" title="PACKAGE_CLASSES">PACKAGE_CLASSES</a></code>
28 variable defined in the <code class="filename">local.conf</code> configuration file,
29 which is located in the <code class="filename">conf</code> folder of the
30 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
31 When defining the variable, you can specify one or more package types.
32 Since images are generated from packages, a packaging class is
33 needed to enable image generation.
34 The first class listed in this variable is used for image generation.
35 </p>
36<p>
37 The package class you choose can affect build-time performance and has space
38 ramifications.
39 In general, building a package with RPM takes about thirty percent more time as
40 compared to using IPK to build the same or similar package.
41 This comparison takes into account a complete build of the package with all
42 dependencies previously built.
43 The reason for this discrepancy is because the RPM package manager creates and
44 processes more metadata than the IPK package manager.
45 Consequently, you might consider setting <code class="filename">PACKAGE_CLASSES</code>
46 to "package_ipk" if you are building smaller systems.
47 </p>
48<p>
49 Keep in mind, however, that RPM starts to provide more abilities than IPK due to
50 the fact that it processes more metadata.
51 For example, this information includes individual file types, file checksum generation
52 and evaluation on install, sparse file support, conflict detection and resolution
53 for multilib systems, ACID style upgrade, and repackaging abilities for rollbacks.
54 </p>
55<p>
56 Another consideration for packages built using the RPM package manager is space.
57 For smaller systems, the extra space used for the Berkley Database and the amount
58 of metadata can affect your ability to do on-device upgrades.
59 </p>
60<p>
61 You can find additional information on the effects of the package class at these
62 two Yocto Project mailing list links:
63 </p>
64<div class="itemizedlist"><ul class="itemizedlist" type="disc">
65<li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html" target="_self">
66 https://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html</a></p></li>
67<li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/pipermail/poky/2011-May/006363.html" target="_self">
68 https://lists.yoctoproject.org/pipermail/poky/2011-May/006363.html</a></p></li>
69</ul></div>
70<p>
71 </p>
72</div></body>
73</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-packagegroup.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-packagegroup.html
deleted file mode 100644
index 96944339aa..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-packagegroup.html
+++ /dev/null
@@ -1,33 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.12. Package Groups - packagegroup.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-devshell.html" title="7.11. Developer Shell - devshell.bbclass">
10<link rel="next" href="ref-classes-package.html" title="7.13. Packaging - package*.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.12. Package Groups - packagegroup.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-packagegroup"></a>7.12. Package Groups - <code class="filename">packagegroup.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class sets default values appropriate for package group recipes (such as
18 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGES" title="PACKAGES">PACKAGES</a></code>,
19 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_ARCH" title="PACKAGE_ARCH">PACKAGE_ARCH</a></code>,
20 <code class="filename"><a class="link" href="ref-variables-glos.html#var-ALLOW_EMPTY" title="ALLOW_EMPTY">ALLOW_EMPTY</a></code>,
21 and so forth.
22 It is highly recommended that all package group recipes inherit this class.
23 </p>
24<p>
25 For information on how to use this class, see the
26 "<a class="link" href="../dev-manual/usingpoky-extend-customimage-customtasks.html" target="_self">Customizing Images Using Custom Package Tasks</a>"
27 section in the Yocto Project Development Manual.
28 </p>
29<p>
30 Previously, this class was named <code class="filename">task.bbclass</code>.
31 </p>
32</div></body>
33</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-perl.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-perl.html
deleted file mode 100644
index b4be9b4da0..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-perl.html
+++ /dev/null
@@ -1,31 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.9. Perl modules - cpan.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-src-distribute.html" title="7.8. Distribution of sources - src_distribute_local.bbclass">
10<link rel="next" href="ref-classes-distutils.html" title="7.10. Python extensions - distutils.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.9. Perl modules - cpan.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-perl"></a>7.9. Perl modules - <code class="filename">cpan.bbclass</code>
15</h2></div></div></div>
16<p>
17 Recipes for Perl modules are simple.
18 These recipes usually only need to point to the source's archive and then inherit the
19 proper <code class="filename">.bbclass</code> file.
20 Building is split into two methods depending on which method the module authors used.
21 </p>
22<p>
23 Modules that use old <code class="filename">Makefile.PL</code>-based build system require
24 <code class="filename">cpan.bbclass</code> in their recipes.
25 </p>
26<p>
27 Modules that use <code class="filename">Build.PL</code>-based build system require
28 using <code class="filename">cpan_build.bbclass</code> in their recipes.
29 </p>
30</div></body>
31</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-pkgconfig.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-pkgconfig.html
deleted file mode 100644
index 09566fd328..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-pkgconfig.html
+++ /dev/null
@@ -1,27 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.7. Pkg-config - pkgconfig.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-debian.html" title="7.6. Debian renaming - debian.bbclass">
10<link rel="next" href="ref-classes-src-distribute.html" title="7.8. Distribution of sources - src_distribute_local.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.7. Pkg-config - pkgconfig.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-pkgconfig"></a>7.7. Pkg-config - <code class="filename">pkgconfig.bbclass</code>
15</h2></div></div></div>
16<p>
17 <code class="filename">pkg-config</code> brought standardization and this class aims to make its
18 integration smooth for all libraries that make use of it.
19 </p>
20<p>
21 During staging, BitBake installs <code class="filename">pkg-config</code> data into the
22 <code class="filename">sysroots/</code> directory.
23 By making use of sysroot functionality within <code class="filename">pkg-config</code>,
24 this class no longer has to manipulate the files.
25 </p>
26</div></body>
27</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-sanity.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-sanity.html
deleted file mode 100644
index 0e3a19a76a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-sanity.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.16. Host System sanity checks - sanity.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-image.html" title="7.15. Creating images - image.bbclass and rootfs*.bbclass">
10<link rel="next" href="ref-classes-insane.html" title="7.17. Generated output quality assurance checks - insane.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.16. Host System sanity checks - sanity.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-sanity"></a>7.16. Host System sanity checks - <code class="filename">sanity.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class checks to see if prerequisite software is present so that
18 users can be notified of potential problems that might affect their build.
19 The class also performs basic user configuration checks from
20 the <code class="filename">local.conf</code> configuration file to
21 prevent common mistakes that cause build failures.
22 Distribution policy usually determines whether to include this class.
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-siteinfo.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-siteinfo.html
deleted file mode 100644
index 878794d201..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-siteinfo.html
+++ /dev/null
@@ -1,39 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.18. Autotools configuration data cache - siteinfo.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-insane.html" title="7.17. Generated output quality assurance checks - insane.bbclass">
10<link rel="next" href="ref-classes-useradd.html" title="7.19. Adding Users - useradd.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.18. Autotools configuration data cache - siteinfo.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-siteinfo"></a>7.18. Autotools configuration data cache - <code class="filename">siteinfo.bbclass</code>
15</h2></div></div></div>
16<p>
17 Autotools can require tests that must execute on the target hardware.
18 Since this is not possible in general when cross compiling, site information is
19 used to provide cached test results so these tests can be skipped over but
20 still make the correct values available.
21 The <code class="filename"><a class="link" href="structure-meta-site.html" title="5.3.18. meta/site/">meta/site directory</a></code>
22 contains test results sorted into different categories such as architecture, endianness, and
23 the <code class="filename">libc</code> used.
24 Site information provides a list of files containing data relevant to
25 the current build in the
26 <code class="filename"><a class="link" href="ref-variables-glos.html#var-CONFIG_SITE" title="CONFIG_SITE">CONFIG_SITE</a></code> variable
27 that Autotools automatically picks up.
28 </p>
29<p>
30 The class also provides variables like
31 <code class="filename"><a class="link" href="ref-variables-glos.html#var-SITEINFO_ENDIANNESS" title="SITEINFO_ENDIANNESS">SITEINFO_ENDIANNESS</a></code>
32 and <code class="filename"><a class="link" href="ref-variables-glos.html#var-SITEINFO_BITS" title="SITEINFO_BITS">SITEINFO_BITS</a></code>
33 that can be used elsewhere in the metadata.
34 </p>
35<p>
36 Because this class is included from <code class="filename">base.bbclass</code>, it is always active.
37 </p>
38</div></body>
39</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-src-distribute.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-src-distribute.html
deleted file mode 100644
index a1bbb8b415..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-src-distribute.html
+++ /dev/null
@@ -1,43 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.8. Distribution of sources - src_distribute_local.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-pkgconfig.html" title="7.7. Pkg-config - pkgconfig.bbclass">
10<link rel="next" href="ref-classes-perl.html" title="7.9. Perl modules - cpan.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.8. Distribution of sources - src_distribute_local.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-src-distribute"></a>7.8. Distribution of sources - <code class="filename">src_distribute_local.bbclass</code>
15</h2></div></div></div>
16<p>
17 Many software licenses require that source files be provided along with the binaries.
18 To simplify this process, two classes were created:
19 <code class="filename">src_distribute.bbclass</code> and
20 <code class="filename">src_distribute_local.bbclass</code>.
21 </p>
22<p>
23 The results of these classes are <code class="filename">tmp/deploy/source/</code>
24 subdirs with sources sorted by
25 <code class="filename"><a class="link" href="ref-variables-glos.html#var-LICENSE" title="LICENSE">LICENSE</a></code> field.
26 If recipes list few licenses (or have entries like "Bitstream Vera"),
27 the source archive is placed in each license directory.
28 </p>
29<p>
30 This class operates using three modes:
31 </p>
32<div class="itemizedlist"><ul class="itemizedlist" type="disc">
33<li class="listitem"><p><span class="emphasis"><em>copy:</em></span> Copies the files to the
34 distribute directory.</p></li>
35<li class="listitem"><p><span class="emphasis"><em>symlink:</em></span> Symlinks the files to the
36 distribute directory.</p></li>
37<li class="listitem"><p><span class="emphasis"><em>move+symlink:</em></span> Moves the files into
38 the distribute directory and then symlinks them back.</p></li>
39</ul></div>
40<p>
41 </p>
42</div></body>
43</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-alternatives.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-alternatives.html
deleted file mode 100644
index cb6dfac6c4..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-alternatives.html
+++ /dev/null
@@ -1,48 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.3. Alternatives - update-alternatives.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-autotools.html" title="7.2. Autotooled Packages - autotools.bbclass">
10<link rel="next" href="ref-classes-update-rc.d.html" title="7.4. Initscripts - update-rc.d.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.3. Alternatives - update-alternatives.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-update-alternatives"></a>7.3. Alternatives - <code class="filename">update-alternatives.bbclass</code>
15</h2></div></div></div>
16<p>
17 Several programs can fulfill the same or similar function and be installed with the same name.
18 For example, the <code class="filename">ar</code> command is available from the
19 <code class="filename">busybox</code>, <code class="filename">binutils</code> and
20 <code class="filename">elfutils</code> packages.
21 The <code class="filename">update-alternatives.bbclass</code> class handles renaming the
22 binaries so that multiple packages can be installed without conflicts.
23 The <code class="filename">ar</code> command still works regardless of which packages are installed
24 or subsequently removed.
25 The class renames the conflicting binary in each package and symlinks the highest
26 priority binary during installation or removal of packages.
27 </p>
28<p>
29 Four variables control this class:
30 </p>
31<div class="itemizedlist"><ul class="itemizedlist" type="disc">
32<li class="listitem"><p><code class="filename">ALTERNATIVE_NAME</code> &#8208; The name of the
33 binary that is replaced (<code class="filename">ar</code> in this example).</p></li>
34<li class="listitem"><p><code class="filename">ALTERNATIVE_LINK</code> &#8208; The path to
35 the resulting binary (<code class="filename">/bin/ar</code> in this example).</p></li>
36<li class="listitem"><p><code class="filename">ALTERNATIVE_PATH</code> &#8208; The path to the
37 real binary (<code class="filename">/usr/bin/ar.binutils</code> in this example).</p></li>
38<li class="listitem"><p><code class="filename">ALTERNATIVE_PRIORITY</code> &#8208; The priority of
39 the binary.
40 The version with the most features should have the highest priority.</p></li>
41</ul></div>
42<p>
43 </p>
44<p>
45 Currently, the OpenEmbedded build system supports only one binary per package.
46 </p>
47</div></body>
48</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-rc.d.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-rc.d.html
deleted file mode 100644
index 7ab1688c3b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-update-rc.d.html
+++ /dev/null
@@ -1,28 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.4. Initscripts - update-rc.d.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-update-alternatives.html" title="7.3. Alternatives - update-alternatives.bbclass">
10<link rel="next" href="ref-classes-binconfig.html" title="7.5. Binary config scripts - binconfig.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.4. Initscripts - update-rc.d.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-update-rc.d"></a>7.4. Initscripts - <code class="filename">update-rc.d.bbclass</code>
15</h2></div></div></div>
16<p>
17 This class uses <code class="filename">update-rc.d</code> to safely install an
18 initialization script on behalf of the package.
19 The OpenEmbedded build system takes care of details such as making sure the script is stopped before
20 a package is removed and started when the package is installed.
21 Three variables control this class:
22 <code class="filename"><a class="link" href="ref-variables-glos.html#var-INITSCRIPT_PACKAGES" title="INITSCRIPT_PACKAGES">INITSCRIPT_PACKAGES</a></code>,
23 <code class="filename"><a class="link" href="ref-variables-glos.html#var-INITSCRIPT_NAME" title="INITSCRIPT_NAME">INITSCRIPT_NAME</a></code> and
24 <code class="filename"><a class="link" href="ref-variables-glos.html#var-INITSCRIPT_PARAMS" title="INITSCRIPT_PARAMS">INITSCRIPT_PARAMS</a></code>.
25 See the variable links for details.
26 </p>
27</div></body>
28</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-useradd.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-useradd.html
deleted file mode 100644
index cc78211aab..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-useradd.html
+++ /dev/null
@@ -1,28 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>7.19. Adding Users - useradd.bbclass</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-classes.html" title="Chapter 7. Classes">
9<link rel="prev" href="ref-classes-siteinfo.html" title="7.18. Autotools configuration data cache - siteinfo.bbclass">
10<link rel="next" href="ref-classes-externalsrc.html" title="7.20. Using External Source - externalsrc.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.19. Adding Users - useradd.bbclass">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-classes-useradd"></a>7.19. Adding Users - <code class="filename">useradd.bbclass</code>
15</h2></div></div></div>
16<p>
17 If you have packages that install files that are owned by custom users or groups,
18 you can use this class to specify those packages and associate the users and groups
19 with those packages.
20 The <code class="filename">meta-skeleton/recipes-skeleton/useradd/useradd-example.bb</code>
21 recipe in the <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>
22 provides a simple exmample that shows how to add three
23 users and groups to two packages.
24 See the <code class="filename">useradd-example.bb</code> for more information on how to
25 use this class.
26 </p>
27</div></body>
28</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes.html
deleted file mode 100644
index 35cc535e70..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes.html
+++ /dev/null
@@ -1,61 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 7. Classes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="ref-bitbake-fetchers.html" title="6.7. Fetchers">
10<link rel="next" href="ref-classes-base.html" title="7.1. The base class - base.bbclass">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 7. Classes">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-classes"></a>Chapter 7. Classes</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="ref-classes-base.html">7.1. The base class - <code class="filename">base.bbclass</code></a></span></dt>
19<dt><span class="section"><a href="ref-classes-autotools.html">7.2. Autotooled Packages - <code class="filename">autotools.bbclass</code></a></span></dt>
20<dt><span class="section"><a href="ref-classes-update-alternatives.html">7.3. Alternatives - <code class="filename">update-alternatives.bbclass</code></a></span></dt>
21<dt><span class="section"><a href="ref-classes-update-rc.d.html">7.4. Initscripts - <code class="filename">update-rc.d.bbclass</code></a></span></dt>
22<dt><span class="section"><a href="ref-classes-binconfig.html">7.5. Binary config scripts - <code class="filename">binconfig.bbclass</code></a></span></dt>
23<dt><span class="section"><a href="ref-classes-debian.html">7.6. Debian renaming - <code class="filename">debian.bbclass</code></a></span></dt>
24<dt><span class="section"><a href="ref-classes-pkgconfig.html">7.7. Pkg-config - <code class="filename">pkgconfig.bbclass</code></a></span></dt>
25<dt><span class="section"><a href="ref-classes-src-distribute.html">7.8. Distribution of sources - <code class="filename">src_distribute_local.bbclass</code></a></span></dt>
26<dt><span class="section"><a href="ref-classes-perl.html">7.9. Perl modules - <code class="filename">cpan.bbclass</code></a></span></dt>
27<dt><span class="section"><a href="ref-classes-distutils.html">7.10. Python extensions - <code class="filename">distutils.bbclass</code></a></span></dt>
28<dt><span class="section"><a href="ref-classes-devshell.html">7.11. Developer Shell - <code class="filename">devshell.bbclass</code></a></span></dt>
29<dt><span class="section"><a href="ref-classes-packagegroup.html">7.12. Package Groups - <code class="filename">packagegroup.bbclass</code></a></span></dt>
30<dt><span class="section"><a href="ref-classes-package.html">7.13. Packaging - <code class="filename">package*.bbclass</code></a></span></dt>
31<dt><span class="section"><a href="ref-classes-kernel.html">7.14. Building kernels - <code class="filename">kernel.bbclass</code></a></span></dt>
32<dt><span class="section"><a href="ref-classes-image.html">7.15. Creating images - <code class="filename">image.bbclass</code> and <code class="filename">rootfs*.bbclass</code></a></span></dt>
33<dt><span class="section"><a href="ref-classes-sanity.html">7.16. Host System sanity checks - <code class="filename">sanity.bbclass</code></a></span></dt>
34<dt><span class="section"><a href="ref-classes-insane.html">7.17. Generated output quality assurance checks - <code class="filename">insane.bbclass</code></a></span></dt>
35<dt><span class="section"><a href="ref-classes-siteinfo.html">7.18. Autotools configuration data cache - <code class="filename">siteinfo.bbclass</code></a></span></dt>
36<dt><span class="section"><a href="ref-classes-useradd.html">7.19. Adding Users - <code class="filename">useradd.bbclass</code></a></span></dt>
37<dt><span class="section"><a href="ref-classes-externalsrc.html">7.20. Using External Source - <code class="filename">externalsrc.bbclass</code></a></span></dt>
38<dt><span class="section"><a href="ref-classes-others.html">7.21. Other Classes</a></span></dt>
39</dl>
40</div>
41<p>
42 Class files are used to abstract common functionality and share it amongst multiple
43 <code class="filename">.bb</code> files.
44 Any metadata usually found in a <code class="filename">.bb</code> file can also be placed in a class
45 file.
46 Class files are identified by the extension <code class="filename">.bbclass</code> and are usually placed
47 in a <code class="filename">classes/</code> directory beneath the
48 <code class="filename">meta*/</code> directory found in the
49 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
50 Class files can also be pointed to by BUILDDIR (e.g. <code class="filename">build/</code>)in the same way as
51 <code class="filename">.conf</code> files in the <code class="filename">conf</code> directory.
52 Class files are searched for in <a class="link" href="ref-variables-glos.html#var-BBPATH" title="BBPATH"><code class="filename">BBPATH</code></a>
53 using the same method by which <code class="filename">.conf</code> files are searched.
54</p>
55<p>
56 In most cases inheriting the class is enough to enable its features, although
57 for some classes you might need to set variables or override some of the
58 default behaviour.
59</p>
60</div></body>
61</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-backfill.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-backfill.html
deleted file mode 100644
index 0ad90dfd70..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-backfill.html
+++ /dev/null
@@ -1,88 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>9.4. Feature Backfilling</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-features.html" title="Chapter 9. Reference: Features">
9<link rel="prev" href="ref-features-image.html" title="9.3. Images">
10<link rel="next" href="ref-variables-glos.html" title="Chapter 10. Variables Glossary">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="9.4. Feature Backfilling">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-features-backfill"></a>9.4. Feature Backfilling</h2></div></div></div>
15<p>
16 Sometimes it is necessary in the OpenEmbedded build system to extend
17 <a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES"><code class="filename">MACHINE_FEATURES</code></a>
18 or <a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES" title="DISTRO_FEATURES"><code class="filename">DISTRO_FEATURES</code></a>
19 to control functionality that was previously enabled and not able
20 to be disabled.
21 For these cases, we need to add an
22 additional feature item to appear in one of these variables,
23 but we do not want to force developers who have existing values
24 of the variables in their configuration to add the new feature
25 in order to retain the same overall level of functionality.
26 Thus, the OpenEmbedded build system has a mechanism to
27 automatically "backfill" these added features into existing
28 distro or machine configurations.
29 You can see the list of features for which this is done by
30 finding the
31 <a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES_BACKFILL" title="DISTRO_FEATURES_BACKFILL"><code class="filename">DISTRO_FEATURES_BACKFILL</code></a>
32 and <a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES_BACKFILL" title="MACHINE_FEATURES_BACKFILL"><code class="filename">MACHINE_FEATURES_BACKFILL</code></a>
33 variables in the <code class="filename">meta/conf/bitbake.conf</code> file.
34 </p>
35<p>
36 Because such features are backfilled by default into all
37 configurations as described in the previous paragraph, developers
38 who wish to disable the new features need to be able to selectively
39 prevent the backfilling from occurring.
40 They can do this by adding the undesired feature or features to the
41 <a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES_BACKFILL_CONSIDERED" title="DISTRO_FEATURES_BACKFILL_CONSIDERED"><code class="filename">DISTRO_FEATURES_BACKFILL_CONSIDERED</code></a>
42 or <a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES_BACKFILL_CONSIDERED" title="MACHINE_FEATURES_BACKFILL_CONSIDERED"><code class="filename">MACHINE_FEATURES_BACKFILL_CONSIDERED</code></a>
43 variables for distro features and machine features respectively.
44 </p>
45<p>
46 Here are two examples to help illustrate feature backfilling:
47 </p>
48<div class="itemizedlist"><ul class="itemizedlist" type="disc">
49<li class="listitem"><p><span class="emphasis"><em>The "pulseaudio" distro feature option</em></span>:
50 Previously, PulseAudio support was enabled within the Qt and
51 GStreamer frameworks.
52 Because of this, the feature is backfilled and thus
53 enabled for all distros through the
54 <code class="filename">DISTRO_FEATURES_BACKFILL</code>
55 variable in the <code class="filename">meta/conf/bitbake.conf</code> file.
56 However, your distro needs to disable the feature.
57 You can disable the feature without affecting
58 other existing distro configurations that need PulseAudio support
59 by adding "pulseaudio" to
60 <code class="filename">DISTRO_FEATURES_BACKFILL_CONSIDERED</code>
61 in your distro's <code class="filename">.conf</code> file.
62 Adding the feature to this variable when it also
63 exists in the <code class="filename">DISTRO_FEATURES_BACKFILL</code>
64 variable prevents the build system from adding the feature to
65 your configuration's <code class="filename">DISTRO_FEATURES</code>, effectively disabling
66 the feature for that particular distro.</p></li>
67<li class="listitem"><p><span class="emphasis"><em>The "rtc" machine feature option</em></span>:
68 Previously, real time clock (RTC) support was enabled for all
69 target devices.
70 Because of this, the feature is backfilled and thus enabled
71 for all machines through the <code class="filename">MACHINE_FEATURES_BACKFILL</code>
72 variable in the <code class="filename">meta/conf/bitbake.conf</code> file.
73 However, your target device does not have this capability.
74 You can disable RTC support for your device without
75 affecting other machines that need RTC support
76 by adding the feature to your machine's
77 <code class="filename">MACHINE_FEATURES_BACKFILL_CONSIDERED</code>
78 list in the machine's <code class="filename">.conf</code> file.
79 Adding the feature to this variable when it also
80 exists in the <code class="filename">MACHINE_FEATURES_BACKFILL</code>
81 variable prevents the build system from adding the feature to
82 your configuration's <code class="filename">MACHINE_FEATURES</code>, effectively
83 disabling RTC support for that particular machine.</p></li>
84</ul></div>
85<p>
86 </p>
87</div></body>
88</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-distro.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-distro.html
deleted file mode 100644
index d261858123..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-distro.html
+++ /dev/null
@@ -1,68 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>9.1. Distro</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-features.html" title="Chapter 9. Reference: Features">
9<link rel="prev" href="ref-features.html" title="Chapter 9. Reference: Features">
10<link rel="next" href="ref-features-machine.html" title="9.2. Machine">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="9.1. Distro">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-features-distro"></a>9.1. Distro</h2></div></div></div>
15<p>
16 The items below are features you can use with
17 <a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES" title="DISTRO_FEATURES"><code class="filename">DISTRO_FEATURES</code></a>.
18 Features do not have a one-to-one correspondence to packages, and they can
19 go beyond simply controlling the installation of a package or packages.
20 Sometimes a feature can influence how certain recipes are built.
21 For example, a feature might determine whether a particular configure option
22 is specified within <code class="filename">do_configure</code> for a particular
23 recipe.
24 </p>
25<p>
26 This list only represents features as shipped with the Yocto Project metadata:
27 </p>
28<div class="itemizedlist"><ul class="itemizedlist" type="disc">
29<li class="listitem"><p><span class="emphasis"><em>alsa:</em></span> ALSA support will be included (OSS compatibility
30 kernel modules will be installed if available).</p></li>
31<li class="listitem"><p><span class="emphasis"><em>bluetooth:</em></span> Include bluetooth support (integrated BT only)
32 </p></li>
33<li class="listitem"><p><span class="emphasis"><em>ext2:</em></span> Include tools for supporting for devices with internal
34 HDD/Microdrive for storing files (instead of Flash only devices)
35 </p></li>
36<li class="listitem"><p><span class="emphasis"><em>irda:</em></span> Include Irda support
37 </p></li>
38<li class="listitem"><p><span class="emphasis"><em>keyboard:</em></span> Include keyboard support (e.g. keymaps will be
39 loaded during boot).
40 </p></li>
41<li class="listitem"><p><span class="emphasis"><em>pci:</em></span> Include PCI bus support
42 </p></li>
43<li class="listitem"><p><span class="emphasis"><em>pcmcia:</em></span> Include PCMCIA/CompactFlash support
44 </p></li>
45<li class="listitem"><p><span class="emphasis"><em>usbgadget:</em></span> USB Gadget Device support (for USB
46 networking/serial/storage)
47 </p></li>
48<li class="listitem"><p><span class="emphasis"><em>usbhost:</em></span> USB Host support (allows to connect external
49 keyboard, mouse, storage, network etc)
50 </p></li>
51<li class="listitem"><p><span class="emphasis"><em>wifi:</em></span> WiFi support (integrated only)
52 </p></li>
53<li class="listitem"><p><span class="emphasis"><em>cramfs:</em></span> CramFS support
54 </p></li>
55<li class="listitem"><p><span class="emphasis"><em>ipsec:</em></span> IPSec support
56 </p></li>
57<li class="listitem"><p><span class="emphasis"><em>ipv6:</em></span> IPv6 support
58 </p></li>
59<li class="listitem"><p><span class="emphasis"><em>nfs:</em></span> NFS client support (for mounting NFS exports on
60 device)</p></li>
61<li class="listitem"><p><span class="emphasis"><em>ppp:</em></span> PPP dialup support</p></li>
62<li class="listitem"><p><span class="emphasis"><em>smbfs:</em></span> SMB networks client support (for mounting
63 Samba/Microsoft Windows shares on device)</p></li>
64</ul></div>
65<p>
66 </p>
67</div></body>
68</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-image.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-image.html
deleted file mode 100644
index e705a2922f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-image.html
+++ /dev/null
@@ -1,73 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>9.3. Images</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-features.html" title="Chapter 9. Reference: Features">
9<link rel="prev" href="ref-features-machine.html" title="9.2. Machine">
10<link rel="next" href="ref-features-backfill.html" title="9.4. Feature Backfilling">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="9.3. Images">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-features-image"></a>9.3. Images</h2></div></div></div>
15<p>
16 The contents of images generated by the OpenEmbedded build system can be controlled by the
17 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FEATURES" title="IMAGE_FEATURES">IMAGE_FEATURES</a></code>
18 and <code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_IMAGE_FEATURES" title="EXTRA_IMAGE_FEATURES">EXTRA_IMAGE_FEATURES</a></code>
19 variables that you typically configure in your image recipes.
20 Through these variables you can add several different
21 predefined packages such as development utilities or packages with debug
22 information needed to investigate application problems or profile applications.
23 </p>
24<p>
25 Current list of
26 <code class="filename">IMAGE_FEATURES</code> contains the following:
27 </p>
28<div class="itemizedlist"><ul class="itemizedlist" type="disc">
29<li class="listitem"><p><span class="emphasis"><em>splash:</em></span> Enables showing a splash screen during boot.
30 By default, this screen is provided by <code class="filename">psplash</code>, which does
31 allow customization.
32 If you prefer to use an alternative splash screen package, you can do so by
33 setting the <code class="filename">SPLASH</code> variable
34 to a different package name (or names) within the image recipe or at the distro
35 configuration level.</p></li>
36<li class="listitem"><p><span class="emphasis"><em>ssh-server-dropbear:</em></span> Installs the Dropbear minimal
37 SSH server.
38 </p></li>
39<li class="listitem"><p><span class="emphasis"><em>ssh-server-openssh:</em></span> Installs the OpenSSH SSH server,
40 which is more full-featured than Dropbear.
41 Note that if both the OpenSSH SSH server and the Dropbear minimal SSH server
42 are present in <code class="filename">IMAGE_FEATURES</code>, then OpenSSH will take
43 precedence and Dropbear will not be installed.</p></li>
44<li class="listitem"><p><span class="emphasis"><em>x11:</em></span> Installs the X server</p></li>
45<li class="listitem"><p><span class="emphasis"><em>x11-base:</em></span> Installs the X server with a
46 minimal environment.</p></li>
47<li class="listitem"><p><span class="emphasis"><em>x11-sato:</em></span> Installs the OpenedHand Sato environment.
48 </p></li>
49<li class="listitem"><p><span class="emphasis"><em>tools-sdk:</em></span> Installs a full SDK that runs on the device.
50 </p></li>
51<li class="listitem"><p><span class="emphasis"><em>tools-debug:</em></span> Installs debugging tools such as
52 <code class="filename">strace</code> and <code class="filename">gdb</code>.
53 </p></li>
54<li class="listitem"><p><span class="emphasis"><em>tools-profile:</em></span> Installs profiling tools such as
55 <code class="filename">oprofile</code>, <code class="filename">exmap</code>, and
56 <code class="filename">LTTng</code>.</p></li>
57<li class="listitem"><p><span class="emphasis"><em>tools-testapps:</em></span> Installs device testing tools (e.g.
58 touchscreen debugging).</p></li>
59<li class="listitem"><p><span class="emphasis"><em>nfs-server:</em></span> Installs an NFS server.</p></li>
60<li class="listitem"><p><span class="emphasis"><em>dev-pkgs:</em></span> Installs development packages (headers and
61 extra library links) for all packages installed in a given image.</p></li>
62<li class="listitem"><p><span class="emphasis"><em>staticdev-pkgs:</em></span> Installs static development
63 packages (i.e. static libraries containing <code class="filename">*.a</code> files) for all
64 packages installed in a given image.</p></li>
65<li class="listitem"><p><span class="emphasis"><em>dbg-pkgs:</em></span> Installs debug symbol packages for all packages
66 installed in a given image.</p></li>
67<li class="listitem"><p><span class="emphasis"><em>doc-pkgs:</em></span> Installs documentation packages for all packages
68 installed in a given image.</p></li>
69</ul></div>
70<p>
71 </p>
72</div></body>
73</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-machine.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-machine.html
deleted file mode 100644
index 428aca3973..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features-machine.html
+++ /dev/null
@@ -1,63 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>9.2. Machine</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-features.html" title="Chapter 9. Reference: Features">
9<link rel="prev" href="ref-features-distro.html" title="9.1. Distro">
10<link rel="next" href="ref-features-image.html" title="9.3. Images">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="9.2. Machine">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-features-machine"></a>9.2. Machine</h2></div></div></div>
15<p>
16 The items below are features you can use with
17 <a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES"><code class="filename">MACHINE_FEATURES</code></a>.
18 Features do not have a one-to-one correspondence to packages, and they can
19 go beyond simply controlling the installation of a package or packages.
20 Sometimes a feature can influence how certain recipes are built.
21 For example, a feature might determine whether a particular configure option
22 is specified within <code class="filename">do_configure</code> for a particular
23 recipe.
24 </p>
25<p>
26 This feature list only represents features as shipped with the Yocto Project metadata:
27 </p>
28<div class="itemizedlist"><ul class="itemizedlist" type="disc">
29<li class="listitem"><p><span class="emphasis"><em>acpi:</em></span> Hardware has ACPI (x86/x86_64 only)
30 </p></li>
31<li class="listitem"><p><span class="emphasis"><em>alsa:</em></span> Hardware has ALSA audio drivers
32 </p></li>
33<li class="listitem"><p><span class="emphasis"><em>apm:</em></span> Hardware uses APM (or APM emulation)
34 </p></li>
35<li class="listitem"><p><span class="emphasis"><em>bluetooth:</em></span> Hardware has integrated BT
36 </p></li>
37<li class="listitem"><p><span class="emphasis"><em>ext2:</em></span> Hardware HDD or Microdrive
38 </p></li>
39<li class="listitem"><p><span class="emphasis"><em>irda:</em></span> Hardware has Irda support
40 </p></li>
41<li class="listitem"><p><span class="emphasis"><em>keyboard:</em></span> Hardware has a keyboard
42 </p></li>
43<li class="listitem"><p><span class="emphasis"><em>pci:</em></span> Hardware has a PCI bus
44 </p></li>
45<li class="listitem"><p><span class="emphasis"><em>pcmcia:</em></span> Hardware has PCMCIA or CompactFlash sockets
46 </p></li>
47<li class="listitem"><p><span class="emphasis"><em>screen:</em></span> Hardware has a screen
48 </p></li>
49<li class="listitem"><p><span class="emphasis"><em>serial:</em></span> Hardware has serial support (usually RS232)
50 </p></li>
51<li class="listitem"><p><span class="emphasis"><em>touchscreen:</em></span> Hardware has a touchscreen
52 </p></li>
53<li class="listitem"><p><span class="emphasis"><em>usbgadget:</em></span> Hardware is USB gadget device capable
54 </p></li>
55<li class="listitem"><p><span class="emphasis"><em>usbhost:</em></span> Hardware is USB Host capable
56 </p></li>
57<li class="listitem"><p><span class="emphasis"><em>wifi:</em></span> Hardware has integrated WiFi
58 </p></li>
59</ul></div>
60<p>
61 </p>
62</div></body>
63</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features.html
deleted file mode 100644
index c10c49cb19..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-features.html
+++ /dev/null
@@ -1,60 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 9. Reference: Features</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="ref-images.html" title="Chapter 8. Images">
10<link rel="next" href="ref-features-distro.html" title="9.1. Distro">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 9. Reference: Features">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-features"></a>Chapter 9. Reference: Features</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="ref-features-distro.html">9.1. Distro</a></span></dt>
19<dt><span class="section"><a href="ref-features-machine.html">9.2. Machine</a></span></dt>
20<dt><span class="section"><a href="ref-features-image.html">9.3. Images</a></span></dt>
21<dt><span class="section"><a href="ref-features-backfill.html">9.4. Feature Backfilling</a></span></dt>
22</dl>
23</div>
24<p>
25 Features provide a mechanism for working out which packages
26 should be included in the generated images.
27 Distributions can select which features they want to support through the
28 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES" title="DISTRO_FEATURES">DISTRO_FEATURES</a></code>
29 variable, which is set in the <code class="filename">poky.conf</code> distribution configuration file.
30 Machine features are set in the
31 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES">MACHINE_FEATURES</a></code>
32 variable, which is set in the machine configuration file and
33 specifies the hardware features for a given machine.
34 </p>
35<p>
36 These two variables combine to work out which kernel modules,
37 utilities, and other packages to include.
38 A given distribution can support a selected subset of features so some machine features might not
39 be included if the distribution itself does not support them.
40 </p>
41<p>
42 One method you can use to determine which recipes are checking to see if a
43 particular feature is contained or not is to <code class="filename">grep</code> through
44 the metadata for the feature.
45 Here is an example that discovers the recipes whose build is potentially
46 changed based on a given feature:
47 </p>
48<pre class="literallayout">
49 $ cd $HOME/poky
50 $ git grep 'contains.*MACHINE_FEATURES.*&lt;feature&gt;'
51 </pre>
52<p>
53 </p>
54<p>
55 This chapter provides a reference of shipped machine and distro features
56 you can include as part of the image, a reference on image types you can
57 build, and a reference on feature backfilling.
58 </p>
59</div></body>
60</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html
deleted file mode 100644
index 81ed4ba8f2..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-images.html
+++ /dev/null
@@ -1,137 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 8. Images</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="ref-classes-others.html" title="7.21. Other Classes">
10<link rel="next" href="ref-features.html" title="Chapter 9. Reference: Features">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 8. Images">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-images"></a>Chapter 8. Images</h2></div></div></div>
15<p>
16 The OpenEmbedded build process supports several types of images to satisfy different needs.
17 When you issue the <code class="filename">bitbake</code> command you provide a &#8220;top-level&#8221; recipe
18 that essentially begins the build for the type of image you want.
19 </p>
20<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
21<h3 class="title">Note</h3>
22 Building an image without GNU General Public License Version 3 (GPLv3) components
23 is only supported for minimal and base images.
24 Furthermore, if you are going to build an image using non-GPLv3 components,
25 you must make the following changes in the <code class="filename">local.conf</code> file
26 before using the BitBake command to build the minimal or base image:
27 <pre class="literallayout">
28 1. Comment out the EXTRA_IMAGE_FEATURES line
29 2. Set INCOMPATIBLE_LICENSE = "GPLv3"
30 </pre>
31</div>
32<p>
33 From within the <code class="filename">poky</code> Git repository, use the following command to list
34 the supported images:
35 </p>
36<pre class="literallayout">
37 $ ls meta*/recipes*/images/*.bb
38 </pre>
39<p>
40 These recipes reside in the <code class="filename">meta/recipes-core/images</code>,
41 <code class="filename">meta/recipes-extended/images</code>,
42 <code class="filename">meta/recipes-graphics/images</code>, and
43 <code class="filename">meta/recipes-sato/images</code> directories
44 within the <a class="link" href="../dev-manual/source-directory.html" target="_self">source directory</a>.
45 Although the recipe names are somewhat explanatory, here is a list that describes them:
46 </p>
47<div class="itemizedlist"><ul class="itemizedlist" type="disc">
48<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-base</code>:</em></span>
49 A console-only image that fully supports the target device hardware.</p></li>
50<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal</code>:</em></span>
51 A small image just capable of allowing a device to boot.</p></li>
52<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal-dev</code>:</em></span>
53 A <code class="filename">core-image-minimal</code> image suitable for development work
54 using the host.
55 The image includes headers and libraries you can use in a host development
56 environment.
57 </p></li>
58<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal-initramfs</code>:</em></span>
59 A <code class="filename">core-image-minimal</code> image that has the Minimal RAM-based
60 Initial Root Filesystem (<code class="filename">initramfs</code>) as part of the kernel,
61 which allows the system to find the first &#8220;init&#8221; program more efficiently.
62 </p></li>
63<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-minimal-mtdutils</code>:</em></span>
64 A <code class="filename">core-image-minimal</code> image that has support
65 for the Minimal MTD Utilities, which let the user interact with the
66 MTD subsystem in the kernel to perform operations on flash devices.
67 </p></li>
68<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-x11</code>:</em></span>
69 A very basic X11 image with a terminal.
70 </p></li>
71<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-basic</code>:</em></span>
72 A console-only image with more full-featured Linux system
73 functionality installed.</p></li>
74<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-lsb</code>:</em></span>
75 An image that conforms to the Linux Standard Base (LSB) specification.</p></li>
76<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-lsb-dev</code>:</em></span>
77 A <code class="filename">core-image-lsb</code> image that is suitable for development work
78 using the host.
79 The image includes headers and libraries you can use in a host development
80 environment.
81 </p></li>
82<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-lsb-sdk</code>:</em></span>
83 A <code class="filename">core-image-lsb</code> that includes everything in meta-toolchain
84 but also includes development headers and libraries to form a complete standalone SDK.
85 This image is suitable for development using the target.</p></li>
86<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-clutter</code>:</em></span>
87 An image with support for the Open GL-based toolkit Clutter, which enables development of
88 rich and animated graphical user interfaces.</p></li>
89<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-sato</code>:</em></span>
90 An image with Sato support, a mobile environment and visual style that works well
91 with mobile devices.
92 The image supports X11 with a Sato theme and applications such as
93 a terminal, editor, file manager, media player, and so forth.</p></li>
94<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-sato-dev</code>:</em></span>
95 A <code class="filename">core-image-sato</code> image suitable for development
96 using the host.
97 The image includes libraries needed to build applications on the device itself,
98 testing and profiling tools, and debug symbols.
99 This image was formerly <code class="filename">core-image-sdk</code>.</p></li>
100<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-sato-sdk</code>:</em></span>
101 A <code class="filename">core-image-sato</code> image that includes everything in meta-toolchain.
102 The image also includes development headers and libraries to form a complete standalone SDK
103 and is suitable for development using the target.</p></li>
104<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-rt</code>:</em></span>
105 A <code class="filename">core-image-minimal</code> image plus a real-time test suite and
106 tools appropriate for real-time use.</p></li>
107<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-rt-sdk</code>:</em></span>
108 A <code class="filename">core-image-rt</code> image that includes everything in
109 <code class="filename">meta-toolchain</code>.
110 The image also includes development headers and libraries to form a complete
111 stand-alone SDK and is suitable for development using the target.</p></li>
112<li class="listitem"><p><span class="emphasis"><em><code class="filename">core-image-gtk-directfb</code>:</em></span>
113 An image that uses <code class="filename">gtk+</code> over <code class="filename">directfb</code>
114 instead of X11.
115 In order to build, this image requires specific distro configuration that enables
116 <code class="filename">gtk</code> over <code class="filename">directfb</code>.</p></li>
117<li class="listitem"><p><span class="emphasis"><em><code class="filename">build-appliance-image</code>:</em></span>
118 An image you can boot and run using either the
119 <a class="ulink" href="http://www.vmware.com/products/player/overview.html" target="_self">VMware Player</a>
120 or <a class="ulink" href="http://www.vmware.com/products/workstation/overview.html" target="_self">VMware Workstation</a>.
121 For more information on this image, see the
122 <a class="ulink" href="http://www.yoctoproject.org/documentation/build-appliance" target="_self">Build Appliance</a> page on
123 the Yocto Project website.</p></li>
124</ul></div>
125<div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;">
126<h3 class="title">Tip</h3>
127 From the Yocto Project release 1.1 onwards, <code class="filename">-live</code> and
128 <code class="filename">-directdisk</code> images have been replaced by a "live"
129 option in <code class="filename">IMAGE_FSTYPES</code> that will work with any image to produce an
130 image file that can be
131 copied directly to a CD or USB device and run as is.
132 To build a live image, simply add
133 "live" to <code class="filename">IMAGE_FSTYPES</code> within the <code class="filename">local.conf</code>
134 file or wherever appropriate and then build the desired image as normal.
135 </div>
136</div></body>
137</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-structure.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-structure.html
deleted file mode 100644
index afc8334ebd..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-structure.html
+++ /dev/null
@@ -1,98 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 5. Source Directory Structure</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="migration-1.3-removed-recipes.html" title="4.1.2.6. Removed Recipes">
10<link rel="next" href="structure-core.html" title="5.1. Top level core components">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 5. Source Directory Structure">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-structure"></a>Chapter 5. Source Directory Structure</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="structure-core.html">5.1. Top level core components</a></span></dt>
19<dd><dl>
20<dt><span class="section"><a href="structure-core-bitbake.html">5.1.1. <code class="filename">bitbake/</code></a></span></dt>
21<dt><span class="section"><a href="structure-core-build.html">5.1.2. <code class="filename">build/</code></a></span></dt>
22<dt><span class="section"><a href="handbook.html">5.1.3. <code class="filename">documentation</code></a></span></dt>
23<dt><span class="section"><a href="structure-core-meta.html">5.1.4. <code class="filename">meta/</code></a></span></dt>
24<dt><span class="section"><a href="structure-core-meta-yocto.html">5.1.5. <code class="filename">meta-yocto/</code></a></span></dt>
25<dt><span class="section"><a href="structure-core-meta-yocto-bsp.html">5.1.6. <code class="filename">meta-yocto-bsp/</code></a></span></dt>
26<dt><span class="section"><a href="structure-meta-hob.html">5.1.7. <code class="filename">meta-hob/</code></a></span></dt>
27<dt><span class="section"><a href="structure-meta-skeleton.html">5.1.8. <code class="filename">meta-skeleton/</code></a></span></dt>
28<dt><span class="section"><a href="structure-core-scripts.html">5.1.9. <code class="filename">scripts/</code></a></span></dt>
29<dt><span class="section"><a href="structure-core-script.html">5.1.10. <code class="filename">oe-init-build-env</code></a></span></dt>
30<dt><span class="section"><a href="structure-basic-top-level.html">5.1.11. <code class="filename">LICENSE, README, and README.hardware</code></a></span></dt>
31</dl></dd>
32<dt><span class="section"><a href="structure-build.html">5.2. The Build Directory - <code class="filename">build/</code></a></span></dt>
33<dd><dl>
34<dt><span class="section"><a href="structure-build-pseudodone.html">5.2.1. <code class="filename">build/pseudodone</code></a></span></dt>
35<dt><span class="section"><a href="structure-build-conf-local.conf.html">5.2.2. <code class="filename">build/conf/local.conf</code></a></span></dt>
36<dt><span class="section"><a href="structure-build-conf-bblayers.conf.html">5.2.3. <code class="filename">build/conf/bblayers.conf</code></a></span></dt>
37<dt><span class="section"><a href="structure-build-conf-sanity_info.html">5.2.4. <code class="filename">build/conf/sanity_info</code></a></span></dt>
38<dt><span class="section"><a href="structure-build-downloads.html">5.2.5. <code class="filename">build/downloads/</code></a></span></dt>
39<dt><span class="section"><a href="structure-build-sstate-cache.html">5.2.6. <code class="filename">build/sstate-cache/</code></a></span></dt>
40<dt><span class="section"><a href="structure-build-tmp.html">5.2.7. <code class="filename">build/tmp/</code></a></span></dt>
41<dt><span class="section"><a href="structure-build-tmp-buildstats.html">5.2.8. <code class="filename">build/tmp/buildstats/</code></a></span></dt>
42<dt><span class="section"><a href="structure-build-tmp-cache.html">5.2.9. <code class="filename">build/tmp/cache/</code></a></span></dt>
43<dt><span class="section"><a href="structure-build-tmp-deploy.html">5.2.10. <code class="filename">build/tmp/deploy/</code></a></span></dt>
44<dt><span class="section"><a href="structure-build-tmp-deploy-deb.html">5.2.11. <code class="filename">build/tmp/deploy/deb/</code></a></span></dt>
45<dt><span class="section"><a href="structure-build-tmp-deploy-rpm.html">5.2.12. <code class="filename">build/tmp/deploy/rpm/</code></a></span></dt>
46<dt><span class="section"><a href="structure-build-tmp-deploy-licenses.html">5.2.13. <code class="filename">build/tmp/deploy/licenses/</code></a></span></dt>
47<dt><span class="section"><a href="structure-build-tmp-deploy-images.html">5.2.14. <code class="filename">build/tmp/deploy/images/</code></a></span></dt>
48<dt><span class="section"><a href="structure-build-tmp-deploy-ipk.html">5.2.15. <code class="filename">build/tmp/deploy/ipk/</code></a></span></dt>
49<dt><span class="section"><a href="structure-build-tmp-sysroots.html">5.2.16. <code class="filename">build/tmp/sysroots/</code></a></span></dt>
50<dt><span class="section"><a href="structure-build-tmp-stamps.html">5.2.17. <code class="filename">build/tmp/stamps/</code></a></span></dt>
51<dt><span class="section"><a href="structure-build-tmp-log.html">5.2.18. <code class="filename">build/tmp/log/</code></a></span></dt>
52<dt><span class="section"><a href="structure-build-tmp-pkgdata.html">5.2.19. <code class="filename">build/tmp/pkgdata/</code></a></span></dt>
53<dt><span class="section"><a href="structure-build-tmp-work.html">5.2.20. <code class="filename">build/tmp/work/</code></a></span></dt>
54</dl></dd>
55<dt><span class="section"><a href="structure-meta.html">5.3. The Metadata - <code class="filename">meta/</code></a></span></dt>
56<dd><dl>
57<dt><span class="section"><a href="structure-meta-classes.html">5.3.1. <code class="filename">meta/classes/</code></a></span></dt>
58<dt><span class="section"><a href="structure-meta-conf.html">5.3.2. <code class="filename">meta/conf/</code></a></span></dt>
59<dt><span class="section"><a href="structure-meta-conf-machine.html">5.3.3. <code class="filename">meta/conf/machine/</code></a></span></dt>
60<dt><span class="section"><a href="structure-meta-conf-distro.html">5.3.4. <code class="filename">meta/conf/distro/</code></a></span></dt>
61<dt><span class="section"><a href="structure-meta-recipes-bsp.html">5.3.5. <code class="filename">meta/recipes-bsp/</code></a></span></dt>
62<dt><span class="section"><a href="structure-meta-recipes-connectivity.html">5.3.6. <code class="filename">meta/recipes-connectivity/</code></a></span></dt>
63<dt><span class="section"><a href="structure-meta-recipes-core.html">5.3.7. <code class="filename">meta/recipes-core/</code></a></span></dt>
64<dt><span class="section"><a href="structure-meta-recipes-devtools.html">5.3.8. <code class="filename">meta/recipes-devtools/</code></a></span></dt>
65<dt><span class="section"><a href="structure-meta-recipes-extended.html">5.3.9. <code class="filename">meta/recipes-extended/</code></a></span></dt>
66<dt><span class="section"><a href="structure-meta-recipes-gnome.html">5.3.10. <code class="filename">meta/recipes-gnome/</code></a></span></dt>
67<dt><span class="section"><a href="structure-meta-recipes-graphics.html">5.3.11. <code class="filename">meta/recipes-graphics/</code></a></span></dt>
68<dt><span class="section"><a href="structure-meta-recipes-kernel.html">5.3.12. <code class="filename">meta/recipes-kernel/</code></a></span></dt>
69<dt><span class="section"><a href="structure-meta-recipes-multimedia.html">5.3.13. <code class="filename">meta/recipes-multimedia/</code></a></span></dt>
70<dt><span class="section"><a href="structure-meta-recipes-qt.html">5.3.14. <code class="filename">meta/recipes-qt/</code></a></span></dt>
71<dt><span class="section"><a href="structure-meta-recipes-rt.html">5.3.15. <code class="filename">meta/recipes-rt/</code></a></span></dt>
72<dt><span class="section"><a href="structure-meta-recipes-sato.html">5.3.16. <code class="filename">meta/recipes-sato/</code></a></span></dt>
73<dt><span class="section"><a href="structure-meta-recipes-support.html">5.3.17. <code class="filename">meta/recipes-support/</code></a></span></dt>
74<dt><span class="section"><a href="structure-meta-site.html">5.3.18. <code class="filename">meta/site/</code></a></span></dt>
75<dt><span class="section"><a href="structure-meta-recipes-txt.html">5.3.19. <code class="filename">meta/recipes.txt</code></a></span></dt>
76</dl></dd>
77</dl>
78</div>
79<p>
80 The <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a> consists of several components.
81 Understanding them and knowing where they are located is key to using the Yocto Project well.
82 This chapter describes the Source Directory and gives information about the various
83 files and directories.
84</p>
85<p>
86 For information on how to establish a local Source Directory on your development system, see the
87 "<a class="link" href="../dev-manual/getting-setup.html" target="_self">Getting Set Up</a>"
88 section in the Yocto Project Development Manual.
89</p>
90<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
91<h3 class="title">Note</h3>
92 The OpenEmbedded build system does not support file or directory names that
93 contain spaces.
94 Be sure that the Source Directory you use does not contain these types
95 of names.
96</div>
97</div></body>
98</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-variables-glos.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-variables-glos.html
deleted file mode 100644
index bb6374fab7..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-variables-glos.html
+++ /dev/null
@@ -1,2800 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 10. Variables Glossary</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="ref-features-backfill.html" title="9.4. Feature Backfilling">
10<link rel="next" href="ref-varlocality.html" title="Chapter 11. Variable Context">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 10. Variables Glossary">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-variables-glos"></a>Chapter 10. Variables Glossary</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl><dt><span class="glossary"><a href="ref-variables-glos.html#ref-variables-glossary">Glossary</a></span></dt></dl>
18</div>
19<p>
20 This chapter lists common variables used in the OpenEmbedded build system and gives an overview
21 of their function and contents.
22</p>
23<div class="glossary" title="Glossary">
24<div class="titlepage"><div><div><h2 class="title">
25<a name="ref-variables-glossary"></a>Glossary</h2></div></div></div>
26<p>
27 <a class="link" href="ref-variables-glos.html#var-ALLOW_EMPTY" title="ALLOW_EMPTY">A</a>
28 <a class="link" href="ref-variables-glos.html#var-B" title="B">B</a>
29 <a class="link" href="ref-variables-glos.html#var-CFLAGS" title="CFLAGS">C</a>
30 <a class="link" href="ref-variables-glos.html#var-D" title="D">D</a>
31 <a class="link" href="ref-variables-glos.html#var-ENABLE_BINARY_LOCALE_GENERATION" title="ENABLE_BINARY_LOCALE_GENERATION">E</a>
32 <a class="link" href="ref-variables-glos.html#var-FILES" title="FILES">F</a>
33
34 <a class="link" href="ref-variables-glos.html#var-HOMEPAGE" title="HOMEPAGE">H</a>
35 <a class="link" href="ref-variables-glos.html#var-IMAGE_FEATURES" title="IMAGE_FEATURES">I</a>
36
37 <a class="link" href="ref-variables-glos.html#var-KBRANCH" title="KBRANCH">K</a>
38 <a class="link" href="ref-variables-glos.html#var-LAYERDIR" title="LAYERDIR">L</a>
39 <a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE">M</a>
40
41 <a class="link" href="ref-variables-glos.html#var-OE_TERMINAL" title="OE_TERMINAL">O</a>
42 <a class="link" href="ref-variables-glos.html#var-P" title="P">P</a>
43
44 <a class="link" href="ref-variables-glos.html#var-RCONFLICTS" title="RCONFLICTS">R</a>
45 <a class="link" href="ref-variables-glos.html#var-S" title="S">S</a>
46 <a class="link" href="ref-variables-glos.html#var-T" title="T">T</a>
47
48
49 <a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">W</a>
50
51
52
53 </p>
54<div class="glossdiv" title="A">
55<h3 class="title">A</h3>
56<dl>
57<dt>
58<a name="var-ALLOW_EMPTY"></a>ALLOW_EMPTY</dt>
59<dd>
60<p>
61 Specifies if an output package should still be produced if it is empty.
62 By default, BitBake does not produce empty packages.
63 This default behavior can cause issues when there is an
64 <a class="link" href="ref-variables-glos.html#var-RDEPENDS" title="RDEPENDS"><code class="filename">RDEPENDS</code></a> or
65 some other runtime hard-requirement on the existence of the package.
66 </p>
67<p>
68 Like all package-controlling variables, you must always use them in
69 conjunction with a package name override.
70 Here is an example:
71 </p>
72<pre class="literallayout">
73 ALLOW_EMPTY_${PN} = "1"
74 </pre>
75<p>
76 </p>
77</dd>
78<dt>
79<a name="var-AUTHOR"></a>AUTHOR</dt>
80<dd><p>The email address used to contact the original author or authors in
81 order to send patches, forward bugs, etc.</p></dd>
82<dt>
83<a name="var-AUTOREV"></a>AUTOREV</dt>
84<dd>
85<p>When <code class="filename"><a class="link" href="ref-variables-glos.html#var-SRCREV" title="SRCREV">SRCREV</a></code>
86 is set to the value of this variable, it specifies that the latest
87 source revision in the repository should be used. Here is an example:
88 </p>
89<pre class="literallayout">
90 SRCREV = "${AUTOREV}"
91 </pre>
92<p>
93 </p>
94</dd>
95</dl>
96</div>
97<div class="glossdiv" title="B">
98<h3 class="title">B</h3>
99<dl>
100<dt>
101<a name="var-B"></a>B</dt>
102<dd>
103<p>
104 The <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
105 The OpenEmbedded build system places generated objects into the Build Directory
106 during a recipe's build process.
107 By default, this directory is the same as the <a class="link" href="ref-variables-glos.html#var-S" title="S"><code class="filename">S</code></a>
108 directory:
109 </p>
110<pre class="literallayout">
111 B = ${WORKDIR}/${BPN}-{PV}/
112 </pre>
113<p>
114 You can separate the (<code class="filename">S</code>) directory and the directory pointed to
115 by the <code class="filename">B</code> variable.
116 Most autotools-based recipes support separating these directories.
117 The build system defaults to using separate directories for <code class="filename">gcc</code>
118 and some kernel recipes.
119 </p>
120</dd>
121<dt>
122<a name="var-BAD_RECOMMENDATIONS"></a>BAD_RECOMMENDATIONS</dt>
123<dd><p>
124 A list of packages not to install despite being recommended by a recipe.
125 Support for this variable exists only when using the
126 <code class="filename">ipk</code> packaging backend.
127 </p></dd>
128<dt>
129<a name="var-BB_DISKMON_DIRS"></a>BB_DISKMON_DIRS</dt>
130<dd>
131<p>
132 Monitors disk space and available inodes during the build
133 and allows you to control the build based on these
134 parameters.
135 </p>
136<p>
137 Disk space monitoring is disabled by default.
138 To enable monitoring, add the <code class="filename">BB_DISKMON_DIRS</code>
139 variable to your <code class="filename">conf/local.conf</code> file found in the
140 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
141 Use the following form:
142 </p>
143<pre class="literallayout">
144 BB_DISKMON_DIRS = "&lt;action&gt;,&lt;dir&gt;,&lt;threshold&gt; [...]"
145
146 where:
147
148 &lt;action&gt; is:
149 ABORT: Immediately abort the build when
150 a threshold is broken.
151 STOPTASKS: Stop the build after the currently
152 executing tasks have finished when
153 a threshold is broken.
154 WARN: Issue a warning but continue the
155 build when a threshold is broken.
156 Subsequent warnings are issued as
157 defined by the
158 <a class="link" href="ref-variables-glos.html#var-BB_DISKMON_WARNINTERVAL" title="BB_DISKMON_WARNINTERVAL">BB_DISKMON_WARNINTERVAL</a> variable,
159 which must be defined in the
160 conf/local.conf file.
161
162 &lt;dir&gt; is:
163 Any directory you choose. You can specify one or
164 more directories to monitor by separating the
165 groupings with a space. If two directories are
166 on the same device, only the first directory
167 is monitored.
168
169 &lt;threshold&gt; is:
170 Either the minimum available disk space,
171 the minimum number of free inodes, or
172 both. You must specify at least one. To
173 omit one or the other, simply omit the value.
174 Specify the threshold using G, M, K for Gbytes,
175 Mbytes, and Kbytes, respectively. If you do
176 not specify G, M, or K, Kbytes is assumed by
177 default. Do not use GB, MB, or KB.
178 </pre>
179<p>
180 </p>
181<p>
182 Here are some examples:
183 </p>
184<pre class="literallayout">
185 BB_DISKMON_DIRS = "ABORT,${TMPDIR},1G,100K WARN,${SSTATE_DIR},1G,100K"
186 BB_DISKMON_DIRS = "STOPTASKS,${TMPDIR},1G"
187 BB_DISKMON_DIRS = "ABORT,${TMPDIR},,100K"
188 </pre>
189<p>
190 The first example works only if you also provide
191 the <a class="link" href="ref-variables-glos.html#var-BB_DISKMON_WARNINTERVAL" title="BB_DISKMON_WARNINTERVAL"><code class="filename">BB_DISKMON_WARNINTERVAL</code></a> variable
192 in the <code class="filename">conf/local.conf</code>.
193 This example causes the build system to immediately
194 abort when either the disk space in <code class="filename">${TMPDIR}</code> drops
195 below 1 Gbyte or the available free inodes drops below
196 100 Kbytes.
197 Because two directories are provided with the variable, the
198 build system also issue a
199 warning when the disk space in the
200 <code class="filename">${SSTATE_DIR}</code> directory drops
201 below 1 Gbyte or the number of free inodes drops
202 below 100 Kbytes.
203 Subsequent warnings are issued during intervals as
204 defined by the <code class="filename">BB_DISKMON_WARNINTERVAL</code>
205 variable.
206 </p>
207<p>
208 The second example stops the build after all currently
209 executing tasks complete when the minimum disk space
210 in the <code class="filename">${TMPDIR}</code> directory drops
211 below 1 Gbyte.
212 No disk monitoring occurs for the free inodes in this case.
213 </p>
214<p>
215 The final example immediately aborts the build when the
216 number of free inodes in the <code class="filename">${TMPDIR}</code> directory
217 drops below 100 Kbytes.
218 No disk space monitoring for the directory itself occurs
219 in this case.
220 </p>
221</dd>
222<dt>
223<a name="var-BB_DISKMON_WARNINTERVAL"></a>BB_DISKMON_WARNINTERVAL</dt>
224<dd>
225<p>
226 Defines the disk space and free inode warning intervals.
227 To set these intervals, define the variable in your
228 <code class="filename">conf/local.conf</code> file in the
229 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
230 </p>
231<p>
232 If you are going to use the
233 <code class="filename">BB_DISKMON_WARNINTERVAL</code> variable, you must
234 also use the
235 <a class="link" href="ref-variables-glos.html#var-BB_DISKMON_DIRS" title="BB_DISKMON_DIRS"><code class="filename">BB_DISKMON_DIRS</code></a> variable
236 and define its action as "WARN".
237 During the build, subsequent warnings are issued each time
238 disk space or number of free inodes further reduces by
239 the respective interval.
240 </p>
241<p>
242 If you do not provide a <code class="filename">BB_DISKMON_WARNINTERVAL</code>
243 variable and you do use <code class="filename">BB_DISKMON_DIRS</code> with
244 the "WARN" action, the disk monitoring interval defaults to
245 the following:
246 </p>
247<pre class="literallayout">
248 BB_DISKMON_WARNINTERVAL = "50M,5K"
249 </pre>
250<p>
251 </p>
252<p>
253 When specifying the variable in your configuration file,
254 use the following form:
255 </p>
256<pre class="literallayout">
257 BB_DISKMON_WARNINTERVAL = "&lt;disk_space_interval&gt;,&lt;disk_inode_interval&gt;"
258
259 where:
260
261 &lt;disk_space_interval&gt; is:
262 An interval of memory expressed in either
263 G, M, or K for Gbytes, Mbytes, or Kbytes,
264 respectively. You cannot use GB, MB, or KB.
265
266 &lt;disk_inode_interval&gt; is:
267 An interval of free inodes expressed in either
268 G, M, or K for Gbytes, Mbytes, or Kbytes,
269 respectively. You cannot use GB, MB, or KB.
270 </pre>
271<p>
272 </p>
273<p>
274 Here is an example:
275 </p>
276<pre class="literallayout">
277 BB_DISKMON_DIRS = "WARN,${SSTATE_DIR},1G,100K"
278 BB_DISKMON_WARNINTERVAL = "50M,5K"
279 </pre>
280<p>
281 These variables cause the OpenEmbedded build system to
282 issue subsequent warnings each time the available
283 disk space further reduces by 50 Mbytes or the number
284 of free inodes further reduces by 5 Kbytes in the
285 <code class="filename">${SSTATE_DIR}</code> directory.
286 Subsequent warnings based on the interval occur each time
287 a respective interval is reached beyond the intial warning
288 (i.e. 1 Gbytes and 100 Kbytes).
289 </p>
290</dd>
291<dt>
292<a name="var-BBCLASSEXTEND"></a>BBCLASSEXTEND</dt>
293<dd>
294<p>
295 Allows you to extend a recipe so that it builds variants of the software.
296 Common variants for recipes exist such as "natives" like <code class="filename">quilt-native</code>,
297 which is a copy of quilt built to run on the build system;
298 "crosses" such as <code class="filename">gcc-cross</code>,
299 which is a compiler built to run on the build machine but produces binaries
300 that run on the target <a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE"><code class="filename">MACHINE</code></a>;
301 "nativesdk", which targets the SDK machine instead of <code class="filename">MACHINE</code>;
302 and "mulitlibs" in the form "<code class="filename">multilib:&lt;multilib_name&gt;</code>".
303 </p>
304<p>
305 To build a different variant of the recipe with a minimal amount of code, it usually
306 is as simple as adding the following to your recipe:
307 </p>
308<pre class="literallayout">
309 BBCLASSEXTEND =+ "native nativesdk"
310 BBCLASSEXTEND =+ "multilib:&lt;multilib_name&gt;"
311 </pre>
312<p>
313 </p>
314</dd>
315<dt>
316<a name="var-BBMASK"></a>BBMASK</dt>
317<dd>
318<p>Prevents BitBake from processing recipes and recipe append files.
319 You can use the <code class="filename">BBMASK</code> variable to "hide"
320 these <code class="filename">.bb</code> and <code class="filename">.bbappend</code> files.
321 BitBake ignores any recipe or recipe append files that match the expression.
322 It is as if BitBake does not see them at all.
323 Consequently, matching files are not parsed or otherwise used by
324 BitBake.</p>
325<p>The value you provide is passed to python's regular expression compiler.
326 For complete syntax information, see python's documentation at
327 <a class="ulink" href="http://docs.python.org/release/2.3/lib/re-syntax.html" target="_self">http://docs.python.org/release/2.3/lib/re-syntax.html</a>.
328 The expression is compared against the full paths to the files.
329 For example, the following uses a complete regular expression to tell
330 BitBake to ignore all recipe and recipe append files in the
331 <code class="filename">.*/meta-ti/recipes-misc/</code> directory:
332 </p>
333<pre class="literallayout">
334 BBMASK = ".*/meta-ti/recipes-misc/"
335 </pre>
336<p>Use the <code class="filename">BBMASK</code> variable from within the
337 <code class="filename">conf/local.conf</code> file found
338 in the <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.</p>
339</dd>
340<dt>
341<a name="var-BB_NUMBER_THREADS"></a>BB_NUMBER_THREADS</dt>
342<dd><p>The maximum number of tasks BitBake should run in parallel at any one time.
343 If your host development system supports multiple cores a good rule of thumb
344 is to set this variable to twice the number of cores.</p></dd>
345<dt>
346<a name="var-BBFILE_COLLECTIONS"></a>BBFILE_COLLECTIONS</dt>
347<dd><p>Lists the names of configured layers.
348 These names are used to find the other <code class="filename">BBFILE_*</code>
349 variables.
350 Typically, each layer will append its name to this variable in its
351 <code class="filename">conf/layer.conf</code> file.
352 </p></dd>
353<dt>
354<a name="var-BBFILE_PATTERN"></a>BBFILE_PATTERN</dt>
355<dd><p>Variable that expands to match files from <code class="filename">BBFILES</code> in a particular layer.
356 This variable is used in the <code class="filename">conf/layer.conf</code> file and must
357 be suffixed with the name of the specific layer (e.g.
358 <code class="filename">BBFILE_PATTERN_emenlow</code>).</p></dd>
359<dt>
360<a name="var-BBFILE_PRIORITY"></a>BBFILE_PRIORITY</dt>
361<dd>
362<p>Assigns the priority for recipe files in each layer.</p>
363<p>This variable is useful in situations where the same recipe appears in
364 more than one layer.
365 Setting this variable allows you to prioritize a
366 layer against other layers that contain the same recipe - effectively
367 letting you control the precedence for the multiple layers.
368 The precedence established through this variable stands regardless of a
369 recipe's version (<code class="filename">PV</code> variable).
370 For example, a layer that has a recipe with a higher <code class="filename">PV</code> value but for
371 which the <code class="filename">BBFILE_PRIORITY</code> is set to have a lower precedence still has a
372 lower precedence.</p>
373<p>A larger value for the <code class="filename">BBFILE_PRIORITY</code> variable results in a higher
374 precedence.
375 For example, the value 6 has a higher precedence than the value 5.
376 If not specified, the <code class="filename">BBFILE_PRIORITY</code> variable is set based on layer
377 dependencies (see the
378 <code class="filename"><a class="link" href="ref-variables-glos.html#var-LAYERDEPENDS" title="LAYERDEPENDS">LAYERDEPENDS</a></code> variable for
379 more information.
380 The default priority, if unspecified
381 for a layer with no dependencies, is the lowest defined priority + 1
382 (or 1 if no priorities are defined).</p>
383<div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;">
384<h3 class="title">Tip</h3>
385 You can use the command <code class="filename">bitbake-layers show_layers</code> to list
386 all configured layers along with their priorities.
387 </div>
388</dd>
389<dt>
390<a name="var-BBFILES"></a>BBFILES</dt>
391<dd><p>List of recipe files used by BitBake to build software</p></dd>
392<dt>
393<a name="var-BBPATH"></a>BBPATH</dt>
394<dd><p>Used by BitBake to locate <code class="filename">.bbclass</code> and configuration files.
395 This variable is analogous to the <code class="filename">PATH</code> variable.</p></dd>
396<dt>
397<a name="var-BBINCLUDELOGS"></a>BBINCLUDELOGS</dt>
398<dd><p>Variable that controls how BitBake displays logs on build failure.</p></dd>
399<dt>
400<a name="var-BBLAYERS"></a>BBLAYERS</dt>
401<dd>
402<p>Lists the layers to enable during the build.
403 This variable is defined in the <code class="filename">bblayers.conf</code> configuration
404 file in the <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
405 Here is an example:
406 </p>
407<pre class="literallayout">
408 BBLAYERS = " \
409 /home/scottrif/poky/meta \
410 /home/scottrif/poky/meta-yocto \
411 /home/scottrif/poky/meta-yocto-bsp \
412 /home/scottrif/poky/meta-mykernel \
413 "
414 </pre>
415<p>
416 This example enables four layers, one of which is a custom, user-defined layer
417 named <code class="filename">meta-mykernel</code>.
418 </p>
419</dd>
420<dt>
421<a name="var-BP"></a>BP</dt>
422<dd>
423<p>The base recipe name and version but without any special
424 recipe name suffix (i.e. <code class="filename">-native</code>, <code class="filename">lib64-</code>,
425 and so forth).
426 <code class="filename">BP</code> is comprised of the following:
427 </p>
428<pre class="literallayout">
429 ${BPN}-${PV}
430 </pre>
431</dd>
432<dt>
433<a name="var-BPN"></a>BPN</dt>
434<dd><p>The bare name of the recipe.
435 This variable is a version of the <a class="link" href="ref-variables-glos.html#var-PN" title="PN"><code class="filename">PN</code></a> variable
436 but removes common suffixes such as "-native" and "-cross" as well
437 as removes common prefixes such as multilib's "lib64-" and "lib32-".
438 The exact list of suffixes removed is specified by the
439 <a class="link" href="ref-variables-glos.html#var-SPECIAL_PKGSUFFIX" title="SPECIAL_PKGSUFFIX"><code class="filename">SPECIAL_PKGSUFFIX</code></a> variable.
440 The exact list of prefixes removed is specified by the
441 <a class="link" href="ref-variables-glos.html#var-MLPREFIX" title="MLPREFIX"><code class="filename">MLPREFIX</code></a> variable.
442 Prefixes are removed for multilib and nativesdk cases.</p></dd>
443</dl>
444</div>
445<div class="glossdiv" title="C">
446<h3 class="title">C</h3>
447<dl>
448<dt>
449<a name="var-CFLAGS"></a>CFLAGS</dt>
450<dd><p>
451 Flags passed to C compiler for the target system.
452 This variable evaluates to the same as
453 <code class="filename"><a class="link" href="ref-variables-glos.html#var-TARGET_CFLAGS" title="TARGET_CFLAGS">TARGET_CFLAGS</a></code>.
454 </p></dd>
455<dt>
456<a name="var-COMBINED_FEATURES"></a>COMBINED_FEATURES</dt>
457<dd><p>A set of features common between
458 <a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES"><code class="filename">MACHINE_FEATURES</code></a>
459 and <a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES" title="DISTRO_FEATURES"><code class="filename">DISTRO_FEATURES</code></a>.
460 See the glossary descriptions for these variables for more information.</p></dd>
461<dt>
462<a name="var-COMPATIBLE_MACHINE"></a>COMPATIBLE_MACHINE</dt>
463<dd><p>A regular expression which evaluates to match the machines the recipe
464 works with.
465 It stops recipes being run on machines for which they are not compatible.
466 This is particularly useful with kernels.
467 It also helps to increase parsing speed as further parsing of the recipe is skipped
468 if it is found the current machine is not compatible.</p></dd>
469<dt>
470<a name="var-CONFFILES"></a>CONFFILES</dt>
471<dd>
472<p>
473 Identifies editable or configurable files that are part of a package.
474 If the Package Management System (PMS) is being used to update
475 packages on the target system, it is possible that
476 configuration files you have changed after the original installation
477 and that you now want to remain unchanged are overwritten.
478 In other words, editable files might exist in the package that you do not
479 want reset as part of the package update process.
480 You can use the <code class="filename">CONFFILES</code> variable to list the files in the
481 package that you wish to prevent the PMS from overwriting during this update process.
482 </p>
483<p>
484 To use the <code class="filename">CONFFILES</code> variable, provide a package name
485 override that identifies the resulting package.
486 Then, provide a space-separated list of files.
487 Here is an example:
488 </p>
489<pre class="literallayout">
490 CONFFILES_${PN} += "${sysconfdir}/file1 \
491 ${sysconfdir}/file2 ${sysconfdir}/file3"
492 </pre>
493<p>
494 </p>
495<p>
496 A relationship exists between the <code class="filename">CONFFILES</code> and
497 <code class="filename"><a class="link" href="ref-variables-glos.html#var-FILES" title="FILES">FILES</a></code> variables.
498 The files listed within <code class="filename">CONFFILES</code> must be a subset of
499 the files listed within <code class="filename">FILES</code>.
500 Because the configuration files you provide with <code class="filename">CONFFILES</code>
501 are simply being identified so that the PMS will not overwrite them,
502 it makes sense that
503 the files must already be included as part of the package through the
504 <code class="filename">FILES</code> variable.
505 </p>
506<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
507<h3 class="title">Note</h3>
508 When specifying paths as part of the <code class="filename">CONFFILES</code> variable,
509 it is good practice to use appropriate path variables.
510 For example, <code class="filename">${sysconfdir}</code> rather than
511 <code class="filename">/etc</code> or <code class="filename">${bindir}</code> rather
512 than <code class="filename">/usr/bin</code>.
513 You can find a list of these variables at the top of the
514 <code class="filename">/meta/conf/bitbake.conf</code> file in the
515 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
516 </div>
517</dd>
518<dt>
519<a name="var-CONFIG_SITE"></a>CONFIG_SITE</dt>
520<dd><p>
521 A list of files that contains <code class="filename">autoconf</code> test results relevant
522 to the current build.
523 This variable is used by the Autotools utilities when running
524 <code class="filename">configure</code>.
525 </p></dd>
526<dt>
527<a name="var-CORE_IMAGE_EXTRA_INSTALL"></a>CORE_IMAGE_EXTRA_INSTALL</dt>
528<dd>
529<p>
530 Specifies the list of packages to be added to the image.
531 This variable should only be set in the <code class="filename">local.conf</code>
532 configuration file found in the
533 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
534 </p>
535<p>
536 This variable replaces <code class="filename">POKY_EXTRA_INSTALL</code>, which is no longer supported.
537 </p>
538</dd>
539</dl>
540</div>
541<div class="glossdiv" title="D">
542<h3 class="title">D</h3>
543<dl>
544<dt>
545<a name="var-D"></a>D</dt>
546<dd><p>The destination directory.</p></dd>
547<dt>
548<a name="var-DEBUG_BUILD"></a>DEBUG_BUILD</dt>
549<dd><p>
550 Specifies to build packages with debugging information.
551 This influences the value of the
552 <code class="filename"><a class="link" href="ref-variables-glos.html#var-SELECTED_OPTIMIZATION" title="SELECTED_OPTIMIZATION">SELECTED_OPTIMIZATION</a></code>
553 variable.
554 </p></dd>
555<dt>
556<a name="var-DEBUG_OPTIMIZATION"></a>DEBUG_OPTIMIZATION</dt>
557<dd><p>
558 The options to pass in
559 <code class="filename"><a class="link" href="ref-variables-glos.html#var-TARGET_CFLAGS" title="TARGET_CFLAGS">TARGET_CFLAGS</a></code>
560 and <code class="filename"><a class="link" href="ref-variables-glos.html#var-CFLAGS" title="CFLAGS">CFLAGS</a></code> when compiling
561 a system for debugging.
562 This variable defaults to "-O -fno-omit-frame-pointer -g".
563 </p></dd>
564<dt>
565<a name="var-DEFAULT_PREFERENCE"></a>DEFAULT_PREFERENCE</dt>
566<dd><p>Specifies the priority of recipes.</p></dd>
567<dt>
568<a name="var-DEPENDS"></a>DEPENDS</dt>
569<dd><p>
570 Lists a recipe's build-time dependencies
571 (i.e. other recipe files).
572 The system ensures that all the dependencies listed
573 have been built and have their contents in the appropriate
574 sysroots before the recipe's configure task is executed.
575 </p></dd>
576<dt>
577<a name="var-DESCRIPTION"></a>DESCRIPTION</dt>
578<dd><p>The package description used by package managers.
579 If not set, <code class="filename">DESCRIPTION</code> takes
580 the value of the
581 <a class="link" href="ref-variables-glos.html#var-SUMMARY" title="SUMMARY"><code class="filename">SUMMARY</code></a>
582 variable.
583 </p></dd>
584<dt>
585<a name="var-DESTDIR"></a>DESTDIR</dt>
586<dd><p>the destination directory.</p></dd>
587<dt>
588<a name="var-DISTRO"></a>DISTRO</dt>
589<dd>
590<p>
591 The short name of the distribution.
592 This variable corresponds to a file with the
593 extension <code class="filename">.conf</code>
594 located in a <code class="filename">conf/distro</code> directory
595 within the metadata that contains the distribution configuration.
596 The
597 value must not contain spaces, and is typically all lower-case.
598 </p>
599<p>
600 If the variable is blank, a set of default configuration
601 will be used, which is specified
602 within <code class="filename">meta/conf/distro/defaultsetup.conf</code>.
603 </p>
604</dd>
605<dt>
606<a name="var-DISTRO_EXTRA_RDEPENDS"></a>DISTRO_EXTRA_RDEPENDS</dt>
607<dd><p>
608 Specifies a list of distro-specific packages to add to all images.
609 This variable takes affect through
610 <code class="filename">packagegroup-base</code> so the
611 variable only really applies to the more full-featured
612 images that include <code class="filename">packagegroup-base</code>.
613 You can use this variable to keep distro policy out of
614 generic images.
615 As with all other distro variables, you set this variable
616 in the distro <code class="filename">.conf</code> file.
617 </p></dd>
618<dt>
619<a name="var-DISTRO_EXTRA_RRECOMMENDS"></a>DISTRO_EXTRA_RRECOMMENDS</dt>
620<dd><p>
621 Specifies a list of distro-specific packages to add to all images
622 if the packages exist.
623 The packages might not exist or be empty (e.g. kernel modules).
624 The list of packages are automatically installed but can be
625 removed by the user.
626 </p></dd>
627<dt>
628<a name="var-DISTRO_FEATURES"></a>DISTRO_FEATURES</dt>
629<dd><p>The features enabled for the distribution.
630 For a list of features supported by the Yocto Project as shipped,
631 see the "<a class="link" href="ref-features-distro.html" title="9.1. Distro">Distro</a>"
632 section.
633 </p></dd>
634<dt>
635<a name="var-DISTRO_FEATURES_BACKFILL"></a>DISTRO_FEATURES_BACKFILL</dt>
636<dd>
637<p>Features to be added to
638 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES" title="DISTRO_FEATURES">DISTRO_FEATURES</a></code>
639 if not also present in
640 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES_BACKFILL_CONSIDERED" title="DISTRO_FEATURES_BACKFILL_CONSIDERED">DISTRO_FEATURES_BACKFILL_CONSIDERED</a></code>.
641 </p>
642<p>
643 This variable is set in the <code class="filename">meta/conf/bitbake.conf</code> file.
644 It is not intended to be user-configurable.
645 It is best to just reference the variable to see which distro features are
646 being backfilled for all distro configurations.
647 See the <a class="link" href="ref-features-backfill.html" title="9.4. Feature Backfilling">Feature backfilling</a> section for
648 more information.
649 </p>
650</dd>
651<dt>
652<a name="var-DISTRO_FEATURES_BACKFILL_CONSIDERED"></a>DISTRO_FEATURES_BACKFILL_CONSIDERED</dt>
653<dd><p>Features from
654 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES_BACKFILL" title="DISTRO_FEATURES_BACKFILL">DISTRO_FEATURES_BACKFILL</a></code>
655 that should not backfilled (i.e. added to
656 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_FEATURES" title="DISTRO_FEATURES">DISTRO_FEATURES</a></code>)
657 during the build.
658 See the "<a class="link" href="ref-features-backfill.html" title="9.4. Feature Backfilling">Feature Backfilling</a>" section for
659 more information.
660 </p></dd>
661<dt>
662<a name="var-DISTRO_NAME"></a>DISTRO_NAME</dt>
663<dd><p>The long name of the distribution.</p></dd>
664<dt>
665<a name="var-DISTRO_PN_ALIAS"></a>DISTRO_PN_ALIAS</dt>
666<dd>
667<p>Alias names used for the recipe in various Linux distributions.</p>
668<p>See the
669 "<a class="link" href="../dev-manual/usingpoky-configuring-DISTRO_PN_ALIAS.html" target="_self">Handling
670 a Package Name Alias</a>" section in the Yocto Project Development
671 Manual for more information.</p>
672</dd>
673<dt>
674<a name="var-DISTRO_VERSION"></a>DISTRO_VERSION</dt>
675<dd><p>the version of the distribution.</p></dd>
676<dt>
677<a name="var-DL_DIR"></a>DL_DIR</dt>
678<dd>
679<p>
680 The central download directory used by the build process to store downloads.
681 You can set this directory by defining the <code class="filename">DL_DIR</code>
682 variable in the <code class="filename">/conf/local.conf</code> file.
683 This directory is self-maintaining and you should not have
684 to touch it.
685 By default, the directory is <code class="filename">downloads</code> in the
686 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
687 </p>
688<pre class="literallayout">
689 #DL_DIR ?= "${TOPDIR}/downloads"
690 </pre>
691<p>
692 To specify a different download directory, simply uncomment the line
693 and provide your directory.
694 </p>
695<p>
696 During a first build, the system downloads many different source code
697 tarballs from various upstream projects.
698 Downloading can take a while, particularly if your network
699 connection is slow.
700 Tarballs are all stored in the directory defined by
701 <code class="filename">DL_DIR</code> and the build system looks there first
702 to find source tarballs.
703 </p>
704<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
705<h3 class="title">Note</h3>
706 When wiping and rebuilding, you can preserve this directory to speed
707 up this part of subsequent builds.
708 </div>
709<p>
710 </p>
711<p>
712 You can safely share this directory between multiple builds on the
713 same development machine.
714 For additional information on how the build process gets source files
715 when working behind a firewall or proxy server, see the
716 "<a class="link" href="faq.html#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server">FAQ</a>"
717 chapter.
718 </p>
719</dd>
720</dl>
721</div>
722<div class="glossdiv" title="E">
723<h3 class="title">E</h3>
724<dl>
725<dt>
726<a name="var-ENABLE_BINARY_LOCALE_GENERATION"></a>ENABLE_BINARY_LOCALE_GENERATION</dt>
727<dd>
728<p></p>
729<p>Variable that controls which locales for <code class="filename">eglibc</code> are
730 to be generated during the build (useful if the target device has 64Mbytes
731 of RAM or less).</p>
732</dd>
733<dt>
734<a name="var-EXTENDPE"></a>EXTENDPE</dt>
735<dd>
736<p>
737 Used with file and pathnames to create a prefix for a recipe's
738 version based on the recipe's
739 <a class="link" href="ref-variables-glos.html#var-PE" title="PE"><code class="filename">PE</code></a> value.
740 If <code class="filename">PE</code> is set and greater than zero for a recipe,
741 <code class="filename">EXTENDPE</code> becomes that value (e.g if
742 <code class="filename">PE</code> is equal to "1" then <code class="filename">EXTENDPE</code>
743 becomes "1_").
744 If a recipe's <code class="filename">PE</code> is not set (the default) or is equal to
745 zero, <code class="filename">EXTENDPE</code> becomes "".</p>
746<p>See the <a class="link" href="ref-variables-glos.html#var-STAMP" title="STAMP"><code class="filename">STAMP</code></a>
747 variable for an example.
748 </p>
749</dd>
750<dt>
751<a name="var-EXTRA_IMAGE_FEATURES"></a>EXTRA_IMAGE_FEATURES</dt>
752<dd>
753<p>Allows extra packages to be added to the generated images.
754 You set this variable in the <code class="filename">local.conf</code>
755 configuration file.
756 Note that some image features are also added using the
757 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FEATURES" title="IMAGE_FEATURES">IMAGE_FEATURES</a></code>
758 variable generally configured in image recipes.
759 You can use this variable to add more features in addition to those.
760 Here are some examples of features you can add:</p>
761<pre class="literallayout">
762"dbg-pkgs" - Adds -dbg packages for all installed packages
763 including symbol information for debugging and
764 profiling.
765
766"dev-pkgs" - Adds -dev packages for all installed packages.
767 This is useful if you want to develop against
768 the libraries in the image.
769
770"tools-sdk" - Adds development tools such as gcc, make,
771 pkgconfig and so forth.
772
773"tools-debug" - Adds debugging tools such as gdb and
774 strace.
775
776"tools-profile" - Adds profiling tools such as oprofile,
777 exmap, lttng and valgrind (x86 only).
778
779"tools-testapps" - Adds useful testing tools such as
780 ts_print, aplay, arecord and so
781 forth.
782
783"debug-tweaks" - Makes an image suitable for development.
784 For example, ssh root access has a blank
785 password. You should remove this feature
786 before you produce a production image.
787 </pre>
788<p>There are other valid features too, see the
789 <a class="link" href="ref-features-image.html" title="9.3. Images">Images</a>
790 section for more details.</p>
791</dd>
792<dt>
793<a name="var-EXTRA_IMAGEDEPENDS"></a>EXTRA_IMAGEDEPENDS</dt>
794<dd>
795<p>A list of recipes to be built that do not provide packages to be installed in
796 the root filesystem.
797 </p>
798<p>Sometimes a recipe is required to build the final image but is not
799 needed in the root filesystem.
800 You can use the <code class="filename">EXTRA_IMAGEDEPENDS</code> variable to
801 list these recipes and thus, specify the dependencies.
802 A typical example is a required bootloader in a machine configuration.
803 </p>
804<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
805<h3 class="title">Note</h3>
806 To add packages to the root filesystem, see the various
807 <code class="filename">*DEPENDS</code> and <code class="filename">*RECOMMENDS</code>
808 variables.
809 </div>
810</dd>
811<dt>
812<a name="var-EXTRA_OECMAKE"></a>EXTRA_OECMAKE</dt>
813<dd><p>Additional <code class="filename">cmake</code> options.</p></dd>
814<dt>
815<a name="var-EXTRA_OECONF"></a>EXTRA_OECONF</dt>
816<dd><p>Additional <code class="filename">configure</code> script options.</p></dd>
817<dt>
818<a name="var-EXTRA_OEMAKE"></a>EXTRA_OEMAKE</dt>
819<dd><p>Additional GNU <code class="filename">make</code> options.</p></dd>
820</dl>
821</div>
822<div class="glossdiv" title="F">
823<h3 class="title">F</h3>
824<dl>
825<dt>
826<a name="var-FILES"></a>FILES</dt>
827<dd>
828<p>
829 The list of directories or files that are placed in packages.
830 </p>
831<p>
832 To use the <code class="filename">FILES</code> variable, provide a package name
833 override that identifies the resulting package.
834 Then, provide a space-separated list of files or paths that identifies the
835 files you want included as part of the resulting package.
836 Here is an example:
837 </p>
838<pre class="literallayout">
839 FILES_${PN} += "${bindir}/mydir1/ ${bindir}/mydir2/myfile"
840 </pre>
841<p>
842 </p>
843<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
844<h3 class="title">Note</h3>
845 When specifying paths as part of the <code class="filename">FILES</code> variable,
846 it is good practice to use appropriate path variables.
847 For example, <code class="filename">${sysconfdir}</code> rather than
848 <code class="filename">/etc</code> or <code class="filename">${bindir}</code> rather
849 than <code class="filename">/usr/bin</code>.
850 You can find a list of these variables at the top of the
851 <code class="filename">/meta/conf/bitbake.conf</code> file in the
852 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
853 </div>
854<p>
855 If some of the files you provide with the <code class="filename">FILES</code> variable
856 are editable and you know they should not be
857 overwritten during the package update process by the Package Management
858 System (PMS), you can identify these files so that the PMS will not
859 overwrite them.
860 See the <code class="filename"><a class="link" href="ref-variables-glos.html#var-CONFFILES" title="CONFFILES">CONFFILES</a></code>
861 variable for information on how to identify these files to the PMS.
862 </p>
863</dd>
864<dt>
865<a name="var-FILESEXTRAPATHS"></a>FILESEXTRAPATHS</dt>
866<dd>
867<p>
868 Extends the search path the OpenEmbedded build system uses when
869 looking for files and patches as it processes recipes.
870 The directories BitBake uses when it processes recipes is defined by the
871 <a class="link" href="ref-variables-glos.html#var-FILESPATH" title="FILESPATH"><code class="filename">FILESPATH</code></a> variable.
872 You can add directories to the search path by defining the
873 <code class="filename">FILESEXTRAPATHS</code> variable.
874 </p>
875<p>
876 To add paths to the search order, provide a list of directories and separate
877 each path using a colon character as follows:
878 </p>
879<pre class="literallayout">
880 FILESEXTRAPATHS_prepend := "path_1:path_2:path_3:"
881 </pre>
882<p>
883 Typically, you want your directories search first.
884 To make sure that happens, use <code class="filename">_prepend</code> and
885 the immediate expansion (<code class="filename">:=</code>) operator as shown in the
886 previous example.
887 Finally, to maintain the integrity of the <code class="filename">FILESPATH</code> variable,
888 you must include the appropriate beginning or ending (as needed) colon character.
889 </p>
890<p>
891 The <code class="filename">FILESEXTRAPATHS</code> variable is intended for use in
892 <code class="filename">.bbappend</code> files to include any additional files provided in that layer.
893 You typically accomplish this with the following:
894 </p>
895<pre class="literallayout">
896 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
897 </pre>
898<p>
899 </p>
900</dd>
901<dt>
902<a name="var-FILESPATH"></a>FILESPATH</dt>
903<dd>
904<p>
905 The default set of directories the OpenEmbedded build system uses
906 when searching for patches and files.
907 During the build process, BitBake searches each directory in
908 <code class="filename">FILESPATH</code> in the specified order when looking for
909 files and patches specified by each <code class="filename">file://</code> URI in a recipe.
910 </p>
911<p>
912 The default value for the <code class="filename">FILESPATH</code> variable is defined
913 in the <code class="filename">base.bbclass</code> class found in
914 <code class="filename">meta/classes</code> in the
915 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>:
916 </p>
917<pre class="literallayout">
918FILESPATH = "${@base_set_filespath([ "${FILE_DIRNAME}/${PF}", \
919 "${FILE_DIRNAME}/${P}", "${FILE_DIRNAME}/${PN}", \
920 "${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", \
921 "${FILE_DIRNAME}/files", "${FILE_DIRNAME}" ], d)}"
922 </pre>
923<p>
924 Do not hand-edit the <code class="filename">FILESPATH</code> variable.
925 If you want to extend the set of pathnames that BitBake uses when searching for
926 files and patches, use the
927 <a class="link" href="ref-variables-glos.html#var-FILESEXTRAPATHS" title="FILESEXTRAPATHS"><code class="filename">FILESEXTRAPATHS</code></a> variable.
928 </p>
929</dd>
930<dt>
931<a name="var-FILESYSTEM_PERMS_TABLES"></a>FILESYSTEM_PERMS_TABLES</dt>
932<dd>
933<p>Allows you to define your own file permissions settings table as part of
934 your configuration for the packaging process.
935 For example, suppose you need a consistent set of custom permissions for
936 a set of groups and users across an entire work project.
937 It is best to do this in the packages themselves but this is not always
938 possible.
939 </p>
940<p>
941 By default, the OpenEmbedded build system uses the <code class="filename">fs-perms.txt</code>, which
942 is located in the <code class="filename">meta/files</code> folder in the
943 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
944 If you create your own file permissions setting table, you should place it in your
945 layer or the distros layer.
946 </p>
947<p>
948 You define the <code class="filename">FILESYSTEM_PERMS_TABLES</code> variable in the
949 <code class="filename">conf/local.conf</code> file, which is found in the
950 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>, to
951 point to your custom <code class="filename">fs-perms.txt</code>.
952 You can specify more than a single file permissions setting table.
953 The paths you specify to these files must be defined within the
954 <code class="filename">BBPATH</code> variable.
955 </p>
956<p>
957 For guidance on how to create your own file permissions settings table file,
958 examine the existing <code class="filename">fs-perms.txt</code>.
959 </p>
960</dd>
961<dt>
962<a name="var-FULL_OPTIMIZATION"></a>FULL_OPTIMIZATION</dt>
963<dd><p>
964 The options to pass in
965 <code class="filename"><a class="link" href="ref-variables-glos.html#var-TARGET_CFLAGS" title="TARGET_CFLAGS">TARGET_CFLAGS</a></code>
966 and <code class="filename"><a class="link" href="ref-variables-glos.html#var-CFLAGS" title="CFLAGS">CFLAGS</a></code>
967 when compiling an optimized system.
968 This variable defaults to
969 "-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2".
970 </p></dd>
971</dl>
972</div>
973<div class="glossdiv" title="H">
974<h3 class="title">H</h3>
975<dl>
976<dt>
977<a name="var-HOMEPAGE"></a>HOMEPAGE</dt>
978<dd><p>Website where more information about the software the recipe is building
979 can be found.</p></dd>
980</dl>
981</div>
982<div class="glossdiv" title="I">
983<h3 class="title">I</h3>
984<dl>
985<dt>
986<a name="var-IMAGE_FEATURES"></a>IMAGE_FEATURES</dt>
987<dd><p>The list of features to include in an image.
988 Typically, you configure this variable in an image recipe.
989 Note that you can also add extra features to the image by using the
990 <code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_IMAGE_FEATURES" title="EXTRA_IMAGE_FEATURES">EXTRA_IMAGE_FEATURES</a></code> variable.
991 See the "<a class="link" href="ref-features-image.html" title="9.3. Images">Images</a>" section for the
992 full list of features that can be included in images built by the
993 OpenEmbedded build system.</p></dd>
994<dt>
995<a name="var-IMAGE_FSTYPES"></a>IMAGE_FSTYPES</dt>
996<dd><p>Formats of root filesystem images that you want to have created.</p></dd>
997<dt>
998<a name="var-IMAGE_INSTALL"></a>IMAGE_INSTALL</dt>
999<dd>
1000<p>
1001 Specifies the packages to install into an image.
1002 The <code class="filename">IMAGE_INSTALL</code> variable is a mechanism for an image
1003 recipe and you should use it with care to avoid ordering issues.
1004 </p>
1005<p>
1006 Image recipes set <code class="filename">IMAGE_INSTALL</code> to specify the
1007 packages to install into an image through <code class="filename">image.bbclass</code>.
1008 Additionally, "helper" classes exist, such as <code class="filename">core-image.bbclass</code>,
1009 that can take
1010 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FEATURES" title="IMAGE_FEATURES">IMAGE_FEATURES</a></code> lists
1011 and turn these into auto-generated entries in
1012 <code class="filename">IMAGE_INSTALL</code> in addition to its default contents.
1013 </p>
1014<p>
1015 Using <code class="filename">IMAGE_INSTALL</code> with the <code class="filename">+=</code>
1016 operator from the <code class="filename">/conf/local.conf</code> file or from within
1017 an image recipe is not recommended as it can cause ordering issues.
1018 Since <code class="filename">core-image.bbclass</code> sets <code class="filename">IMAGE_INSTALL</code>
1019 to a default value using the <code class="filename">?=</code> operator, using a
1020 <code class="filename">+=</code> operation against <code class="filename">IMAGE_INSTALL</code>
1021 will result in unexpected behavior when used in
1022 <code class="filename">/conf/local.conf</code>.
1023 Furthermore, the same operation from with an image recipe may or may not
1024 succeed depending on the specific situation.
1025 In both these cases, the behavior is contrary to how most users expect
1026 the <code class="filename">+=</code> operator to work.
1027 </p>
1028<p>
1029 When you use this variable, it is best to use it as follows:
1030 </p>
1031<pre class="literallayout">
1032 IMAGE_INSTALL_append = " package-name"
1033 </pre>
1034<p>
1035 Be sure to include the space between the quotation character and the start of the
1036 package name.
1037 </p>
1038</dd>
1039<dt>
1040<a name="var-IMAGE_OVERHEAD_FACTOR"></a>IMAGE_OVERHEAD_FACTOR</dt>
1041<dd>
1042<p>
1043 Defines a multiplier that the build system applies to the initial image
1044 size for cases when the multiplier times the returned disk usage value
1045 for the image is greater than the sum of
1046 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_ROOTFS_SIZE" title="IMAGE_ROOTFS_SIZE">IMAGE_ROOTFS_SIZE</a></code>
1047 and
1048 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_ROOTFS_EXTRA_SPACE" title="IMAGE_ROOTFS_EXTRA_SPACE">IMAGE_ROOTFS_EXTRA_SPACE</a></code>.
1049 The result of the multiplier applied to the initial image size creates
1050 free disk space in the image as overhead.
1051 By default, the build process uses a multiplier of 1.3 for this variable.
1052 This default value results in 30% free disk space added to the image when this
1053 method is used to determine the final generated image size.
1054 You should be aware that post install scripts and the package management
1055 system uses disk space inside this overhead area.
1056 Consequently, the multiplier does not produce an image with
1057 all the theoretical free disk space.
1058 See <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_ROOTFS_SIZE" title="IMAGE_ROOTFS_SIZE">IMAGE_ROOTFS_SIZE</a></code>
1059 for information on how the build system determines the overall image size.
1060 </p>
1061<p>
1062 The default 30% free disk space typically gives the image enough room to boot
1063 and allows for basic post installs while still leaving a small amount of
1064 free disk space.
1065 If 30% free space is inadequate, you can increase the default value.
1066 For example, the following setting gives you 50% free space added to the image:
1067 </p>
1068<pre class="literallayout">
1069 IMAGE_OVERHEAD_FACTOR = "1.5"
1070 </pre>
1071<p>
1072 </p>
1073<p>
1074 Alternatively, you can ensure a specific amount of free disk space is added
1075 to the image by using
1076 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_ROOTFS_EXTRA_SPACE" title="IMAGE_ROOTFS_EXTRA_SPACE">IMAGE_ROOTFS_EXTRA_SPACE</a></code>
1077 the variable.
1078 </p>
1079</dd>
1080<dt>
1081<a name="var-IMAGE_ROOTFS_EXTRA_SPACE"></a>IMAGE_ROOTFS_EXTRA_SPACE</dt>
1082<dd>
1083<p>
1084 Defines additional free disk space created in the image in Kbytes.
1085 By default, this variable is set to "0".
1086 This free disk space is added to the image after the build system determines
1087 the image size as described in
1088 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_ROOTFS_SIZE" title="IMAGE_ROOTFS_SIZE">IMAGE_ROOTFS_SIZE</a></code>.
1089 </p>
1090<p>
1091 This variable is particularly useful when you want to ensure that a
1092 specific amount of free disk space is available on a device after an image
1093 is installed and running.
1094 For example, to be sure 5 Gbytes of free disk space is available, set the
1095 variable as follows:
1096 </p>
1097<pre class="literallayout">
1098 IMAGE_ROOTFS_EXTRA_SPACE = "5242880"
1099 </pre>
1100<p>
1101 </p>
1102</dd>
1103<dt>
1104<a name="var-IMAGE_ROOTFS_SIZE"></a>IMAGE_ROOTFS_SIZE</dt>
1105<dd>
1106<p>
1107 Defines the size in Kbytes for the generated image.
1108 The OpenEmbedded build system determines the final size for the generated
1109 image using an algorithm that takes into account the initial disk space used
1110 for the generated image, a requested size for the image, and requested
1111 additional free disk space to be added to the image.
1112 Programatically, the build system determines the final size of the
1113 generated image as follows:
1114 </p>
1115<pre class="literallayout">
1116 if (image-du * overhead) &lt; rootfs-size:
1117 internal-rootfs-size = rootfs-size + xspace
1118 else:
1119 internal-rootfs-size = (image-du * overhead) + xspace
1120
1121 where:
1122
1123 image-du = Returned value of the du command on
1124 the image.
1125
1126 overhead = IMAGE_OVERHEAD_FACTOR
1127
1128 rootfs-size = IMAGE_ROOTFS_SIZE
1129
1130 internal-rootfs-size = Initial root filesystem
1131 size before any modifications.
1132
1133 xspace = IMAGE_ROOTFS_EXTRA_SPACE
1134 </pre>
1135<p>
1136
1137 </p>
1138</dd>
1139<dt>
1140<a name="var-INC_PR"></a>INC_PR</dt>
1141<dd>
1142<p>Helps define the recipe revision for recipes that share
1143 a common <code class="filename">include</code> file.
1144 You can think of this variable as part of the recipe revision
1145 as set from within an include file.</p>
1146<p>Suppose, for example, you have a set of recipes that
1147 are used across several projects.
1148 And, within each of those recipes the revision
1149 (its <code class="filename">PR</code> value) is set accordingly.
1150 In this case, when the revision of those recipes changes
1151 the burden is on you to find all those recipes and
1152 be sure that they get changed to reflect the updated
1153 version of the recipe.
1154 In this scenario, it can get complicated when recipes
1155 used in many places and that provide common functionality
1156 are upgraded to a new revision.</p>
1157<p>A more efficient way of dealing with this situation is
1158 to set the <code class="filename">INC_PR</code> variable inside
1159 the <code class="filename">include</code> files that the recipes
1160 share and then expand the <code class="filename">INC_PR</code>
1161 variable within the recipes to help
1162 define the recipe revision.
1163 </p>
1164<p>
1165 The following provides an example that shows how to use
1166 the <code class="filename">INC_PR</code> variable
1167 given a common <code class="filename">include</code> file that
1168 defines the variable.
1169 Once the variable is defined in the
1170 <code class="filename">include</code> file, you can use the
1171 variable to set the <code class="filename">PR</code> values in
1172 each recipe.
1173 You will notice that when you set a recipe's
1174 <code class="filename">PR</code> you can provide more granular
1175 revisioning by appending values to the
1176 <code class="filename">INC_PR</code> variable:
1177 </p>
1178<pre class="literallayout">
1179recipes-graphics/xorg-font/xorg-font-common.inc:INC_PR = "r2"
1180recipes-graphics/xorg-font/encodings_1.0.4.bb:PR = "${INC_PR}.1"
1181recipes-graphics/xorg-font/font-util_1.3.0.bb:PR = "${INC_PR}.0"
1182recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
1183 </pre>
1184<p>
1185 The first line of the example establishes the baseline
1186 revision to be used for all recipes that use the
1187 <code class="filename">include</code> file.
1188 The remaining lines in the example are from individual
1189 recipes and show how the <code class="filename">PR</code> value
1190 is set.</p>
1191</dd>
1192<dt>
1193<a name="var-INHIBIT_PACKAGE_STRIP"></a>INHIBIT_PACKAGE_STRIP</dt>
1194<dd><p>
1195 Causes the build to not strip binaries in resulting packages.
1196 </p></dd>
1197<dt>
1198<a name="var-INHERIT"></a>INHERIT</dt>
1199<dd><p>
1200 Causes the named class to be inherited at
1201 this point during parsing.
1202 The variable is only valid in configuration files.
1203 </p></dd>
1204<dt>
1205<a name="var-INITSCRIPT_PACKAGES"></a>INITSCRIPT_PACKAGES</dt>
1206<dd>
1207<p>
1208 A list of the packages that contain initscripts.
1209 If multiple packages are specified, you need to append the package name
1210 to the other <code class="filename">INITSCRIPT_*</code> as an override.</p>
1211<p>
1212 This variable is used in recipes when using <code class="filename">update-rc.d.bbclass</code>.
1213 The variable is optional and defaults to the <code class="filename">PN</code> variable.
1214 </p>
1215</dd>
1216<dt>
1217<a name="var-INITSCRIPT_NAME"></a>INITSCRIPT_NAME</dt>
1218<dd>
1219<p>
1220 The filename of the initscript (as installed to <code class="filename">${etcdir}/init.d)</code>.
1221 </p>
1222<p>
1223 This variable is used in recipes when using <code class="filename">update-rc.d.bbclass</code>.
1224 The variable is Mandatory.
1225 </p>
1226</dd>
1227<dt>
1228<a name="var-INITSCRIPT_PARAMS"></a>INITSCRIPT_PARAMS</dt>
1229<dd>
1230<p>
1231 Specifies the options to pass to <code class="filename">update-rc.d</code>.
1232 An example is <code class="filename">start 99 5 2 . stop 20 0 1 6 .</code>, which gives the script a
1233 runlevel of 99, starts the script in initlevels 2 and 5, and
1234 stops the script in levels 0, 1 and 6.
1235 </p>
1236<p>
1237 The variable is mandatory and is used in recipes when using
1238 <code class="filename">update-rc.d.bbclass</code>.
1239 </p>
1240</dd>
1241</dl>
1242</div>
1243<div class="glossdiv" title="K">
1244<h3 class="title">K</h3>
1245<dl>
1246<dt>
1247<a name="var-KBRANCH"></a>KBRANCH</dt>
1248<dd>
1249<p>
1250 A regular expression used by the build process to explicitly identify the kernel
1251 branch that is validated, patched and configured during a build.
1252 The <code class="filename">KBRANCH</code> variable is optional.
1253 You can use it to trigger checks to ensure the exact kernel branch you want is
1254 being used by the build process.
1255 </p>
1256<p>
1257 Values for this variable are set in the kernel's recipe file and the kernel's
1258 append file.
1259 For example, if you are using the Yocto Project kernel that is based on the
1260 Linux 3.4 kernel, the kernel recipe file is the
1261 <code class="filename">meta/recipes-kernel/linux/linux-yocto_3.4.bb</code> file.
1262 Following is the default value for <code class="filename">KBRANCH</code> and the default
1263 override for the architectures the Yocto Project supports:
1264 </p>
1265<pre class="literallayout">
1266 KBRANCH_DEFAULT = "standard/base"
1267 KBRANCH = "${KBRANCH_DEFAULT}"
1268 </pre>
1269<p>
1270 This branch exists in the <code class="filename">linux-yocto-3.4</code> kernel Git
1271 repository <a class="ulink" href="http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.4/refs/heads" target="_self">http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.4/refs/heads</a>.
1272 </p>
1273<p>
1274 This variable is also used from the kernel's append file to identify the kernel
1275 branch specific to a particular machine or target hardware.
1276 The kernel's append file is located in the BSP layer for a given machine.
1277 For example, the kernel append file for the Crown Bay BSP is in the
1278 <code class="filename">meta-intel</code> Git repository and is named
1279 <code class="filename">meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend</code>.
1280 Here are the related statements from the append file:
1281 </p>
1282<pre class="literallayout">
1283 COMPATIBLE_MACHINE_crownbay = "crownbay"
1284 KMACHINE_crownbay = "crownbay"
1285 KBRANCH_crownbay = "standard/crownbay"
1286
1287 COMPATIBLE_MACHINE_crownbay-noemgd = "crownbay-noemgd"
1288 KMACHINE_crownbay-noemgd = "crownbay"
1289 KBRANCH_crownbay-noemgd = "standard/crownbay"
1290 </pre>
1291<p>
1292 The <code class="filename">KBRANCH_*</code> statements identify the kernel branch to
1293 use when building for the Crown Bay BSP.
1294 In this case there are two identical statements: one for each type of
1295 Crown Bay machine.
1296 </p>
1297</dd>
1298<dt>
1299<a name="var-KERNEL_FEATURES"></a>KERNEL_FEATURES</dt>
1300<dd>
1301<p>Includes additional metadata from the Yocto Project kernel Git repository.
1302 In the OpenEmbedded build system, the default Board Support Packages (BSPs)
1303 metadata is provided through
1304 the <code class="filename">KMACHINE</code> and <code class="filename">KBRANCH</code> variables.
1305 You can use the <code class="filename">KERNEL_FEATURES</code> variable to further
1306 add metadata for all BSPs.</p>
1307<p>The metadata you add through this variable includes config fragments and
1308 features descriptions,
1309 which usually includes patches as well as config fragments.
1310 You typically override the <code class="filename">KERNEL_FEATURES</code> variable
1311 for a specific machine.
1312 In this way, you can provide validated, but optional, sets of kernel
1313 configurations and features.</p>
1314<p>For example, the following adds <code class="filename">netfilter</code> to all
1315 the Yocto Project kernels and adds sound support to the <code class="filename">qemux86</code>
1316 machine:
1317 </p>
1318<pre class="literallayout">
1319 # Add netfilter to all linux-yocto kernels
1320 KERNEL_FEATURES="features/netfilter"
1321
1322 # Add sound support to the qemux86 machine
1323 KERNEL_FEATURES_append_qemux86=" cfg/sound"
1324 </pre>
1325</dd>
1326<dt>
1327<a name="var-KERNEL_IMAGETYPE"></a>KERNEL_IMAGETYPE</dt>
1328<dd><p>The type of kernel to build for a device, usually set by the
1329 machine configuration files and defaults to "zImage".
1330 This variable is used
1331 when building the kernel and is passed to <code class="filename">make</code> as the target to
1332 build.</p></dd>
1333<dt>
1334<a name="var-KMACHINE"></a>KMACHINE</dt>
1335<dd>
1336<p>
1337 The machine as known by the kernel.
1338 Sometimes the machine name used by the kernel does not match the machine name
1339 used by the OpenEmbedded build system.
1340 For example, the machine name that the OpenEmbedded build system understands as
1341 <code class="filename">qemuarm</code> goes by a different name in the Linux Yocto kernel.
1342 The kernel understands that machine as <code class="filename">arm_versatile926ejs</code>.
1343 For cases like these, the <code class="filename">KMACHINE</code> variable maps the
1344 kernel machine name to the OpenEmbedded build system machine name.
1345 </p>
1346<p>
1347 Kernel machine names are initially defined in the
1348 <a class="ulink" href="http://git.yoctoproject.org/cgit.cgi" target="_self">Yocto Linux Kernel</a> in
1349 the <code class="filename">meta</code> branch.
1350 From the <code class="filename">meta</code> branch, look in
1351 the <code class="filename">meta/cfg/kernel-cache/bsp/&lt;bsp_name&gt;/&lt;bsp-name&gt;-&lt;kernel-type&gt;.scc</code> file.
1352 For example, from the <code class="filename">meta</code> branch in the
1353 <code class="filename">linux-yocto-3.0</code> kernel, the
1354 <code class="filename">meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-standard.scc</code> file
1355 has the following:
1356 </p>
1357<pre class="literallayout">
1358 define KMACHINE cedartrail
1359 define KTYPE standard
1360 define KARCH i386
1361
1362 include ktypes/standard
1363 branch cedartrail
1364
1365 include cedartrail.scc
1366 </pre>
1367<p>
1368 You can see that the kernel understands the machine name for the Cedar Trail BSP as
1369 <code class="filename">cedartrail</code>.
1370 </p>
1371<p>
1372 If you look in the Cedar Trail BSP layer in the <code class="filename">meta-intel</code> source
1373 repository at <code class="filename">meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend</code>,
1374 you will find the following statements among others:
1375 </p>
1376<pre class="literallayout">
1377 COMPATIBLE_MACHINE_cedartrail = "cedartrail"
1378 KMACHINE_cedartrail = "cedartrail"
1379 KBRANCH_cedartrail = "yocto/standard/cedartrail"
1380 KERNEL_FEATURES_append_cedartrail += "bsp/cedartrail/cedartrail-pvr-merge.scc"
1381 KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc"
1382
1383 COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
1384 KMACHINE_cedartrail-nopvr = "cedartrail"
1385 KBRANCH_cedartrail-nopvr = "yocto/standard/cedartrail"
1386 KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
1387 </pre>
1388<p>
1389 The <code class="filename">KMACHINE</code> statements in the kernel's append file make sure that
1390 the OpenEmbedded build system and the Yocto Linux kernel understand the same machine
1391 names.
1392 </p>
1393<p>
1394 This append file uses two <code class="filename">KMACHINE</code> statements.
1395 The first is not really necessary but does ensure that the machine known to the
1396 OpenEmbedded build system as <code class="filename">cedartrail</code> maps to the machine
1397 in the kernel also known as <code class="filename">cedartrail</code>:
1398 </p>
1399<pre class="literallayout">
1400 KMACHINE_cedartrail = "cedartrail"
1401 </pre>
1402<p>
1403 </p>
1404<p>
1405 The second statement is a good example of why the <code class="filename">KMACHINE</code> variable
1406 is needed.
1407 In this example, the OpenEmbedded build system uses the <code class="filename">cedartrail-nopvr</code>
1408 machine name to refer to the Cedar Trail BSP that does not support the propriatory
1409 PowerVR driver.
1410 The kernel, however, uses the machine name <code class="filename">cedartrail</code>.
1411 Thus, the append file must map the <code class="filename">cedartrail-nopvr</code> machine name to
1412 the kernel's <code class="filename">cedartrail</code> name:
1413 </p>
1414<pre class="literallayout">
1415 KMACHINE_cedartrail-nopvr = "cedartrail"
1416 </pre>
1417<p>
1418 </p>
1419<p>
1420 BSPs that ship with the Yocto Project release provide all mappings between the Yocto
1421 Project kernel machine names and the OpenEmbedded machine names.
1422 Be sure to use the <code class="filename">KMACHINE</code> if you create a BSP and the machine
1423 name you use is different than that used in the kernel.
1424 </p>
1425</dd>
1426</dl>
1427</div>
1428<div class="glossdiv" title="L">
1429<h3 class="title">L</h3>
1430<dl>
1431<dt>
1432<a name="var-LAYERDEPENDS"></a>LAYERDEPENDS</dt>
1433<dd><p>Lists the layers that this recipe depends upon, separated by spaces.
1434 Optionally, you can specify a specific layer version for a dependency
1435 by adding it to the end of the layer name with a colon, (e.g. "anotherlayer:3"
1436 to be compared against <code class="filename">LAYERVERSION_anotherlayer</code> in this case).
1437 An error will be produced if any dependency is missing or
1438 the version numbers do not match exactly (if specified).
1439 This variable is used in the <code class="filename">conf/layer.conf</code> file
1440 and must be suffixed with the name of the specific layer (e.g.
1441 <code class="filename">LAYERDEPENDS_mylayer</code>).</p></dd>
1442<dt>
1443<a name="var-LAYERDIR"></a>LAYERDIR</dt>
1444<dd><p>When used inside the <code class="filename">layer.conf</code> configuration
1445 file, this variable provides the path of the current layer.
1446 This variable requires immediate expansion
1447 (see the BitBake manual) as lazy expansion can result in
1448 the expansion happening in the wrong directory and therefore
1449 giving the wrong value.</p></dd>
1450<dt>
1451<a name="var-LAYERVERSION"></a>LAYERVERSION</dt>
1452<dd><p>Optionally specifies the version of a layer as a single number.
1453 You can use this within <code class="filename">LAYERDEPENDS</code> for another layer in order to
1454 depend on a specific version of the layer.
1455 This variable is used in the <code class="filename">conf/layer.conf</code> file
1456 and must be suffixed with the name of the specific layer (e.g.
1457 <code class="filename">LAYERVERSION_mylayer</code>).</p></dd>
1458<dt>
1459<a name="var-LIC_FILES_CHKSUM"></a>LIC_FILES_CHKSUM</dt>
1460<dd>
1461<p>Checksums of the license text in the recipe source code.</p>
1462<p>This variable tracks changes in license text of the source
1463 code files.
1464 If the license text is changed, it will trigger a build
1465 failure, which gives the developer an opportunity to review any
1466 license change.</p>
1467<p>
1468 This variable must be defined for all recipes (unless <code class="filename">LICENSE</code>
1469 is set to "CLOSED")</p>
1470<p>For more information, see the
1471 <a class="link" href="usingpoky-configuring-LIC_FILES_CHKSUM.html" title="3.4.1. Tracking License Changes">
1472 Tracking License Changes</a> section</p>
1473</dd>
1474<dt>
1475<a name="var-LICENSE"></a>LICENSE</dt>
1476<dd>
1477<p>
1478 The list of source licenses for the recipe.
1479 Follow these rules:
1480 </p>
1481<div class="itemizedlist"><ul class="itemizedlist" type="disc">
1482<li class="listitem"><p>Do not use spaces within individual
1483 license names.</p></li>
1484<li class="listitem"><p>Separate license names using
1485 | (pipe) when there is a choice between licenses.
1486 </p></li>
1487<li class="listitem"><p>Separate license names using
1488 &amp; (ampersand) when multiple licenses exist
1489 that cover different parts of the source.
1490 </p></li>
1491<li class="listitem"><p>You can use spaces between license
1492 names.</p></li>
1493</ul></div>
1494<p>
1495 </p>
1496<p>
1497 Here are some examples:
1498 </p>
1499<pre class="literallayout">
1500 LICENSE = "LGPLv2.1 | GPLv3"
1501 LICENSE = "MPL-1 &amp; LGPLv2.1"
1502 LICENSE = "GPLv2+"
1503 </pre>
1504<p>
1505 The first example is from the recipes for Qt, which the user
1506 may choose to distribute under either the LGPL version
1507 2.1 or GPL version 3.
1508 The second example is from Cairo where two licenses cover
1509 different parts of the source code.
1510 The final example is from <code class="filename">sysstat</code>,
1511 which presents a single license.
1512 </p>
1513</dd>
1514<dt>
1515<a name="var-LICENSE_PATH"></a>LICENSE_PATH</dt>
1516<dd>
1517<p>Path to additional licenses used during the build.
1518 By default, the OpenEmbedded build system uses <code class="filename">COMMON_LICENSE_DIR</code>
1519 to define the directory that holds common license text used during the build.
1520 The <code class="filename">LICENSE_PATH</code> variable allows you to extend that
1521 location to other areas that have additional licenses:
1522 </p>
1523<pre class="literallayout">
1524 LICENSE_PATH += "/path/to/additional/common/licenses"
1525 </pre>
1526</dd>
1527</dl>
1528</div>
1529<div class="glossdiv" title="M">
1530<h3 class="title">M</h3>
1531<dl>
1532<dt>
1533<a name="var-MACHINE"></a>MACHINE</dt>
1534<dd>
1535<p>
1536 Specifies the target device for which the image is built.
1537 You define <code class="filename">MACHINE</code> in the
1538 <code class="filename">local.conf</code> file found in the
1539 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
1540 By default, <code class="filename">MACHINE</code> is set to
1541 "qemux86", which is an x86-based architecture machine to
1542 be emulated using QEMU:
1543 </p>
1544<pre class="literallayout">
1545 MACHINE ?= "qemux86"
1546 </pre>
1547<p>
1548 The variable corresponds to a machine configuration file of the
1549 same name, through which machine-specific configurations are set.
1550 Thus, when <code class="filename">MACHINE</code> is set to "qemux86" there
1551 exists the corresponding <code class="filename">qemux86.conf</code> machine
1552 configuration file, which can be found in the
1553 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>
1554 in <code class="filename">meta/conf/machine</code>.
1555 </p>
1556<p>
1557 The list of machines supported by the Yocto Project as
1558 shipped include the following:
1559 </p>
1560<pre class="literallayout">
1561 MACHINE ?= "qemuarm"
1562 MACHINE ?= "qemumips"
1563 MACHINE ?= "qemuppc"
1564 MACHINE ?= "qemux86"
1565 MACHINE ?= "qemux86-64"
1566 MACHINE ?= "atom-pc"
1567 MACHINE ?= "beagleboard"
1568 MACHINE ?= "mpc8315e-rdb"
1569 MACHINE ?= "routerstationpro"
1570 </pre>
1571<p>
1572 The last four are Yocto Project reference hardware boards, which
1573 are provided in the <code class="filename">meta-yocto-bsp</code> layer.
1574 </p>
1575<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
1576<h3 class="title">Note</h3>Adding additional Board Support Package (BSP) layers
1577 to your configuration adds new possible settings for
1578 <code class="filename">MACHINE</code>.
1579 </div>
1580<p>
1581 </p>
1582</dd>
1583<dt>
1584<a name="var-MACHINE_ESSENTIAL_EXTRA_RDEPENDS"></a>MACHINE_ESSENTIAL_EXTRA_RDEPENDS</dt>
1585<dd>
1586<p></p>
1587<p>
1588 A list of required machine-specific packages to install as part of
1589 the image being built.
1590 The build process depends on these packages being present.
1591 Furthermore, because this is a "machine essential" variable, the list of
1592 packages are essential for the machine to boot.
1593 The impact of this variable affects images based on
1594 <code class="filename">packagegroup-core-boot</code>,
1595 including the <code class="filename">core-image-minimal</code> image.
1596 </p>
1597<p>
1598 This variable is similar to the
1599 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS" title="MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS">MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</a></code>
1600 variable with the exception that the image being built has a build
1601 dependency on the variable's list of packages.
1602 In other words, the image will not build if a file in this list is not found.
1603 </p>
1604<p>
1605 As an example, suppose the machine for which you are building requires
1606 <code class="filename">example-init</code> to be run during boot to initialize the hardware.
1607 In this case, you would use the following in the machine's
1608 <code class="filename">.conf</code> configuration file:
1609 </p>
1610<pre class="literallayout">
1611 MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "example-init"
1612 </pre>
1613<p>
1614 </p>
1615</dd>
1616<dt>
1617<a name="var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS"></a>MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</dt>
1618<dd>
1619<p></p>
1620<p>
1621 A list of recommended machine-specific packages to install as part of
1622 the image being built.
1623 The build process does not depend on these packages being present.
1624 However, because this is a "machine essential" variable, the list of
1625 packages are essential for the machine to boot.
1626 The impact of this variable affects images based on
1627 <code class="filename">packagegroup-core-boot</code>,
1628 including the <code class="filename">core-image-minimal</code> image.
1629 </p>
1630<p>
1631 This variable is similar to the
1632 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_ESSENTIAL_EXTRA_RDEPENDS" title="MACHINE_ESSENTIAL_EXTRA_RDEPENDS">MACHINE_ESSENTIAL_EXTRA_RDEPENDS</a></code>
1633 variable with the exception that the image being built does not have a build
1634 dependency on the variable's list of packages.
1635 In other words, the image will still build if a package in this list is not found.
1636 Typically, this variable is used to handle essential kernel modules, whose
1637 functionality may be selected to be built into the kernel rather than as a module,
1638 in which case a package will not be produced.
1639 </p>
1640<p>
1641 Consider an example where you have a custom kernel where a specific touchscreen
1642 driver is required for the machine to be usable.
1643 However, the driver can be built as a module or
1644 into the kernel depending on the kernel configuration.
1645 If the driver is built as a module, you want it to be installed.
1646 But, when the driver is built into the kernel, you still want the
1647 build to succeed.
1648 This variable sets up a "recommends" relationship so that in the latter case,
1649 the build will not fail due to the missing package.
1650 To accomplish this, assuming the package for the module was called
1651 <code class="filename">kernel-module-ab123</code>, you would use the
1652 following in the machine's <code class="filename">.conf</code> configuration
1653 file:
1654 </p>
1655<pre class="literallayout">
1656 MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-ab123"
1657 </pre>
1658<p>
1659 </p>
1660<p>
1661 Some examples of these machine essentials are flash, screen, keyboard, mouse,
1662 or touchscreen drivers (depending on the machine).
1663 </p>
1664</dd>
1665<dt>
1666<a name="var-MACHINE_EXTRA_RDEPENDS"></a>MACHINE_EXTRA_RDEPENDS</dt>
1667<dd>
1668<p>
1669 A list of machine-specific packages to install as part of the
1670 image being built that are not essential for the machine to boot.
1671 However, the build process for more fully-featured images
1672 depends on the packages being present.
1673 </p>
1674<p>
1675 This variable affects all images based on
1676 <code class="filename">packagegroup-base</code>, which does not include the
1677 <code class="filename">core-image-minimal</code> or <code class="filename">core-image-basic</code>
1678 images.
1679 </p>
1680<p>
1681 The variable is similar to the
1682 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_EXTRA_RRECOMMENDS" title="MACHINE_EXTRA_RRECOMMENDS">MACHINE_EXTRA_RRECOMMENDS</a></code>
1683 variable with the exception that the image being built has a build
1684 dependency on the variable's list of packages.
1685 In other words, the image will not build if a file in this list is not found.
1686 </p>
1687<p>
1688 An example is a machine that has WiFi capability but is not essential
1689 For the machine to boot the image.
1690 However, if you are building a more fully-featured image, you want to enable
1691 the WiFi.
1692 The package containing the firmware for the WiFi hardware is always
1693 expected to exist, so it is acceptable for the build process to depend upon
1694 finding the package.
1695 In this case, assuming the package for the firmware was called
1696 <code class="filename">wifidriver-firmware</code>, you would use the following in the
1697 <code class="filename">.conf</code> file for the machine:
1698 </p>
1699<pre class="literallayout">
1700 MACHINE_EXTRA_RDEPENDS += "wifidriver-firmware"
1701 </pre>
1702<p>
1703 </p>
1704</dd>
1705<dt>
1706<a name="var-MACHINE_EXTRA_RRECOMMENDS"></a>MACHINE_EXTRA_RRECOMMENDS</dt>
1707<dd>
1708<p></p>
1709<p>
1710 A list of machine-specific packages to install as part of the
1711 image being built that are not essential for booting the machine.
1712 The image being built has no build dependency on this list of packages.
1713 </p>
1714<p>
1715 This variable affects only images based on
1716 <code class="filename">packagegroup-base</code>, which does not include the
1717 <code class="filename">core-image-minimal</code> or <code class="filename">core-image-basic</code>
1718 images.
1719 </p>
1720<p>
1721 This variable is similar to the
1722 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_EXTRA_RDEPENDS" title="MACHINE_EXTRA_RDEPENDS">MACHINE_EXTRA_RDEPENDS</a></code>
1723 variable with the exception that the image being built does not have a build
1724 dependency on the variable's list of packages.
1725 In other words, the image will build if a file in this list is not found.
1726 </p>
1727<p>
1728 An example is a machine that has WiFi capability but is not essential
1729 For the machine to boot the image.
1730 However, if you are building a more fully-featured image, you want to enable
1731 WiFi.
1732 In this case, the package containing the WiFi kernel module will not be produced
1733 if the WiFi driver is built into the kernel, in which case you still want the
1734 build to succeed instead of failing as a result of the package not being found.
1735 To accomplish this, assuming the package for the module was called
1736 <code class="filename">kernel-module-examplewifi</code>, you would use the
1737 following in the <code class="filename">.conf</code> file for the machine:
1738 </p>
1739<pre class="literallayout">
1740 MACHINE_EXTRA_RRECOMMENDS += "kernel-module-examplewifi"
1741 </pre>
1742<p>
1743 </p>
1744</dd>
1745<dt>
1746<a name="var-MACHINE_FEATURES"></a>MACHINE_FEATURES</dt>
1747<dd>
1748<p>Specifies the list of hardware features the
1749 <a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE">MACHINE</a> supports.
1750 For example, including the "bluetooth" feature causes the
1751 <code class="filename">bluez</code> bluetooth daemon to be built and
1752 added to the image.
1753 It also causes the <code class="filename">connman</code> recipe
1754 to look at <code class="filename">MACHINE_FEATURES</code> and when it
1755 finds "bluetooth" there it enables the bluetooth
1756 support in ConnMan.
1757 </p>
1758<p>
1759 For a list of features supported by the Yocto Project as shipped,
1760 see the "<a class="link" href="ref-features-machine.html" title="9.2. Machine">Machine</a>" section.
1761 </p>
1762</dd>
1763<dt>
1764<a name="var-MACHINE_FEATURES_BACKFILL"></a>MACHINE_FEATURES_BACKFILL</dt>
1765<dd>
1766<p>Features to be added to
1767 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES">MACHINE_FEATURES</a></code>
1768 if not also present in
1769 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES_BACKFILL_CONSIDERED" title="MACHINE_FEATURES_BACKFILL_CONSIDERED">MACHINE_FEATURES_BACKFILL_CONSIDERED</a></code>.
1770 </p>
1771<p>
1772 This variable is set in the <code class="filename">meta/conf/bitbake.conf</code> file.
1773 It is not intended to be user-configurable.
1774 It is best to just reference the variable to see which machine features are
1775 being backfilled for all machine configurations.
1776 See the <a class="link" href="ref-features-backfill.html" title="9.4. Feature Backfilling">Feature backfilling</a> section for
1777 more information.
1778 </p>
1779</dd>
1780<dt>
1781<a name="var-MACHINE_FEATURES_BACKFILL_CONSIDERED"></a>MACHINE_FEATURES_BACKFILL_CONSIDERED</dt>
1782<dd><p>Features from
1783 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES_BACKFILL" title="MACHINE_FEATURES_BACKFILL">MACHINE_FEATURES_BACKFILL</a></code>
1784 that should not be backfilled (i.e. added to
1785 <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES">MACHINE_FEATURES</a></code>)
1786 during the build.
1787 See the <a class="link" href="ref-features-backfill.html" title="9.4. Feature Backfilling">Feature backfilling</a> section for
1788 more information.
1789 </p></dd>
1790<dt>
1791<a name="var-MAINTAINER"></a>MAINTAINER</dt>
1792<dd><p>The email address of the distribution maintainer.</p></dd>
1793<dt>
1794<a name="var-MLPREFIX"></a>MLPREFIX</dt>
1795<dd><p>
1796 Specifies a prefix has been added to
1797 <a class="link" href="ref-variables-glos.html#var-PN" title="PN"><code class="filename">PN</code></a> to create a special version
1798 of a recipe or package, such as a multilib version.
1799 The variable is used in places where the prefix needs to be
1800 added to or removed from a the name (e.g. the
1801 <a class="link" href="ref-variables-glos.html#var-BPN" title="BPN"><code class="filename">BPN</code></a> variable).
1802 <code class="filename">MLPREFIX</code> gets set when a prefix has been
1803 added to <code class="filename">PN</code>.
1804 </p></dd>
1805<dt>
1806<a name="var-MULTIMACH_TARGET_SYS"></a>MULTIMACH_TARGET_SYS</dt>
1807<dd><p>
1808 Separates files for different machines such that you can build
1809 for multiple target machines using the same output directories.
1810 See the <a class="link" href="ref-variables-glos.html#var-STAMP" title="STAMP"><code class="filename">STAMP</code></a> variable
1811 for an example.
1812 </p></dd>
1813</dl>
1814</div>
1815<div class="glossdiv" title="O">
1816<h3 class="title">O</h3>
1817<dl>
1818<dt>
1819<a name="var-OE_TERMINAL"></a>OE_TERMINAL</dt>
1820<dd>
1821<p>
1822 Controls how the OpenEmbedded build system spawns
1823 interactive terminals on the host development system
1824 (e.g. using the BitBake command with the
1825 <code class="filename">-c devshell</code> command-line option).
1826 For more information, see the
1827 "<a class="link" href="../dev-manual/platdev-appdev-devshell.html" target="_self">Using a Development Shell</a>" section
1828 in the Yocto Project Development Manual.
1829 </p>
1830<p>
1831 You can use the following values for the
1832 <code class="filename">OE_TERMINAL</code> variable:
1833 </p>
1834<pre class="literallayout">
1835 auto
1836 gnome
1837 xfce
1838 rxvt
1839 screen
1840 konsole
1841 none
1842 </pre>
1843<p>
1844 </p>
1845<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
1846<h3 class="title">Note</h3>Konsole support only works for KDE 3.x.
1847 Also, "auto" is the default behavior for
1848 <code class="filename">OE_TERMINAL</code>
1849</div>
1850<p>
1851 </p>
1852</dd>
1853</dl>
1854</div>
1855<div class="glossdiv" title="P">
1856<h3 class="title">P</h3>
1857<dl>
1858<dt>
1859<a name="var-P"></a>P</dt>
1860<dd>
1861<p>The recipe name and version.
1862 <code class="filename">P</code> is comprised of the following:
1863 </p>
1864<pre class="literallayout">
1865 ${PN}-${PV}
1866 </pre>
1867</dd>
1868<dt>
1869<a name="var-PACKAGE_ARCH"></a>PACKAGE_ARCH</dt>
1870<dd><p>The architecture of the resulting package or packages.</p></dd>
1871<dt>
1872<a name="var-PACKAGE_BEFORE_PN"></a>PACKAGE_BEFORE_PN</dt>
1873<dd><p>Enables easily adding packages to
1874 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGES" title="PACKAGES">PACKAGES</a></code>
1875 before <code class="filename">${PN}</code> so that the packages can pick
1876 up files that would normally be included in the default package.</p></dd>
1877<dt>
1878<a name="var-PACKAGE_CLASSES"></a>PACKAGE_CLASSES</dt>
1879<dd>
1880<p>This variable, which is set in the <code class="filename">local.conf</code> configuration
1881 file found in the <code class="filename">conf</code> folder of the
1882 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>,
1883 specifies the package manager to use when packaging data.
1884 You can provide one or more arguments for the variable with the first
1885 argument being the package manager used to create images:
1886 </p>
1887<pre class="literallayout">
1888 PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
1889 </pre>
1890<p>
1891 For information on build performance effects as a result of the
1892 package manager use, see
1893 <a class="link" href="ref-classes-package.html" title="7.13. Packaging - package*.bbclass">Packaging - <code class="filename">package*.bbclass</code></a>
1894 in this manual.
1895 </p>
1896</dd>
1897<dt>
1898<a name="var-PACKAGE_EXTRA_ARCHS"></a>PACKAGE_EXTRA_ARCHS</dt>
1899<dd><p>Specifies the list of architectures compatible with the device CPU.
1900 This variable is useful when you build for several different devices that use
1901 miscellaneous processors such as XScale and ARM926-EJS).</p></dd>
1902<dt>
1903<a name="var-PACKAGECONFIG"></a>PACKAGECONFIG</dt>
1904<dd>
1905<p>
1906 This variable provides a means of enabling or disabling
1907 features of a recipe on a per-recipe basis.
1908 The <code class="filename">PACKAGECONFIG</code>
1909 variable itself specifies a space-separated list of the
1910 features to enable.
1911 The features themselves are specified as flags on the
1912 <code class="filename">PACKAGECONFIG</code> variable.
1913 You can provide up to four arguments, which are separated by
1914 commas, to determine the behavior of each feature
1915 when it is enabled or disabled.
1916 You can omit any argument you like but must retain the
1917 separating commas.
1918 The arguments specify the following:
1919 </p>
1920<div class="orderedlist"><ol class="orderedlist" type="1">
1921<li class="listitem"><p>Extra arguments
1922 that should be added to the configure script argument list
1923 (<a class="link" href="ref-variables-glos.html#var-EXTRA_OECONF" title="EXTRA_OECONF"><code class="filename">EXTRA_OECONF</code></a>)
1924 if the feature is enabled.</p></li>
1925<li class="listitem"><p>Extra arguments
1926 that should be added to <code class="filename">EXTRA_OECONF</code>
1927 if the feature is disabled.
1928 </p></li>
1929<li class="listitem"><p>Additional build dependencies
1930 (<a class="link" href="ref-variables-glos.html#var-DEPENDS" title="DEPENDS"><code class="filename">DEPENDS</code></a>)
1931 that should be added if the feature is enabled.
1932 </p></li>
1933<li class="listitem"><p>Additional runtime dependencies
1934 (<a class="link" href="ref-variables-glos.html#var-RDEPENDS" title="RDEPENDS"><code class="filename">RDEPENDS</code></a>)
1935 that should be added if the feature is enabled.
1936 </p></li>
1937</ol></div>
1938<p>
1939 </p>
1940<p>
1941 Consider the following example taken from the
1942 <code class="filename">librsvg</code> recipe.
1943 In this example the feature is <code class="filename">croco</code>, which
1944 has three arguments that determine the feature's behavior.
1945 </p>
1946<pre class="literallayout">
1947 PACKAGECONFIG ??= "croco"
1948 PACKAGECONFIG[croco] = "--with-croco,--without-croco,libcroco"
1949 </pre>
1950<p>
1951 The <code class="filename">--with-croco</code> and
1952 <code class="filename">libcroco</code> arguments apply only if
1953 the feature is enabled.
1954 In this case, <code class="filename">--with-croco</code> is
1955 added to the configure script argument list and
1956 <code class="filename">libcroco</code> is added to
1957 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEPENDS" title="DEPENDS">DEPENDS</a></code>.
1958 On the other hand, if the feature is disabled say through
1959 a <code class="filename">.bbappend</code> file in another layer, then
1960 the second argument <code class="filename">--without-croco</code> is
1961 added to the configure script rather than
1962 <code class="filename">--with-croco</code>.
1963 </p>
1964</dd>
1965<dt>
1966<a name="var-PACKAGES"></a>PACKAGES</dt>
1967<dd>
1968<p>The list of packages to be created from the recipe.
1969 The default value is the following:
1970 </p>
1971<pre class="literallayout">
1972 ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}
1973 </pre>
1974</dd>
1975<dt>
1976<a name="var-PACKAGES_DYNAMIC"></a>PACKAGES_DYNAMIC</dt>
1977<dd>
1978<p>
1979 A promise that your recipe satisfies runtime dependencies
1980 for optional modules that are found in other recipes.
1981 <code class="filename">PACKAGES_DYNAMIC</code>
1982 does not actually satisfy the dependencies, it only states that
1983 they should be satisfied.
1984 For example, if a hard, runtime dependency
1985 (<code class="filename">RDEPENDS</code>) of another package is satisfied
1986 at build time through the <code class="filename">PACKAGES_DYNAMIC</code>
1987 variable, but a package with the module name is never actually
1988 produced, then the other package will be broken.
1989 Thus, if you attempt to include that package in an image,
1990 you will get a dependency failure from the packaging system
1991 during <code class="filename">do_rootfs</code>.
1992 Typically, if there is a chance that such a situation can
1993 occur and the package that is not created is valid
1994 without the dependency being satisfied, then you should use
1995 <code class="filename">RRECOMMENDS</code> (a soft runtime dependency)
1996 instead of <code class="filename">RDEPENDS</code>.
1997 </p>
1998<p>
1999 For an example of how to use the <code class="filename">PACKAGES_DYNAMIC</code>
2000 variable when you are splitting packages, see the
2001 "<a class="link" href="../dev-manual/handling-optional-module-packaging.html" target="_self">Handling Optional Module Packaging</a>" section
2002 in the Yocto Project Development Manual.
2003 </p>
2004</dd>
2005<dt>
2006<a name="var-PARALLEL_MAKE"></a>PARALLEL_MAKE</dt>
2007<dd><p>Specifies extra options that are passed to the <code class="filename">make</code> command during the
2008 compile tasks.
2009 This variable is usually in the form <code class="filename">-j 4</code>, where the number
2010 represents the maximum number of parallel threads make can run.
2011 If you development host supports multiple cores a good rule of thumb is to set
2012 this variable to twice the number of cores on the host.</p></dd>
2013<dt>
2014<a name="var-PF"></a>PF</dt>
2015<dd>
2016<p>Specifies the recipe or package name and includes all version and revision
2017 numbers (i.e. <code class="filename">eglibc-2.13-r20+svnr15508/</code> and
2018 <code class="filename">bash-4.2-r1/</code>).
2019 This variable is comprised of the following:
2020 </p>
2021<pre class="literallayout">
2022 ${PN}-${EXTENDPE}${PV}-${PR}
2023 </pre>
2024</dd>
2025<dt>
2026<a name="var-PN"></a>PN</dt>
2027<dd>
2028<p>This variable can have two separate functions depending on the context: a recipe
2029 name or a resulting package name.</p>
2030<p><code class="filename">PN</code> refers to a recipe name in the context of a file used
2031 by the OpenEmbedded build system as input to create a package.
2032 The name is normally extracted from the recipe file name.
2033 For example, if the recipe is named
2034 <code class="filename">expat_2.0.1.bb</code>, then the default value of <code class="filename">PN</code>
2035 will be "expat".</p>
2036<p>
2037 The variable refers to a package name in the context of a file created or produced by the
2038 OpenEmbedded build system.</p>
2039<p>If applicable, the <code class="filename">PN</code> variable also contains any special
2040 suffix or prefix.
2041 For example, using <code class="filename">bash</code> to build packages for the native
2042 machine, <code class="filename">PN</code> is <code class="filename">bash-native</code>.
2043 Using <code class="filename">bash</code> to build packages for the target and for Multilib,
2044 <code class="filename">PN</code> would be <code class="filename">bash</code> and
2045 <code class="filename">lib64-bash</code>, respectively.
2046 </p>
2047</dd>
2048<dt>
2049<a name="var-PR"></a>PR</dt>
2050<dd><p>The revision of the recipe.
2051 The default value for this variable is "r0".
2052 </p></dd>
2053<dt>
2054<a name="var-PRINC"></a>PRINC</dt>
2055<dd>
2056<p>Causes the <code class="filename">PR</code> variable of
2057 <code class="filename">.bbappend</code> files to dynamically increment.
2058 This increment minimizes the impact of layer ordering.</p>
2059<p>In order to ensure multiple <code class="filename">.bbappend</code> files can co-exist,
2060 <code class="filename">PRINC</code> should be self referencing.
2061 This variable defaults to 0.</p>
2062<p>Following is an example that increments <code class="filename">PR</code> by two:
2063 </p>
2064<pre class="literallayout">
2065 PRINC := "${@int(PRINC) + 2}"
2066 </pre>
2067<p>
2068 It is adviseable not to use strings such as ".= '.1'" with the variable because
2069 this usage is very sensitive to layer ordering.
2070 Explicit assignments should be avoided as they cannot adequately represent multiple
2071 <code class="filename">.bbappend</code> files.</p>
2072</dd>
2073<dt>
2074<a name="var-PV"></a>PV</dt>
2075<dd><p>The version of the recipe.
2076 The version is normally extracted from the recipe filename.
2077 For example, if the recipe is named
2078 <code class="filename">expat_2.0.1.bb</code>, then the default value of <code class="filename">PV</code>
2079 will be "2.0.1".
2080 <code class="filename">PV</code> is generally not overridden within
2081 a recipe unless it is building an unstable (i.e. development) version from a source code repository
2082 (e.g. Git or Subversion).
2083 </p></dd>
2084<dt>
2085<a name="var-PE"></a>PE</dt>
2086<dd><p>
2087 the epoch of the recipe.
2088 The default value is "0".
2089 The field is used to make upgrades possible when the versioning scheme changes in
2090 some backwards incompatible way.
2091 </p></dd>
2092<dt>
2093<a name="var-PREFERRED_PROVIDER"></a>PREFERRED_PROVIDER</dt>
2094<dd>
2095<p>
2096 If multiple recipes provide an item, this variable
2097 determines which recipe should be given preference.
2098 The variable must always be suffixed with the name of the
2099 provided item, and should be set to the
2100 <code class="filename">PN</code> of the recipe
2101 to which you want to give precedence.
2102 Here is an example:
2103 </p>
2104<pre class="literallayout">
2105 PREFERRED_PROVIDER_virtual/xserver = "xserver-xf86"
2106 </pre>
2107<p>
2108 </p>
2109</dd>
2110<dt>
2111<a name="var-PREFERRED_VERSION"></a>PREFERRED_VERSION</dt>
2112<dd>
2113<p>
2114 If there are multiple versions of recipes available, this
2115 variable determines which recipe should be given preference.
2116 The variable must always be suffixed with the <code class="filename">PN</code>
2117 for which to select, and should be set to the
2118 <code class="filename">PV</code> to which you want to give precedence.
2119 You can use the "<code class="filename">%</code>" character as a wildcard
2120 to match any number of characters, which can be useful when
2121 specifying versions that contain long revision number that could
2122 potentially change.
2123 Here are two examples:
2124 </p>
2125<pre class="literallayout">
2126 PREFERRED_VERSION_python = "2.6.6"
2127 PREFERRED_VERSION_linux-yocto = "3.0+git%"
2128 </pre>
2129<p>
2130 </p>
2131</dd>
2132</dl>
2133</div>
2134<div class="glossdiv" title="R">
2135<h3 class="title">R</h3>
2136<dl>
2137<dt>
2138<a name="var-RCONFLICTS"></a>RCONFLICTS</dt>
2139<dd>
2140<p>The list of packages that conflict with a package.
2141 Note that the package will not be installed if the conflicting packages are not
2142 first removed.</p>
2143<p>
2144 Like all package-controlling variables, you must always use them in
2145 conjunction with a package name override.
2146 Here is an example:
2147 </p>
2148<pre class="literallayout">
2149 RCONFLICTS_${PN} = "another-conflicting-package-name"
2150 </pre>
2151<p>
2152 </p>
2153</dd>
2154<dt>
2155<a name="var-RDEPENDS"></a>RDEPENDS</dt>
2156<dd>
2157<p>
2158 Lists a package's run-time dependencies (i.e. other packages)
2159 that must be installed for the package to be built.
2160 In other words, in order for the package to be built and
2161 run correctly, it depends on the listed packages.
2162 If a package in this list cannot be found, it is probable
2163 that a dependency error would occur before the build.
2164 </p>
2165<p>
2166 The names of the variables you list with
2167 <code class="filename">RDEPENDS</code> must be the names of other
2168 packages as listed in the
2169 <a class="link" href="ref-variables-glos.html#var-PACKAGES" title="PACKAGES"><code class="filename">PACKAGES</code></a>
2170 variable.
2171 You should not list recipe names (<code class="filename">PN</code>).
2172 </p>
2173<p>
2174 Because the <code class="filename">RDEPENDS</code> variable applies
2175 to packages being built, you should
2176 always attach a package name to the variable to specify the
2177 particular run-time package that has the dependency.
2178 For example, suppose you are building a development package
2179 that depends on the <code class="filename">perl</code> package.
2180 In this case, you would use the following
2181 <code class="filename">RDEPENDS</code> statement:
2182 </p>
2183<pre class="literallayout">
2184 RDEPENDS_${PN}-dev += "perl"
2185 </pre>
2186<p>
2187 In the example, the package name
2188 (<code class="filename">${PN}-dev</code>) must appear as it would
2189 in the
2190 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGES" title="PACKAGES">PACKAGES</a></code>
2191 namespace before any renaming of the output package by
2192 classes like <code class="filename">debian.bbclass</code>.
2193 </p>
2194<p>
2195 In many cases you do not need to explicitly add dependencies
2196 to <code class="filename">RDEPENDS</code> since some automatic
2197 handling occurs:
2198 </p>
2199<div class="itemizedlist"><ul class="itemizedlist" type="disc">
2200<li class="listitem"><p><span class="emphasis"><em><code class="filename">shlibdeps</code></em></span>: If
2201 a run-time package contains a shared library
2202 (<code class="filename">.so</code>), the build
2203 processes the library in order to determine other
2204 libraries to which it is dynamically linked.
2205 The build process adds these libraries to
2206 <code class="filename">RDEPENDS</code> when creating the run-time
2207 package.</p></li>
2208<li class="listitem"><p><span class="emphasis"><em><code class="filename">pcdeps</code></em></span>: If
2209 the package ships a <code class="filename">pkg-config</code>
2210 information file, the build process uses this file
2211 to add items to the <code class="filename">RDEPENDS</code>
2212 variable to create the run-time packages.
2213 </p></li>
2214</ul></div>
2215<p>
2216 </p>
2217</dd>
2218<dt>
2219<a name="var-RRECOMMENDS"></a>RRECOMMENDS</dt>
2220<dd>
2221<p>
2222 A list of packages that extend the usability of a package being
2223 built.
2224 The package being built does not depend on this list of packages in
2225 order to successfully build, but needs them for the extended usability.
2226 To specify runtime dependencies for packages, see the
2227 <code class="filename"><a class="link" href="ref-variables-glos.html#var-RDEPENDS" title="RDEPENDS">RDEPENDS</a></code> variable.
2228 </p>
2229<p>
2230 The OpenEmbedded build process automatically installs the list of packages
2231 as part of the built package.
2232 However, you can remove them later if you want.
2233 If, during the build, a package from the list cannot be found, the build
2234 process continues without an error.
2235 </p>
2236<p>
2237 Because the <code class="filename">RRECOMMENDS</code> variable applies to packages
2238 being built, you should
2239 always attach an override to the variable to specify the particular package
2240 whose usability is being extended.
2241 For example, suppose you are building a development package that is extended
2242 to support wireless functionality.
2243 In this case, you would use the following:
2244 </p>
2245<pre class="literallayout">
2246 RRECOMMENDS_${PN}-dev += "&lt;wireless_package_name&gt;"
2247 </pre>
2248<p>
2249 In the example, the package name (<code class="filename">${PN}-dev</code>) must
2250 appear as it would in the
2251 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGES" title="PACKAGES">PACKAGES</a></code> namespace before any
2252 renaming of the output package by classes like <code class="filename">debian.bbclass</code>.
2253 </p>
2254</dd>
2255<dt>
2256<a name="var-RREPLACES"></a>RREPLACES</dt>
2257<dd><p>The list of packages that are replaced with this package.</p></dd>
2258</dl>
2259</div>
2260<div class="glossdiv" title="S">
2261<h3 class="title">S</h3>
2262<dl>
2263<dt>
2264<a name="var-S"></a>S</dt>
2265<dd>
2266<p>
2267 The location in the <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>
2268 where unpacked package source code resides.
2269 This location is within the working directory
2270 (<code class="filename"><a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">WORKDIR</a></code>), which
2271 is not static.
2272 The unpacked source location depends on the package name
2273 (<code class="filename"><a class="link" href="ref-variables-glos.html#var-PN" title="PN">PN</a></code>) and
2274 package version (<code class="filename"><a class="link" href="ref-variables-glos.html#var-PV" title="PV">PV</a></code>) as
2275 follows:
2276 </p>
2277<pre class="literallayout">
2278 ${WORKDIR}/${PN}-${PV}
2279 </pre>
2280<p>
2281 As an example, assume a
2282 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a> top-level
2283 folder named <code class="filename">poky</code>
2284 and a default <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>
2285 at <code class="filename">poky/build</code>.
2286 In this case, the working directory the build system uses to build
2287 the <code class="filename">db</code> package is the following:
2288 </p>
2289<pre class="literallayout">
2290 ~/poky/build/tmp/work/qemux86-poky-linux/db-5.1.19-r3/db-5.1.19
2291 </pre>
2292<p>
2293 </p>
2294</dd>
2295<dt>
2296<a name="var-SDKIMAGE_FEATURES"></a>SDKIMAGE_FEATURES</dt>
2297<dd><p>Equivalent to
2298 <code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FEATURES" title="IMAGE_FEATURES">IMAGE_FEATURES</a></code>.
2299 However, this variable applies to the SDK generated from an image using
2300 <code class="filename">bitbake -c populate_sdk imagename</code>).
2301 </p></dd>
2302<dt>
2303<a name="var-SECTION"></a>SECTION</dt>
2304<dd><p>The section in which packages should be categorized.
2305 Package management utilities can make use of this variable.</p></dd>
2306<dt>
2307<a name="var-SELECTED_OPTIMIZATION"></a>SELECTED_OPTIMIZATION</dt>
2308<dd><p>
2309 The variable takes the value of
2310 <code class="filename"><a class="link" href="ref-variables-glos.html#var-FULL_OPTIMIZATION" title="FULL_OPTIMIZATION">FULL_OPTIMIZATION</a></code>
2311 unless <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEBUG_BUILD" title="DEBUG_BUILD">DEBUG_BUILD</a></code> = "1".
2312 In this case the value of
2313 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DEBUG_OPTIMIZATION" title="DEBUG_OPTIMIZATION">DEBUG_OPTIMIZATION</a></code> is used.
2314 </p></dd>
2315<dt>
2316<a name="var-SERIAL_CONSOLE"></a>SERIAL_CONSOLE</dt>
2317<dd><p>The speed and device for the serial port used to attach the serial console.
2318 This variable is given to the kernel as the "console"
2319 parameter and after booting occurs <code class="filename">getty</code> is started on that port
2320 so remote login is possible.</p></dd>
2321<dt>
2322<a name="var-SITEINFO_ENDIANNESS"></a>SITEINFO_ENDIANNESS</dt>
2323<dd><p>
2324 Specifies the endian byte order of the target system.
2325 The value should be either "le" for little-endian or "be" for big-endian.
2326 </p></dd>
2327<dt>
2328<a name="var-SITEINFO_BITS"></a>SITEINFO_BITS</dt>
2329<dd><p>
2330 Specifies the number of bits for the target system CPU.
2331 The value should be either "32" or "64".
2332 </p></dd>
2333<dt>
2334<a name="var-SPECIAL_PKGSUFFIX"></a>SPECIAL_PKGSUFFIX</dt>
2335<dd><p>
2336 A list of prefixes for <a class="link" href="ref-variables-glos.html#var-PN" title="PN"><code class="filename">PN</code></a> used by the
2337 OpenEmbedded build system to create variants of recipes or packages.
2338 The list specifies the prefixes to strip off during certain circumstances
2339 such as the generation of the <a class="link" href="ref-variables-glos.html#var-BPN" title="BPN"><code class="filename">BPN</code></a> variable.
2340 </p></dd>
2341<dt>
2342<a name="var-SRC_URI"></a>SRC_URI</dt>
2343<dd>
2344<p>The list of source files - local or remote.
2345 This variable tells the OpenEmbedded build system which bits to pull
2346 in for the build and how to pull them in.
2347 For example, if the recipe only needs to fetch a tarball from the
2348 internet, the recipe uses a single <code class="filename">SRC_URI</code> entry.
2349 On the other hand, if the recipe needs to fetch a tarball, apply
2350 two patches, and include a custom file, the recipe would include four
2351 instances of the variable.</p>
2352<p>The following list explains the available URI protocols:
2353 </p>
2354<div class="itemizedlist"><ul class="itemizedlist" type="disc">
2355<li class="listitem">
2356<p><span class="emphasis"><em><code class="filename">file://</code> -</em></span> Fetches files, which is usually
2357 a file shipped with the metadata, from the local machine.
2358 The path is relative to the
2359 <a class="link" href="ref-variables-glos.html#var-FILESPATH" title="FILESPATH"><code class="filename">FILESPATH</code></a>
2360 variable.
2361 Thus, the build system searches, in order, from the following directories,
2362 which are assumed to be a subdirectories of the directory in which the
2363 recipe file resides:
2364 </p>
2365<div class="itemizedlist"><ul class="itemizedlist" type="circle">
2366<li class="listitem"><p><span class="emphasis"><em><code class="filename">${PN}</code> -</em></span> The recipe name
2367 with any special suffix or prefix, if applicable.
2368 For example, using <code class="filename">bash</code> to build for the native
2369 machine, <code class="filename">PN</code> is <code class="filename">bash-native</code>.
2370 Using <code class="filename">bash</code> to build for the target and for Multilib,
2371 <code class="filename">PN</code> would be <code class="filename">bash</code> and
2372 <code class="filename">lib64-bash</code>, respectively.
2373 </p></li>
2374<li class="listitem"><p><span class="emphasis"><em><code class="filename">${PF}</code> - </em></span>
2375 <code class="filename">${PN}-${EXTENDPE}${PV}-${PR}</code>.
2376 The recipe name including all version and revision numbers
2377 (i.e. <code class="filename">eglibc-2.13-r20+svnr15508/</code> and
2378 <code class="filename">bash-4.2-r1/</code>).</p></li>
2379<li class="listitem"><p><span class="emphasis"><em><code class="filename">${P}</code> -</em></span>
2380 <code class="filename">${PN}-${PV}</code>.
2381 The recipe name and version (i.e. <code class="filename">bash-4.2</code>).
2382 </p></li>
2383<li class="listitem"><p><span class="emphasis"><em><code class="filename">${BPN}</code> -</em></span> The
2384 base recipe name without any special suffix or version numbers.
2385 </p></li>
2386<li class="listitem"><p><span class="emphasis"><em><code class="filename">${BP}</code> -</em></span>
2387 <code class="filename">${BPN}-${PV}</code>.
2388 The base recipe name and version but without any special
2389 package name suffix.</p></li>
2390<li class="listitem"><p><span class="emphasis"><em>Files -</em></span> Files beneath the directory in which the recipe
2391 resides.</p></li>
2392<li class="listitem"><p><span class="emphasis"><em>Directory -</em></span> The directory itself in which the recipe
2393 resides.</p></li>
2394</ul></div>
2395</li>
2396<li class="listitem"><p><span class="emphasis"><em><code class="filename">bzr://</code> -</em></span> Fetches files from a
2397 Bazaar revision control repository.</p></li>
2398<li class="listitem"><p><span class="emphasis"><em><code class="filename">git://</code> -</em></span> Fetches files from a
2399 Git revision control repository.</p></li>
2400<li class="listitem"><p><span class="emphasis"><em><code class="filename">osc://</code> -</em></span> Fetches files from
2401 an OSC (OpenSuse Build service) revision control repository.</p></li>
2402<li class="listitem"><p><span class="emphasis"><em><code class="filename">repo://</code> -</em></span> Fetches files from
2403 a repo (Git) repository.</p></li>
2404<li class="listitem"><p><span class="emphasis"><em><code class="filename">svk://</code> -</em></span> Fetches files from
2405 an SVK revision control repository.</p></li>
2406<li class="listitem"><p><span class="emphasis"><em><code class="filename">http://</code> -</em></span> Fetches files from
2407 the Internet using <code class="filename">http</code>.</p></li>
2408<li class="listitem"><p><span class="emphasis"><em><code class="filename">https://</code> -</em></span> Fetches files
2409 from the Internet using <code class="filename">https</code>.</p></li>
2410<li class="listitem"><p><span class="emphasis"><em><code class="filename">ftp://</code> -</em></span> Fetches files
2411 from the Internet using <code class="filename">ftp</code>.</p></li>
2412<li class="listitem"><p><span class="emphasis"><em><code class="filename">cvs://</code> -</em></span> Fetches files from
2413 a CVS revision control repository.</p></li>
2414<li class="listitem"><p><span class="emphasis"><em><code class="filename">hg://</code> -</em></span> Fetches files from
2415 a Mercurial (<code class="filename">hg</code>) revision control repository.</p></li>
2416<li class="listitem"><p><span class="emphasis"><em><code class="filename">p4://</code> -</em></span> Fetches files from
2417 a Perforce (<code class="filename">p4</code>) revision control repository.</p></li>
2418<li class="listitem"><p><span class="emphasis"><em><code class="filename">ssh://</code> -</em></span> Fetches files from
2419 a secure shell.</p></li>
2420<li class="listitem"><p><span class="emphasis"><em><code class="filename">svn://</code> -</em></span> Fetches files from
2421 a Subversion (<code class="filename">svn</code>) revision control repository.</p></li>
2422</ul></div>
2423<p>
2424 </p>
2425<p>Standard and recipe-specific options for <code class="filename">SRC_URI</code> exist.
2426 Here are standard options:
2427 </p>
2428<div class="itemizedlist"><ul class="itemizedlist" type="disc">
2429<li class="listitem"><p><span class="emphasis"><em><code class="filename">apply</code> -</em></span> Whether to apply
2430 the patch or not.
2431 The default action is to apply the patch.</p></li>
2432<li class="listitem"><p><span class="emphasis"><em><code class="filename">striplevel</code> -</em></span> Which
2433 striplevel to use when applying the patch.
2434 The default level is 1.</p></li>
2435</ul></div>
2436<p>
2437 </p>
2438<p>Here are options specific to recipes building code from a revision control system:
2439 </p>
2440<div class="itemizedlist"><ul class="itemizedlist" type="disc">
2441<li class="listitem"><p><span class="emphasis"><em><code class="filename">mindate</code> -</em></span> Only applies
2442 the patch if <a class="link" href="ref-variables-glos.html#var-SRCDATE" title="SRCDATE"><code class="filename">SRCDATE</code></a>
2443 is equal to or greater than <code class="filename">mindate</code>.</p></li>
2444<li class="listitem"><p><span class="emphasis"><em><code class="filename">maxdate</code> -</em></span> Only applies
2445 the patch if <a class="link" href="ref-variables-glos.html#var-SRCDATE" title="SRCDATE"><code class="filename">SRCDATE</code></a>
2446 is not later than <code class="filename">mindate</code>.</p></li>
2447<li class="listitem"><p><span class="emphasis"><em><code class="filename">minrev</code> -</em></span> Only applies
2448 the patch if <a class="link" href="ref-variables-glos.html#var-SRCREV" title="SRCREV"><code class="filename">SRCREV</code></a>
2449 is equal to or greater than <code class="filename">minrev</code>.</p></li>
2450<li class="listitem"><p><span class="emphasis"><em><code class="filename">maxrev</code> -</em></span> Only applies
2451 the patch if <a class="link" href="ref-variables-glos.html#var-SRCREV" title="SRCREV"><code class="filename">SRCREV</code></a>
2452 is not later than <code class="filename">maxrev</code>.</p></li>
2453<li class="listitem"><p><span class="emphasis"><em><code class="filename">rev</code> -</em></span> Only applies the
2454 patch if <a class="link" href="ref-variables-glos.html#var-SRCREV" title="SRCREV"><code class="filename">SRCREV</code></a>
2455 is equal to <code class="filename">rev</code>.</p></li>
2456<li class="listitem"><p><span class="emphasis"><em><code class="filename">notrev</code> -</em></span> Only applies
2457 the patch if <a class="link" href="ref-variables-glos.html#var-SRCREV" title="SRCREV"><code class="filename">SRCREV</code></a>
2458 is not equal to <code class="filename">rev</code>.</p></li>
2459</ul></div>
2460<p>
2461 </p>
2462<p>Here are some additional options worth mentioning:
2463 </p>
2464<div class="itemizedlist"><ul class="itemizedlist" type="disc">
2465<li class="listitem"><p><span class="emphasis"><em><code class="filename">unpack</code> -</em></span> Controls
2466 whether or not to unpack the file if it is an archive.
2467 The default action is to upack the file.</p></li>
2468<li class="listitem"><p><span class="emphasis"><em><code class="filename">subdir</code> -</em></span> Places the file
2469 (or extracts its contents) into the specified
2470 subdirectory of <a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR"><code class="filename">WORKDIR</code></a>.
2471 This option is useful for unusual tarballs or other archives that
2472 don't have their files already in a subdirectory within the archive.
2473 </p></li>
2474<li class="listitem"><p><span class="emphasis"><em><code class="filename">name</code> -</em></span> Specifies a
2475 name to be used for association with <code class="filename">SRC_URI</code> checksums
2476 when you have more than one file specified in <code class="filename">SRC_URI</code>.
2477 </p></li>
2478<li class="listitem"><p><span class="emphasis"><em><code class="filename">downloadfilename</code> -</em></span> Specifies
2479 the filename used when storing the downloaded file.</p></li>
2480</ul></div>
2481<p>
2482 </p>
2483</dd>
2484<dt>
2485<a name="var-SRC_URI_OVERRIDES_PACKAGE_ARCH"></a>SRC_URI_OVERRIDES_PACKAGE_ARCH</dt>
2486<dd>
2487<p></p>
2488<p>
2489 By default, the OpenEmbedded build system automatically detects whether
2490 <code class="filename"><a class="link" href="ref-variables-glos.html#var-SRC_URI" title="SRC_URI">SRC_URI</a></code>
2491 contains files that are machine-specific.
2492 If so, the build system automatically changes
2493 <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_ARCH" title="PACKAGE_ARCH">PACKAGE_ARCH</a></code>.
2494 Setting this variable to "0" disables this behavior.
2495 </p>
2496</dd>
2497<dt>
2498<a name="var-SRCDATE"></a>SRCDATE</dt>
2499<dd><p>
2500 The date of the source code used to build the package.
2501 This variable applies only if the source was fetched from a Source Code Manager (SCM).
2502 </p></dd>
2503<dt>
2504<a name="var-SRCREV"></a>SRCREV</dt>
2505<dd><p>
2506 The revision of the source code used to build the package.
2507 This variable applies to Subversion, Git, Mercurial and Bazaar
2508 only.
2509 Note that if you wish to build a fixed revision and you wish
2510 to avoid performing a query on the remote repository every time
2511 BitBake parses your recipe, you should specify a <code class="filename">SRCREV</code> that is a
2512 full revision identifier and not just a tag.
2513 </p></dd>
2514<dt>
2515<a name="var-SSTATE_DIR"></a>SSTATE_DIR</dt>
2516<dd><p>The directory for the shared state.</p></dd>
2517<dt>
2518<a name="var-SSTATE_MIRRORS"></a>SSTATE_MIRRORS</dt>
2519<dd>
2520<p>
2521 Configures the OpenEmbedded build system to search other
2522 mirror locations for prebuilt cache data objects before
2523 building out the data.
2524 This variable works like fetcher
2525 <code class="filename">MIRRORS</code>/<code class="filename">PREMIRRORS</code>
2526 and points to the cache locations to check for the shared
2527 objects.
2528 </p>
2529<p>
2530 You can specify a filesystem directory or a remote URL such
2531 as HTTP or FTP.
2532 The locations you specify need to contain the shared state
2533 cache (sstate-cache) results from previous builds.
2534 The sstate-cache you point to can also be from builds on
2535 other machines.
2536 </p>
2537<p>
2538 If a mirror uses the same structure as
2539 <a class="link" href="ref-variables-glos.html#var-SSTATE_DIR" title="SSTATE_DIR"><code class="filename">SSTATE_DIR</code></a>,
2540 you need to add
2541 "PATH" at the end as shown in the examples below.
2542 The build system substitues the correct path within the
2543 directory structure.
2544 </p>
2545<pre class="literallayout">
2546 SSTATE_MIRRORS ?= "\
2547 file://.* http://someserver.tld/share/sstate/PATH \n \
2548 file://.* file:///some/local/dir/sstate/PATH"
2549 </pre>
2550<p>
2551 </p>
2552</dd>
2553<dt>
2554<a name="var-STAGING_KERNEL_DIR"></a>STAGING_KERNEL_DIR</dt>
2555<dd><p>
2556 The directory with kernel headers that are required to build out-of-tree
2557 modules.
2558 </p></dd>
2559<dt>
2560<a name="var-STAMP"></a>STAMP</dt>
2561<dd>
2562<p>
2563 Specifies the base path used to create recipe stamp files.
2564 The path to an actual stamp file is constructed by evaluating this
2565 string and then appending additional information.
2566 Currently, the default assignment for <code class="filename">STAMP</code>
2567 as set in the <code class="filename">meta/conf/bitbake.conf</code> file
2568 is:
2569 </p>
2570<pre class="literallayout">
2571 STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}-${EXTENDPE}${PV}-${PR}"
2572 </pre>
2573<p>
2574 See <a class="link" href="ref-variables-glos.html#var-TMPDIR" title="TMPDIR"><code class="filename">TMPDIR</code></a>,
2575 <a class="link" href="ref-variables-glos.html#var-MULTIMACH_TARGET_SYS" title="MULTIMACH_TARGET_SYS"><code class="filename">MULTIMACH_TARGET_SYS</code></a>,
2576 <a class="link" href="ref-variables-glos.html#var-PN" title="PN"><code class="filename">PN</code></a>,
2577 <a class="link" href="ref-variables-glos.html#var-EXTENDPE" title="EXTENDPE"><code class="filename">EXTENDPE</code></a>,
2578 <a class="link" href="ref-variables-glos.html#var-PV" title="PV"><code class="filename">PV</code></a>, and
2579 <a class="link" href="ref-variables-glos.html#var-PR" title="PR"><code class="filename">PR</code></a> for related variable
2580 information.
2581 </p>
2582</dd>
2583<dt>
2584<a name="var-SUMMARY"></a>SUMMARY</dt>
2585<dd><p>The short (72 characters or less) summary of the binary package for packaging
2586 systems such as <code class="filename">opkg</code>, <code class="filename">rpm</code> or
2587 <code class="filename">dpkg</code>.
2588 By default, <code class="filename">SUMMARY</code> is used to define
2589 the <a class="link" href="ref-variables-glos.html#var-DESCRIPTION" title="DESCRIPTION"><code class="filename">DESCRIPTION</code></a>
2590 variable if <code class="filename">DESCRIPTION</code> is not set
2591 in the recipe.
2592 </p></dd>
2593</dl>
2594</div>
2595<div class="glossdiv" title="T">
2596<h3 class="title">T</h3>
2597<dl>
2598<dt>
2599<a name="var-T"></a>T</dt>
2600<dd>
2601<p>This variable points to a directory were Bitbake places temporary
2602 files when building a particular package.
2603 It is typically set as follows:
2604 </p>
2605<pre class="literallayout">
2606 T = ${WORKDIR}/temp
2607 </pre>
2608<p>
2609 The <a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR"><code class="filename">WORKDIR</code></a>
2610 is the directory into which Bitbake unpacks and builds the package.
2611 The default <code class="filename">bitbake.conf</code> file sets this variable.</p>
2612<p>The <code class="filename">T</code> variable is not to be confused with
2613 the <a class="link" href="ref-variables-glos.html#var-TMPDIR" title="TMPDIR"><code class="filename">TMPDIR</code></a> variable,
2614 which points to the root of the directory tree where Bitbake
2615 places the output of an entire build.
2616 </p>
2617</dd>
2618<dt>
2619<a name="var-TARGET_ARCH"></a>TARGET_ARCH</dt>
2620<dd><p>The architecture of the device being built.
2621 While a number of values are possible, the OpenEmbedded build system primarily supports
2622 <code class="filename">arm</code> and <code class="filename">i586</code>.</p></dd>
2623<dt>
2624<a name="var-TARGET_CFLAGS"></a>TARGET_CFLAGS</dt>
2625<dd><p>
2626 Flags passed to the C compiler for the target system.
2627 This variable evaluates to the same as
2628 <code class="filename"><a class="link" href="ref-variables-glos.html#var-CFLAGS" title="CFLAGS">CFLAGS</a></code>.
2629 </p></dd>
2630<dt>
2631<a name="var-TARGET_FPU"></a>TARGET_FPU</dt>
2632<dd><p>Specifies the method for handling FPU code.
2633 For FPU-less targets, which include most ARM CPUs, the variable must be
2634 set to "soft".
2635 If not, the kernel emulation gets used, which results in a performance penalty.</p></dd>
2636<dt>
2637<a name="var-TARGET_OS"></a>TARGET_OS</dt>
2638<dd><p>Specifies the target's operating system.
2639 The variable can be set to "linux" for <code class="filename">eglibc</code>-based systems and
2640 to "linux-uclibc" for <code class="filename">uclibc</code>.
2641 For ARM/EABI targets, there are also "linux-gnueabi" and
2642 "linux-uclibc-gnueabi" values possible.</p></dd>
2643<dt>
2644<a name="var-TCLIBC"></a>TCLIBC</dt>
2645<dd>
2646<p>
2647 Specifies which variant of the GNU standard C library (<code class="filename">libc</code>)
2648 to use during the build process.
2649 This variable replaces <code class="filename">POKYLIBC</code>, which is no longer
2650 supported.
2651 </p>
2652<p>
2653 You can select <code class="filename">eglibc</code> or <code class="filename">uclibc</code>.
2654 </p>
2655<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
2656<h3 class="title">Note</h3>
2657 This release of the Yocto Project does not support the
2658 <code class="filename">glibc</code> implementation of <code class="filename">libc</code>.
2659 </div>
2660<p>
2661 </p>
2662</dd>
2663<dt>
2664<a name="var-TCMODE"></a>TCMODE</dt>
2665<dd>
2666<p>
2667 The toolchain selector.
2668 This variable replaces <code class="filename">POKYMODE</code>, which is no longer
2669 supported.
2670 </p>
2671<p>
2672 The <code class="filename">TCMODE</code> variable selects the external toolchain
2673 built using the OpenEmbedded build system or a few supported combinations of
2674 the upstream GCC or CodeSourcery Labs toolchain.
2675 The variable identifies the <code class="filename">tcmode-*</code> files used in
2676 the <code class="filename">meta/conf/distro/include</code> directory, which is found in the
2677 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
2678 </p>
2679<p>
2680 By default, <code class="filename">TCMODE</code> is set to "default", which
2681 chooses the <code class="filename">tcmode-default.inc</code> file.
2682 The variable is similar to
2683 <a class="link" href="ref-variables-glos.html#var-TCLIBC" title="TCLIBC"><code class="filename">TCLIBC</code></a>, which controls
2684 the variant of the GNU standard C library (<code class="filename">libc</code>)
2685 used during the build process: <code class="filename">eglibc</code> or <code class="filename">uclibc</code>.
2686 </p>
2687</dd>
2688<dt>
2689<a name="var-TMPDIR"></a>TMPDIR</dt>
2690<dd>
2691<p>
2692 This variable is the temporary directory the OpenEmbedded build system
2693 uses when it does its work building images.
2694 By default, the <code class="filename">TMPDIR</code> variable is named
2695 <code class="filename">tmp</code> within the
2696 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
2697 </p>
2698<p>
2699 If you want to establish this directory in a location other than the
2700 default, you can uncomment the following statement in the
2701 <code class="filename">conf/local.conf</code> file in the
2702 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>:
2703 </p>
2704<pre class="literallayout">
2705 #TMPDIR = "${TOPDIR}/tmp"
2706 </pre>
2707<p>
2708 </p>
2709</dd>
2710<dt>
2711<a name="var-TOPDIR"></a>TOPDIR</dt>
2712<dd><p>
2713 This variable is the
2714 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
2715 BitBake automatically sets this variable.
2716 The OpenEmbedded build system uses the Build Directory when building images.
2717 </p></dd>
2718</dl>
2719</div>
2720<div class="glossdiv" title="W">
2721<h3 class="title">W</h3>
2722<dl>
2723<dt>
2724<a name="var-WORKDIR"></a>WORKDIR</dt>
2725<dd>
2726<p>
2727 The pathname of the working directory in which the OpenEmbedded build system
2728 builds a recipe.
2729 This directory is located within the
2730 <a class="link" href="ref-variables-glos.html#var-TMPDIR" title="TMPDIR"><code class="filename">TMPDIR</code></a> directory structure and changes
2731 as different packages are built.
2732 </p>
2733<p>
2734 The actual <code class="filename">WORKDIR</code> directory depends on several things:
2735 </p>
2736<div class="itemizedlist"><ul class="itemizedlist" type="disc">
2737<li class="listitem">The temporary directory - <a class="link" href="ref-variables-glos.html#var-TMPDIR" title="TMPDIR"><code class="filename">TMPDIR</code></a>
2738</li>
2739<li class="listitem">The package architecture - <a class="link" href="ref-variables-glos.html#var-PACKAGE_ARCH" title="PACKAGE_ARCH"><code class="filename">PACKAGE_ARCH</code></a>
2740</li>
2741<li class="listitem">The target machine - <a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE"><code class="filename">MACHINE</code></a>
2742</li>
2743<li class="listitem">The target operating system - <a class="link" href="ref-variables-glos.html#var-TARGET_OS" title="TARGET_OS"><code class="filename">TARGET_OS</code></a>
2744</li>
2745<li class="listitem">The recipe name - <a class="link" href="ref-variables-glos.html#var-PN" title="PN"><code class="filename">PN</code></a>
2746</li>
2747<li class="listitem">The recipe version - <a class="link" href="ref-variables-glos.html#var-PV" title="PV"><code class="filename">PV</code></a>
2748</li>
2749<li class="listitem">The recipe revision - <a class="link" href="ref-variables-glos.html#var-PR" title="PR"><code class="filename">PR</code></a>
2750</li>
2751</ul></div>
2752<p>
2753 </p>
2754<p>
2755 For packages that are not dependent on a particular machine,
2756 <code class="filename">WORKDIR</code> is defined as follows:
2757 </p>
2758<pre class="literallayout">
2759 ${TMPDIR}/work/${PACKAGE_ARCH}-poky-${TARGET_OS}/${PN}-${PV}-${PR}
2760 </pre>
2761<p>
2762 As an example, assume a
2763 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a> top-level
2764 folder name <code class="filename">poky</code> and a default
2765 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>
2766 at <code class="filename">poky/build</code>.
2767 In this case, the working directory the build system uses to build
2768 the <code class="filename">v86d</code> package is the following:
2769 </p>
2770<pre class="literallayout">
2771 ~/poky/build/tmp/work/qemux86-poky-linux/v86d-01.9-r0
2772 </pre>
2773<p>
2774 </p>
2775<p>
2776 For packages that are dependent on a particular machine, <code class="filename">WORKDIR</code>
2777 is defined slightly different:
2778 </p>
2779<pre class="literallayout">
2780 ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR}
2781 </pre>
2782<p>
2783 As an example, again assume a Source Directory top-level folder
2784 named <code class="filename">poky</code> and a default Build Directory
2785 at <code class="filename">poky/build</code>.
2786 In this case, the working directory the build system uses to build
2787 the <code class="filename">acl</code> recipe, which is being built for a
2788 MIPS-based device, is the following:
2789 </p>
2790<pre class="literallayout">
2791 ~/poky/build/tmp/work/mips-poky-linux/acl-2.2.51-r2
2792 </pre>
2793<p>
2794 </p>
2795</dd>
2796</dl>
2797</div>
2798</div>
2799</div></body>
2800</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-distro.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-distro.html
deleted file mode 100644
index ba26400d5a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-distro.html
+++ /dev/null
@@ -1,40 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.1.1. Distribution (Distro)</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-configuration.html" title="11.1. Configuration">
9<link rel="prev" href="ref-varlocality-configuration.html" title="11.1. Configuration">
10<link rel="next" href="ref-varlocality-config-machine.html" title="11.1.2. Machine">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.1.1. Distribution (Distro)">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-config-distro"></a>11.1.1. Distribution (Distro)</h3></div></div></div>
15<p>
16 This section lists variables whose context is the distribution, or distro.
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO" title="DISTRO">DISTRO</a></code></p></li>
20<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_NAME" title="DISTRO_NAME">DISTRO_NAME</a></code>
21 </p></li>
22<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO_VERSION" title="DISTRO_VERSION">DISTRO_VERSION</a>
23 </code></p></li>
24<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MAINTAINER" title="MAINTAINER">MAINTAINER</a></code>
25 </p></li>
26<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_CLASSES" title="PACKAGE_CLASSES">PACKAGE_CLASSES</a>
27 </code></p></li>
28<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-TARGET_OS" title="TARGET_OS">TARGET_OS</a></code>
29 </p></li>
30<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-TARGET_FPU" title="TARGET_FPU">TARGET_FPU</a></code>
31 </p></li>
32<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-TCMODE" title="TCMODE">TCMODE</a></code>
33 </p></li>
34<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-TCLIBC" title="TCLIBC">TCLIBC</a></code>
35 </p></li>
36</ul></div>
37<p>
38 </p>
39</div></body>
40</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-local.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-local.html
deleted file mode 100644
index 2067374c26..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-local.html
+++ /dev/null
@@ -1,42 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.1.3. Local</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-configuration.html" title="11.1. Configuration">
9<link rel="prev" href="ref-varlocality-config-machine.html" title="11.1.2. Machine">
10<link rel="next" href="ref-varlocality-recipes.html" title="11.2. Recipes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.1.3. Local">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-config-local"></a>11.1.3. Local</h3></div></div></div>
15<p>
16 This section lists variables whose context is the local configuration through the
17 <code class="filename">local.conf</code> file.
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DISTRO" title="DISTRO">DISTRO</a></code>
21 </p></li>
22<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE">MACHINE</a></code>
23 </p></li>
24<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DL_DIR" title="DL_DIR">DL_DIR</a></code>
25 </p></li>
26<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-BBFILES" title="BBFILES">BBFILES</a></code>
27 </p></li>
28<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_IMAGE_FEATURES" title="EXTRA_IMAGE_FEATURES">EXTRA_IMAGE_FEATURES
29 </a></code></p></li>
30<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_CLASSES" title="PACKAGE_CLASSES">PACKAGE_CLASSES</a>
31 </code></p></li>
32<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-BB_NUMBER_THREADS" title="BB_NUMBER_THREADS">BB_NUMBER_THREADS</a>
33 </code></p></li>
34<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-BBINCLUDELOGS" title="BBINCLUDELOGS">BBINCLUDELOGS</a>
35 </code></p></li>
36<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-ENABLE_BINARY_LOCALE_GENERATION" title="ENABLE_BINARY_LOCALE_GENERATION">
37 ENABLE_BINARY_LOCALE_GENERATION</a></code></p></li>
38</ul></div>
39<p>
40 </p>
41</div></body>
42</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-machine.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-machine.html
deleted file mode 100644
index 82ee2a4e6d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-config-machine.html
+++ /dev/null
@@ -1,41 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.1.2. Machine</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-configuration.html" title="11.1. Configuration">
9<link rel="prev" href="ref-varlocality-config-distro.html" title="11.1.1. Distribution (Distro)">
10<link rel="next" href="ref-varlocality-config-local.html" title="11.1.3. Local">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.1.2. Machine">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-config-machine"></a>11.1.2. Machine</h3></div></div></div>
15<p>
16 This section lists variables whose context is the machine.
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-TARGET_ARCH" title="TARGET_ARCH">TARGET_ARCH</a></code>
20 </p></li>
21<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-SERIAL_CONSOLE" title="SERIAL_CONSOLE">SERIAL_CONSOLE</a>
22 </code></p></li>
23<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_EXTRA_ARCHS" title="PACKAGE_EXTRA_ARCHS">PACKAGE_EXTRA_ARCHS</a>
24 </code></p></li>
25<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-IMAGE_FSTYPES" title="IMAGE_FSTYPES">IMAGE_FSTYPES</a>
26 </code></p></li>
27<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_FEATURES" title="MACHINE_FEATURES">MACHINE_FEATURES</a>
28 </code></p></li>
29<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_EXTRA_RDEPENDS" title="MACHINE_EXTRA_RDEPENDS">MACHINE_EXTRA_RDEPENDS
30 </a></code></p></li>
31<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_EXTRA_RRECOMMENDS" title="MACHINE_EXTRA_RRECOMMENDS">MACHINE_EXTRA_RRECOMMENDS
32 </a></code></p></li>
33<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_ESSENTIAL_EXTRA_RDEPENDS" title="MACHINE_ESSENTIAL_EXTRA_RDEPENDS">MACHINE_ESSENTIAL_EXTRA_RDEPENDS
34 </a></code></p></li>
35<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS" title="MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS">
36 MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS</a></code></p></li>
37</ul></div>
38<p>
39 </p>
40</div></body>
41</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-configuration.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-configuration.html
deleted file mode 100644
index c6a1c87198..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-configuration.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.1. Configuration</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality.html" title="Chapter 11. Variable Context">
9<link rel="prev" href="ref-varlocality.html" title="Chapter 11. Variable Context">
10<link rel="next" href="ref-varlocality-config-distro.html" title="11.1.1. Distribution (Distro)">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.1. Configuration">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-varlocality-configuration"></a>11.1. Configuration</h2></div></div></div>
15<p>
16 The following subsections provide lists of variables whose context is
17 configuration: distribution, machine, and local.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-build.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-build.html
deleted file mode 100644
index 3068ceb8d2..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-build.html
+++ /dev/null
@@ -1,33 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.2.4. Extra Build Information</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-recipes.html" title="11.2. Recipes">
9<link rel="prev" href="ref-varlocality-recipe-paths.html" title="11.2.3. Paths">
10<link rel="next" href="faq.html" title="Chapter 12. FAQ">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.2.4. Extra Build Information">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-recipe-build"></a>11.2.4. Extra Build Information</h3></div></div></div>
15<p>
16 This section lists variables that define extra build information for recipes.
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OECMAKE" title="EXTRA_OECMAKE">EXTRA_OECMAKE</a>
20 </code></p></li>
21<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OECONF" title="EXTRA_OECONF">EXTRA_OECONF</a>
22 </code></p></li>
23<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-EXTRA_OEMAKE" title="EXTRA_OEMAKE">EXTRA_OEMAKE</a>
24 </code></p></li>
25<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGES" title="PACKAGES">PACKAGES</a></code>
26 </p></li>
27<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DEFAULT_PREFERENCE" title="DEFAULT_PREFERENCE">DEFAULT_PREFERENCE
28 </a></code></p></li>
29</ul></div>
30<p>
31 </p>
32</div></body>
33</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-dependencies.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-dependencies.html
deleted file mode 100644
index 4a172a7751..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-dependencies.html
+++ /dev/null
@@ -1,33 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.2.2. Dependencies</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-recipes.html" title="11.2. Recipes">
9<link rel="prev" href="ref-varlocality-recipe-required.html" title="11.2.1. Required">
10<link rel="next" href="ref-varlocality-recipe-paths.html" title="11.2.3. Paths">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.2.2. Dependencies">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-recipe-dependencies"></a>11.2.2. Dependencies</h3></div></div></div>
15<p>
16 This section lists variables that define recipe dependencies.
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-DEPENDS" title="DEPENDS">DEPENDS</a>
20 </code></p></li>
21<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-RDEPENDS" title="RDEPENDS">RDEPENDS</a>
22 </code></p></li>
23<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-RRECOMMENDS" title="RRECOMMENDS">RRECOMMENDS</a>
24 </code></p></li>
25<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-RCONFLICTS" title="RCONFLICTS">RCONFLICTS</a>
26 </code></p></li>
27<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-RREPLACES" title="RREPLACES">RREPLACES</a>
28 </code></p></li>
29</ul></div>
30<p>
31 </p>
32</div></body>
33</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-paths.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-paths.html
deleted file mode 100644
index 92003d344f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-paths.html
+++ /dev/null
@@ -1,29 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.2.3. Paths</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-recipes.html" title="11.2. Recipes">
9<link rel="prev" href="ref-varlocality-recipe-dependencies.html" title="11.2.2. Dependencies">
10<link rel="next" href="ref-varlocality-recipe-build.html" title="11.2.4. Extra Build Information">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.2.3. Paths">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-recipe-paths"></a>11.2.3. Paths</h3></div></div></div>
15<p>
16 This section lists variables that define recipe paths.
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">WORKDIR</a>
20 </code></p></li>
21<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-S" title="S">S</a>
22 </code></p></li>
23<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-FILES" title="FILES">FILES</a>
24 </code></p></li>
25</ul></div>
26<p>
27 </p>
28</div></body>
29</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-required.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-required.html
deleted file mode 100644
index bb0355cced..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipe-required.html
+++ /dev/null
@@ -1,30 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.2.1. Required</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality-recipes.html" title="11.2. Recipes">
9<link rel="prev" href="ref-varlocality-recipes.html" title="11.2. Recipes">
10<link rel="next" href="ref-varlocality-recipe-dependencies.html" title="11.2.2. Dependencies">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.2.1. Required">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="ref-varlocality-recipe-required"></a>11.2.1. Required</h3></div></div></div>
15<p>
16 This section lists variables that are required for recipes.
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-LICENSE" title="LICENSE">LICENSE</a>
20 </code></p></li>
21<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-LIC_FILES_CHKSUM" title="LIC_FILES_CHKSUM">LIC_FILES_CHKSUM</a>
22 </code></p></li>
23<li class="listitem"><p><code class="filename"><a class="link" href="ref-variables-glos.html#var-SRC_URI" title="SRC_URI">SRC_URI</a></code> - used
24 in recipes that fetch local or remote files.
25 </p></li>
26</ul></div>
27<p>
28 </p>
29</div></body>
30</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipes.html
deleted file mode 100644
index 5959cdc5ed..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality-recipes.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>11.2. Recipes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-varlocality.html" title="Chapter 11. Variable Context">
9<link rel="prev" href="ref-varlocality-config-local.html" title="11.1.3. Local">
10<link rel="next" href="ref-varlocality-recipe-required.html" title="11.2.1. Required">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="11.2. Recipes">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="ref-varlocality-recipes"></a>11.2. Recipes</h2></div></div></div>
15<p>
16 The following subsections provide lists of variables whose context is
17 recipes: required, dependencies, path, and extra build information.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality.html
deleted file mode 100644
index 3cf716975f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-varlocality.html
+++ /dev/null
@@ -1,41 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 11. Variable Context</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="ref-variables-glos.html" title="Chapter 10. Variables Glossary">
10<link rel="next" href="ref-varlocality-configuration.html" title="11.1. Configuration">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 11. Variable Context">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="ref-varlocality"></a>Chapter 11. Variable Context</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="ref-varlocality-configuration.html">11.1. Configuration</a></span></dt>
19<dd><dl>
20<dt><span class="section"><a href="ref-varlocality-config-distro.html">11.1.1. Distribution (Distro)</a></span></dt>
21<dt><span class="section"><a href="ref-varlocality-config-machine.html">11.1.2. Machine</a></span></dt>
22<dt><span class="section"><a href="ref-varlocality-config-local.html">11.1.3. Local</a></span></dt>
23</dl></dd>
24<dt><span class="section"><a href="ref-varlocality-recipes.html">11.2. Recipes</a></span></dt>
25<dd><dl>
26<dt><span class="section"><a href="ref-varlocality-recipe-required.html">11.2.1. Required</a></span></dt>
27<dt><span class="section"><a href="ref-varlocality-recipe-dependencies.html">11.2.2. Dependencies</a></span></dt>
28<dt><span class="section"><a href="ref-varlocality-recipe-paths.html">11.2.3. Paths</a></span></dt>
29<dt><span class="section"><a href="ref-varlocality-recipe-build.html">11.2.4. Extra Build Information</a></span></dt>
30</dl></dd>
31</dl>
32</div>
33<p>
34 While most variables can be used in almost any context such as
35 <code class="filename">.conf</code>, <code class="filename">.bbclass</code>,
36 <code class="filename">.inc</code>, and <code class="filename">.bb</code> files,
37 some variables are often associated with a particular locality or context.
38 This chapter describes some common associations.
39 </p>
40</div></body>
41</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/required-packages-for-the-host-development-system.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/required-packages-for-the-host-development-system.html
deleted file mode 100644
index 5100bbcb29..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/required-packages-for-the-host-development-system.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3.2. Required Packages for the Host Development System</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="intro-requirements.html" title="1.3. System Requirements">
9<link rel="prev" href="detailed-supported-distros.html" title="1.3.1. Supported Linux Distributions">
10<link rel="next" href="ubuntu-packages.html" title="1.3.2.1. Ubuntu">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.2. Required Packages for the Host Development System">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="required-packages-for-the-host-development-system"></a>1.3.2. Required Packages for the Host Development System</h3></div></div></div>
15<p>
16 The list of packages you need on the host development system can
17 be large when covering all build scenarios using the Yocto Project.
18 This section provides required packages by Linux distribution and
19 further categorized by function.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-bugtracker.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-bugtracker.html
deleted file mode 100644
index 4b4f994671..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-bugtracker.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>13.2. Tracking Bugs</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
9<link rel="prev" href="resources-intro.html" title="13.1. Introduction">
10<link rel="next" href="resources-mailinglist.html" title="13.3. Mailing lists">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="13.2. Tracking Bugs">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="resources-bugtracker"></a>13.2. Tracking Bugs</h2></div></div></div>
15<p>
16 If you find problems with the Yocto Project, you should report them using the
17 Bugzilla application at <a class="ulink" href="http://bugzilla.yoctoproject.org" target="_self">http://bugzilla.yoctoproject.org</a>.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-contributions.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-contributions.html
deleted file mode 100644
index c7d8c539ae..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-contributions.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>13.6. Contributions</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
9<link rel="prev" href="resources-links.html" title="13.5. Links">
10</head>
11<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="13.6. Contributions">
12<div class="titlepage"><div><div><h2 class="title" style="clear: both">
13<a name="resources-contributions"></a>13.6. Contributions</h2></div></div></div>
14<p>
15 The Yocto Project gladly accepts contributions.
16 You can submit changes to the project either by creating and sending pull requests,
17 or by submitting patches through email.
18 For information on how to do both, see the
19 "<a class="link" href="../dev-manual/how-to-submit-a-change.html" target="_self">How to Submit a Change</a>"
20 section in the Yocto Project Development Manual.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-intro.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-intro.html
deleted file mode 100644
index c7340ff313..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-intro.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>13.1. Introduction</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
9<link rel="prev" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
10<link rel="next" href="resources-bugtracker.html" title="13.2. Tracking Bugs">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="13.1. Introduction">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="resources-intro"></a>13.1. Introduction</h2></div></div></div>
15<p>
16 The Yocto Project team is happy for people to experiment with the Yocto Project.
17 A number of places exist to find help if you run into difficulties or find bugs.
18 To find out how to download source code,
19 see the "<a class="link" href="../dev-manual/local-yp-release.html" target="_self">Yocto Project Release</a>"
20 list item in the Yocto Project Development Manual.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-irc.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-irc.html
deleted file mode 100644
index 5a611fa6a8..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-irc.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>13.4. Internet Relay Chat (IRC)</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
9<link rel="prev" href="resources-mailinglist.html" title="13.3. Mailing lists">
10<link rel="next" href="resources-links.html" title="13.5. Links">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="13.4. Internet Relay Chat (IRC)">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="resources-irc"></a>13.4. Internet Relay Chat (IRC)</h2></div></div></div>
15<p>
16 Two IRC channels on freenode are available for the Yocto Project and Poky discussions:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><code class="filename">#yocto</code></p></li>
20<li class="listitem"><p><code class="filename">#poky</code></p></li>
21</ul></div>
22<p>
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-links.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-links.html
deleted file mode 100644
index 0a153b8f01..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-links.html
+++ /dev/null
@@ -1,42 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>13.5. Links</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
9<link rel="prev" href="resources-irc.html" title="13.4. Internet Relay Chat (IRC)">
10<link rel="next" href="resources-contributions.html" title="13.6. Contributions">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="13.5. Links">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="resources-links"></a>13.5. Links</h2></div></div></div>
15<p>
16 Following is a list of resources you will find helpful:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p><span class="emphasis"><em><a class="ulink" href="http://www.yoctoproject.org" target="_self">The Yocto Project website</a>:
20 </em></span> The home site for the Yocto Project.</p></li>
21<li class="listitem"><p><span class="emphasis"><em><a class="ulink" href="http://www.intel.com/" target="_self">Intel Corporation</a>:</em></span>
22 The company who acquired OpenedHand in 2008 and began development on the
23 Yocto Project.</p></li>
24<li class="listitem"><p><span class="emphasis"><em><a class="ulink" href="http://www.openembedded.org" target="_self">OpenEmbedded</a>:</em></span>
25 The upstream, generic, embedded distribution used as the basis for the build system in the
26 Yocto Project.
27 Poky derives from and contributes back to the OpenEmbedded project.</p></li>
28<li class="listitem"><p><span class="emphasis"><em><a class="ulink" href="http://developer.berlios.de/projects/bitbake/" target="_self">
29 BitBake</a>:</em></span> The tool used to process metadata.</p></li>
30<li class="listitem"><p><span class="emphasis"><em>BitBake User Manual:</em></span>
31 A comprehensive guide to the BitBake tool.
32 You can find the BitBake User Manual in the <code class="filename">bitbake/doc/manual</code>
33 directory, which is found in the
34 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
35 </p></li>
36<li class="listitem"><p><span class="emphasis"><em><a class="ulink" href="http://wiki.qemu.org/Index.html" target="_self">QEMU</a>:
37 </em></span> An open source machine emulator and virtualizer.</p></li>
38</ul></div>
39<p>
40 </p>
41</div></body>
42</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-mailinglist.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-mailinglist.html
deleted file mode 100644
index 3cc05beea4..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources-mailinglist.html
+++ /dev/null
@@ -1,39 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>13.3. Mailing lists</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="resources.html" title="Chapter 13. Contributing to the Yocto Project">
9<link rel="prev" href="resources-bugtracker.html" title="13.2. Tracking Bugs">
10<link rel="next" href="resources-irc.html" title="13.4. Internet Relay Chat (IRC)">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="13.3. Mailing lists">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="resources-mailinglist"></a>13.3. Mailing lists</h2></div></div></div>
15<p>
16 There are a number of mailing lists maintained by the Yocto Project as well as
17 related OpenEmbedded mailing lists for discussion, patch submission and announcements.
18 To subscribe to one of the following mailing lists, click on the appropriate URL
19 in the following list and follow the instructions:
20 </p>
21<div class="itemizedlist"><ul class="itemizedlist" type="disc">
22<li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/listinfo/yocto" target="_self">http://lists.yoctoproject.org/listinfo/yocto</a> -
23 General Yocto Project discussion mailing list. </p></li>
24<li class="listitem"><p><a class="ulink" href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_self">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a> -
25 Discussion mailing list about OpenEmbedded-Core (the core metadata).</p></li>
26<li class="listitem"><p><a class="ulink" href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel" target="_self">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel</a> -
27 Discussion mailing list about OpenEmbedded.</p></li>
28<li class="listitem"><p><a class="ulink" href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel" target="_self">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel</a> -
29 Discussion mailing list about the BitBake build tool.</p></li>
30<li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/listinfo/poky" target="_self">http://lists.yoctoproject.org/listinfo/poky</a> -
31 Discussion mailing list about Poky.</p></li>
32<li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/listinfo/yocto-announce" target="_self">http://lists.yoctoproject.org/listinfo/yocto-announce</a> -
33 Mailing list to receive official Yocto Project release and milestone
34 announcements.</p></li>
35</ul></div>
36<p>
37 </p>
38</div></body>
39</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/resources.html
deleted file mode 100644
index c97f06e0c2..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/resources.html
+++ /dev/null
@@ -1,27 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 13. Contributing to the Yocto Project</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="faq.html" title="Chapter 12. FAQ">
10<link rel="next" href="resources-intro.html" title="13.1. Introduction">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 13. Contributing to the Yocto Project">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="resources"></a>Chapter 13. Contributing to the Yocto Project</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="resources-intro.html">13.1. Introduction</a></span></dt>
19<dt><span class="section"><a href="resources-bugtracker.html">13.2. Tracking Bugs</a></span></dt>
20<dt><span class="section"><a href="resources-mailinglist.html">13.3. Mailing lists</a></span></dt>
21<dt><span class="section"><a href="resources-irc.html">13.4. Internet Relay Chat (IRC)</a></span></dt>
22<dt><span class="section"><a href="resources-links.html">13.5. Links</a></span></dt>
23<dt><span class="section"><a href="resources-contributions.html">13.6. Contributions</a></span></dt>
24</dl>
25</div>
26</div></body>
27</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state-cache.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state-cache.html
deleted file mode 100644
index 8f2f5a5ed6..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state-cache.html
+++ /dev/null
@@ -1,60 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2. Shared State Cache</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="technical-details.html" title="Chapter 3. Technical Details">
9<link rel="prev" href="usingpoky-components-configuration.html" title="3.1.4. Configuration">
10<link rel="next" href="overall-architecture.html" title="3.2.1. Overall Architecture">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2. Shared State Cache">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="shared-state-cache"></a>3.2. Shared State Cache</h2></div></div></div>
15<p>
16 By design, the OpenEmbedded build system builds everything from scratch unless
17 BitBake can determine that parts don't need to be rebuilt.
18 Fundamentally, building from scratch is attractive as it means all parts are
19 built fresh and there is no possibility of stale data causing problems.
20 When developers hit problems, they typically default back to building from scratch
21 so they know the state of things from the start.
22 </p>
23<p>
24 Building an image from scratch is both an advantage and a disadvantage to the process.
25 As mentioned in the previous paragraph, building from scratch ensures that
26 everything is current and starts from a known state.
27 However, building from scratch also takes much longer as it generally means
28 rebuilding things that don't necessarily need rebuilt.
29 </p>
30<p>
31 The Yocto Project implements shared state code that supports incremental builds.
32 The implementation of the shared state code answers the following questions that
33 were fundamental roadblocks within the OpenEmbedded incremental build support system:
34 </p>
35<div class="itemizedlist"><ul class="itemizedlist" type="disc">
36<li class="listitem">What pieces of the system have changed and what pieces have not changed?</li>
37<li class="listitem">How are changed pieces of software removed and replaced?</li>
38<li class="listitem">How are pre-built components that don't need to be rebuilt from scratch
39 used when they are available?</li>
40</ul></div>
41<p>
42 </p>
43<p>
44 For the first question, the build system detects changes in the "inputs" to a given task by
45 creating a checksum (or signature) of the task's inputs.
46 If the checksum changes, the system assumes the inputs have changed and the task needs to be
47 rerun.
48 For the second question, the shared state (sstate) code tracks which tasks add which output
49 to the build process.
50 This means the output from a given task can be removed, upgraded or otherwise manipulated.
51 The third question is partly addressed by the solution for the second question
52 assuming the build system can fetch the sstate objects from remote locations and
53 install them if they are deemed to be valid.
54 </p>
55<p>
56 The rest of this section goes into detail about the overall incremental build
57 architecture, the checksums (signatures), shared state, and some tips and tricks.
58 </p>
59</div></body>
60</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state.html
deleted file mode 100644
index e14e306eb5..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/shared-state.html
+++ /dev/null
@@ -1,134 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.3. Shared State</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="shared-state-cache.html" title="3.2. Shared State Cache">
9<link rel="prev" href="checksums.html" title="3.2.2. Checksums (Signatures)">
10<link rel="next" href="tips-and-tricks.html" title="3.2.4. Tips and Tricks">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.3. Shared State">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="shared-state"></a>3.2.3. Shared State</h3></div></div></div>
15<p>
16 Checksums and dependencies, as discussed in the previous section, solve half the
17 problem.
18 The other part of the problem is being able to use checksum information during the build
19 and being able to reuse or rebuild specific components.
20 </p>
21<p>
22 The shared state class (<code class="filename">sstate.bbclass</code>)
23 is a relatively generic implementation of how to "capture" a snapshot of a given task.
24 The idea is that the build process does not care about the source of a task's output.
25 Output could be freshly built or it could be downloaded and unpacked from
26 somewhere - the build process doesn't need to worry about its source.
27 </p>
28<p>
29 There are two types of output, one is just about creating a directory
30 in <code class="filename">WORKDIR</code>.
31 A good example is the output of either <code class="filename">do_install</code> or
32 <code class="filename">do_package</code>.
33 The other type of output occurs when a set of data is merged into a shared directory
34 tree such as the sysroot.
35 </p>
36<p>
37 The Yocto Project team has tried to keep the details of the implementation hidden in
38 <code class="filename">sstate.bbclass</code>.
39 From a user's perspective, adding shared state wrapping to a task
40 is as simple as this <code class="filename">do_deploy</code> example taken from
41 <code class="filename">do_deploy.bbclass</code>:
42 </p>
43<pre class="literallayout">
44 DEPLOYDIR = "${WORKDIR}/deploy-${PN}"
45 SSTATETASKS += "do_deploy"
46 do_deploy[sstate-name] = "deploy"
47 do_deploy[sstate-inputdirs] = "${DEPLOYDIR}"
48 do_deploy[sstate-outputdirs] = "${DEPLOY_DIR_IMAGE}"
49
50 python do_deploy_setscene () {
51 sstate_setscene(d)
52 }
53 addtask do_deploy_setscene
54 </pre>
55<p>
56 In the example, we add some extra flags to the task, a name field ("deploy"), an
57 input directory where the task sends data, and the output
58 directory where the data from the task should eventually be copied.
59 We also add a <code class="filename">_setscene</code> variant of the task and add the task
60 name to the <code class="filename">SSTATETASKS</code> list.
61 </p>
62<p>
63 If you have a directory whose contents you need to preserve, you can do this with
64 a line like the following:
65 </p>
66<pre class="literallayout">
67 do_package[sstate-plaindirs] = "${PKGD} ${PKGDEST}"
68 </pre>
69<p>
70 This method, as well as the following example, also works for multiple directories.
71 </p>
72<pre class="literallayout">
73 do_package[sstate-inputdirs] = "${PKGDESTWORK} ${SHLIBSWORKDIR}"
74 do_package[sstate-outputdirs] = "${PKGDATA_DIR} ${SHLIBSDIR}"
75 do_package[sstate-lockfile] = "${PACKAGELOCK}"
76 </pre>
77<p>
78 These methods also include the ability to take a lockfile when manipulating
79 shared state directory structures since some cases are sensitive to file
80 additions or removals.
81 </p>
82<p>
83 Behind the scenes, the shared state code works by looking in
84 <a class="link" href="ref-variables-glos.html#var-SSTATE_DIR" title="SSTATE_DIR"><code class="filename">SSTATE_DIR</code></a> and
85 <a class="link" href="ref-variables-glos.html#var-SSTATE_MIRRORS" title="SSTATE_MIRRORS"><code class="filename">SSTATE_MIRRORS</code></a>
86 for shared state files.
87 Here is an example:
88 </p>
89<pre class="literallayout">
90 SSTATE_MIRRORS ?= "\
91 file://.* http://someserver.tld/share/sstate/PATH \n \
92 file://.* file:///some/local/dir/sstate/PATH"
93 </pre>
94<p>
95 </p>
96<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
97<h3 class="title">Note</h3>
98 The shared state directory (<code class="filename">SSTATE_DIR</code>) is
99 organized into two-character subdirectories, where the subdirectory
100 names are based on the first two characters of the hash.
101 If the shared state directory structure for a mirror has the
102 same structure as <code class="filename">SSTATE_DIR</code>, you must
103 specify "PATH" as part of the URI to enable the build system
104 to map to the appropriate subdirectory.
105 </div>
106<p>
107 </p>
108<p>
109 The shared state package validity can be detected just by looking at the
110 filename since the filename contains the task checksum (or signature) as
111 described earlier in this section.
112 If a valid shared state package is found, the build process downloads it
113 and uses it to accelerate the task.
114 </p>
115<p>
116 The build processes uses the <code class="filename">*_setscene</code> tasks
117 for the task acceleration phase.
118 BitBake goes through this phase before the main execution code and tries
119 to accelerate any tasks for which it can find shared state packages.
120 If a shared state package for a task is available, the shared state
121 package is used.
122 This means the task and any tasks on which it is dependent are not
123 executed.
124 </p>
125<p>
126 As a real world example, the aim is when building an IPK-based image,
127 only the <code class="filename">do_package_write_ipk</code> tasks would have their
128 shared state packages fetched and extracted.
129 Since the sysroot is not used, it would never get extracted.
130 This is another reason why a task-based approach is preferred over a
131 recipe-based approach, which would have to install the output from every task.
132 </p>
133</div></body>
134</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-basic-top-level.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-basic-top-level.html
deleted file mode 100644
index 62bdd6b748..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-basic-top-level.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.11. LICENSE, README, and README.hardware</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-script.html" title="5.1.10. oe-init-build-env">
10<link rel="next" href="structure-build.html" title="5.2. The Build Directory - build/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.11. LICENSE, README, and README.hardware">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-basic-top-level"></a>5.1.11. <code class="filename">LICENSE, README, and README.hardware</code>
15</h3></div></div></div>
16<p>
17 These files are standard top-level files.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-bblayers.conf.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-bblayers.conf.html
deleted file mode 100644
index 74f7729330..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-bblayers.conf.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.3. build/conf/bblayers.conf</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-conf-local.conf.html" title="5.2.2. build/conf/local.conf">
10<link rel="next" href="structure-build-conf-sanity_info.html" title="5.2.4. build/conf/sanity_info">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.3. build/conf/bblayers.conf">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-conf-bblayers.conf"></a>5.2.3. <code class="filename">build/conf/bblayers.conf</code>
15</h3></div></div></div>
16<p>
17 This file defines layers, which is a directory tree, traversed (or walked) by BitBake.
18 If <code class="filename">bblayers.conf</code>
19 is not present, it is created from <code class="filename">bblayers.conf.sample</code> when
20 you <code class="filename">source</code> the environment setup script.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-local.conf.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-local.conf.html
deleted file mode 100644
index 30f1c10881..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-local.conf.html
+++ /dev/null
@@ -1,37 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.2. build/conf/local.conf</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-pseudodone.html" title="5.2.1. build/pseudodone">
10<link rel="next" href="structure-build-conf-bblayers.conf.html" title="5.2.3. build/conf/bblayers.conf">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.2. build/conf/local.conf">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-conf-local.conf"></a>5.2.2. <code class="filename">build/conf/local.conf</code>
15</h3></div></div></div>
16<p>
17 This file contains all the local user configuration for your build environment.
18 If there is no <code class="filename">local.conf</code> present, it is created from
19 <code class="filename">local.conf.sample</code>.
20 The <code class="filename">local.conf</code> file contains documentation on the various configuration options.
21 Any variable set here overrides any variable set elsewhere within the environment unless
22 that variable is hard-coded within a file (e.g. by using '=' instead of '?=').
23 Some variables are hard-coded for various reasons but these variables are
24 relatively rare.
25 </p>
26<p>
27 Edit this file to set the <code class="filename"><a class="link" href="ref-variables-glos.html#var-MACHINE" title="MACHINE">MACHINE</a></code>
28 for which you want to build, which package types you wish to use
29 (<a class="link" href="ref-variables-glos.html#var-PACKAGE_CLASSES" title="PACKAGE_CLASSES"><code class="filename">PACKAGE_CLASSES</code></a>),
30 where you want to downloaded files
31 (<code class="filename"><a class="link" href="ref-variables-glos.html#var-DL_DIR" title="DL_DIR">DL_DIR</a></code>),
32 and how you want your host machine to use resources
33 (<a class="link" href="ref-variables-glos.html#var-BB_NUMBER_THREADS" title="BB_NUMBER_THREADS"><code class="filename">BB_NUMBER_THREADS</code></a> and
34 <a class="link" href="ref-variables-glos.html#var-PARALLEL_MAKE" title="PARALLEL_MAKE"><code class="filename">PARALLEL_MAKE</code></a>).
35 </p>
36</div></body>
37</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-sanity_info.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-sanity_info.html
deleted file mode 100644
index 7cb04282b9..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-conf-sanity_info.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.4. build/conf/sanity_info</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-conf-bblayers.conf.html" title="5.2.3. build/conf/bblayers.conf">
10<link rel="next" href="structure-build-downloads.html" title="5.2.5. build/downloads/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.4. build/conf/sanity_info">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-conf-sanity_info"></a>5.2.4. <code class="filename">build/conf/sanity_info</code>
15</h3></div></div></div>
16<p>
17 This file is created during the build to indicate the state of the sanity checks.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-downloads.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-downloads.html
deleted file mode 100644
index 5ca90d8d8d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-downloads.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.5. build/downloads/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-conf-sanity_info.html" title="5.2.4. build/conf/sanity_info">
10<link rel="next" href="structure-build-sstate-cache.html" title="5.2.6. build/sstate-cache/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.5. build/downloads/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-downloads"></a>5.2.5. <code class="filename">build/downloads/</code>
15</h3></div></div></div>
16<p>
17 This directory is used for the upstream source tarballs.
18 The directory can be reused by multiple builds or moved to another location.
19 You can control the location of this directory through the
20 <code class="filename"><a class="link" href="ref-variables-glos.html#var-DL_DIR" title="DL_DIR">DL_DIR</a></code> variable.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-pseudodone.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-pseudodone.html
deleted file mode 100644
index 74f4cd4a90..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-pseudodone.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.1. build/pseudodone</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build.html" title="5.2. The Build Directory - build/">
10<link rel="next" href="structure-build-conf-local.conf.html" title="5.2.2. build/conf/local.conf">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.1. build/pseudodone">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-pseudodone"></a>5.2.1. <code class="filename">build/pseudodone</code>
15</h3></div></div></div>
16<p>
17 This tag file indicates that the initial pseudo binary was created.
18 The file is built the first time BitBake is invoked.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-sstate-cache.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-sstate-cache.html
deleted file mode 100644
index f1cb3d291b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-sstate-cache.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.6. build/sstate-cache/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-downloads.html" title="5.2.5. build/downloads/">
10<link rel="next" href="structure-build-tmp.html" title="5.2.7. build/tmp/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.6. build/sstate-cache/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-sstate-cache"></a>5.2.6. <code class="filename">build/sstate-cache/</code>
15</h3></div></div></div>
16<p>
17 This directory is used for the shared state cache.
18 The directory can be reused by multiple builds or moved to another location.
19 You can control the location of this directory through the
20 <code class="filename"><a class="link" href="ref-variables-glos.html#var-SSTATE_DIR" title="SSTATE_DIR">SSTATE_DIR</a></code> variable.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-buildstats.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-buildstats.html
deleted file mode 100644
index c1ad81c98a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-buildstats.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.8. build/tmp/buildstats/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp.html" title="5.2.7. build/tmp/">
10<link rel="next" href="structure-build-tmp-cache.html" title="5.2.9. build/tmp/cache/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.8. build/tmp/buildstats/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-buildstats"></a>5.2.8. <code class="filename">build/tmp/buildstats/</code>
15</h3></div></div></div>
16<p>
17 This directory stores the build statistics.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-cache.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-cache.html
deleted file mode 100644
index d18f201c6c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-cache.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.9. build/tmp/cache/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-buildstats.html" title="5.2.8. build/tmp/buildstats/">
10<link rel="next" href="structure-build-tmp-deploy.html" title="5.2.10. build/tmp/deploy/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.9. build/tmp/cache/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-cache"></a>5.2.9. <code class="filename">build/tmp/cache/</code>
15</h3></div></div></div>
16<p>
17 When BitBake parses the metadata, it creates a cache file of the result that can
18 be used when subsequently running commands.
19 These results are stored here on a per-machine basis.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-deb.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-deb.html
deleted file mode 100644
index 42647f54d0..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-deb.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.11. build/tmp/deploy/deb/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-deploy.html" title="5.2.10. build/tmp/deploy/">
10<link rel="next" href="structure-build-tmp-deploy-rpm.html" title="5.2.12. build/tmp/deploy/rpm/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.11. build/tmp/deploy/deb/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy-deb"></a>5.2.11. <code class="filename">build/tmp/deploy/deb/</code>
15</h3></div></div></div>
16<p>
17 This directory receives any <code class="filename">.deb</code> packages produced by
18 the build process.
19 The packages are sorted into feeds for different architecture types.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html
deleted file mode 100644
index b2810d2a76..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html
+++ /dev/null
@@ -1,44 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.14. build/tmp/deploy/images/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-deploy-licenses.html" title="5.2.13. build/tmp/deploy/licenses/">
10<link rel="next" href="structure-build-tmp-deploy-ipk.html" title="5.2.15. build/tmp/deploy/ipk/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.14. build/tmp/deploy/images/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy-images"></a>5.2.14. <code class="filename">build/tmp/deploy/images/</code>
15</h3></div></div></div>
16<p>
17 This directory receives complete filesystem images.
18 If you want to flash the resulting image from a build onto a device, look here for the image.
19 </p>
20<p>
21 Be careful when deleting files in this directory.
22 You can safely delete old images from this directory (e.g.
23 <code class="filename">core-image-*</code>, <code class="filename">hob-image-*</code>,
24 etc.).
25 However, the kernel (<code class="filename">*zImage*</code>, <code class="filename">*uImage*</code>, etc.),
26 bootloader and other supplementary files might be deployed here prior to building an
27 image.
28 Because these files, however, are not directly produced from the image, if you
29 delete them they will not be automatically re-created when you build the image again.
30 </p>
31<p>
32 If you do accidentally delete files here, you will need to force them to be
33 re-created.
34 In order to do that, you will need to know the target that produced them.
35 For example, these commands rebuild and re-create the kernel files:
36 </p>
37<pre class="literallayout">
38 $ bitbake -c clean virtual/kernel
39 $ bitbake virtual/kernel
40 </pre>
41<p>
42 </p>
43</div></body>
44</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-ipk.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-ipk.html
deleted file mode 100644
index 9975833326..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-ipk.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.15. build/tmp/deploy/ipk/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-deploy-images.html" title="5.2.14. build/tmp/deploy/images/">
10<link rel="next" href="structure-build-tmp-sysroots.html" title="5.2.16. build/tmp/sysroots/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.15. build/tmp/deploy/ipk/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy-ipk"></a>5.2.15. <code class="filename">build/tmp/deploy/ipk/</code>
15</h3></div></div></div>
16<p>
17 This directory receives <code class="filename">.ipk</code> packages produced by
18 the build process.</p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-licenses.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-licenses.html
deleted file mode 100644
index b3ec898551..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-licenses.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.13. build/tmp/deploy/licenses/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-deploy-rpm.html" title="5.2.12. build/tmp/deploy/rpm/">
10<link rel="next" href="structure-build-tmp-deploy-images.html" title="5.2.14. build/tmp/deploy/images/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.13. build/tmp/deploy/licenses/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy-licenses"></a>5.2.13. <code class="filename">build/tmp/deploy/licenses/</code>
15</h3></div></div></div>
16<p>
17 This directory receives package licensing information.
18 For example, the directory contains sub-directories for <code class="filename">bash</code>,
19 <code class="filename">busybox</code>, and <code class="filename">eglibc</code> (among others) that in turn
20 contain appropriate <code class="filename">COPYING</code> license files with other licensing information.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-rpm.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-rpm.html
deleted file mode 100644
index 1579e1131e..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-rpm.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.12. build/tmp/deploy/rpm/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-deploy-deb.html" title="5.2.11. build/tmp/deploy/deb/">
10<link rel="next" href="structure-build-tmp-deploy-licenses.html" title="5.2.13. build/tmp/deploy/licenses/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.12. build/tmp/deploy/rpm/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy-rpm"></a>5.2.12. <code class="filename">build/tmp/deploy/rpm/</code>
15</h3></div></div></div>
16<p>
17 This directory receives any <code class="filename">.rpm</code> packages produced by
18 the build process.
19 The packages are sorted into feeds for different architecture types.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy.html
deleted file mode 100644
index b50f20802f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.10. build/tmp/deploy/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-cache.html" title="5.2.9. build/tmp/cache/">
10<link rel="next" href="structure-build-tmp-deploy-deb.html" title="5.2.11. build/tmp/deploy/deb/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.10. build/tmp/deploy/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy"></a>5.2.10. <code class="filename">build/tmp/deploy/</code>
15</h3></div></div></div>
16<p>
17 This directory contains any 'end result' output from the OpenEmbedded build process.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-log.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-log.html
deleted file mode 100644
index bd7f7053cf..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-log.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.18. build/tmp/log/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-stamps.html" title="5.2.17. build/tmp/stamps/">
10<link rel="next" href="structure-build-tmp-pkgdata.html" title="5.2.19. build/tmp/pkgdata/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.18. build/tmp/log/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-log"></a>5.2.18. <code class="filename">build/tmp/log/</code>
15</h3></div></div></div>
16<p>
17 This directory contains general logs that are not otherwise placed using the
18 package's <code class="filename"><a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">WORKDIR</a></code>.
19 Examples of logs are the output from the <code class="filename">check_pkg</code> or
20 <code class="filename">distro_check</code> tasks.
21 Running a build does not necessarily mean this directory is created.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-pkgdata.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-pkgdata.html
deleted file mode 100644
index 2fdad1ee31..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-pkgdata.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.19. build/tmp/pkgdata/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-log.html" title="5.2.18. build/tmp/log/">
10<link rel="next" href="structure-build-tmp-work.html" title="5.2.20. build/tmp/work/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.19. build/tmp/pkgdata/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-pkgdata"></a>5.2.19. <code class="filename">build/tmp/pkgdata/</code>
15</h3></div></div></div>
16<p>
17 This directory contains intermediate packaging data that is used later in the packaging process.
18 For more information, see the "<a class="link" href="ref-classes-package.html" title="7.13. Packaging - package*.bbclass">Packaging - package*.bbclass</a>" section.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-stamps.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-stamps.html
deleted file mode 100644
index a6f77c8ff3..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-stamps.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.17. build/tmp/stamps/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-sysroots.html" title="5.2.16. build/tmp/sysroots/">
10<link rel="next" href="structure-build-tmp-log.html" title="5.2.18. build/tmp/log/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.17. build/tmp/stamps/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-stamps"></a>5.2.17. <code class="filename">build/tmp/stamps/</code>
15</h3></div></div></div>
16<p>
17 This directory holds information that that BitBake uses for accounting purposes
18 to track what tasks have run and when they have run.
19 The directory is sub-divided by architecture.
20 The files in the directory are empty of data.
21 However, BitBake uses the filenames and timestamps for tracking purposes.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-sysroots.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-sysroots.html
deleted file mode 100644
index 10a74d805e..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-sysroots.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.16. build/tmp/sysroots/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-deploy-ipk.html" title="5.2.15. build/tmp/deploy/ipk/">
10<link rel="next" href="structure-build-tmp-stamps.html" title="5.2.17. build/tmp/stamps/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.16. build/tmp/sysroots/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-sysroots"></a>5.2.16. <code class="filename">build/tmp/sysroots/</code>
15</h3></div></div></div>
16<p>
17 This directory contains shared header files and libraries as well as other shared
18 data.
19 Packages that need to share output with other packages do so within this directory.
20 The directory is subdivided by architecture so multiple builds can run within
21 the one Build Directory.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html
deleted file mode 100644
index aa78c18b5d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html
+++ /dev/null
@@ -1,52 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.20. build/tmp/work/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-pkgdata.html" title="5.2.19. build/tmp/pkgdata/">
10<link rel="next" href="structure-meta.html" title="5.3. The Metadata - meta/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.20. build/tmp/work/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-work"></a>5.2.20. <code class="filename">build/tmp/work/</code>
15</h3></div></div></div>
16<p>
17 This directory contains architecture-specific work sub-directories for packages built by BitBake.
18 All tasks execute from a work directory.
19 For example, the source for a particular package is unpacked, patched, configured and compiled all
20 within its own work directory.
21 Within the work directory, organization is based on the package group for which the source
22 is being compiled.
23 </p>
24<p>
25 It is worth considering the structure of a typical work directory.
26 As an example, consider the <code class="filename">linux-yocto-kernel-3.0</code>
27 on the machine <code class="filename">qemux86</code>
28 built within the Yocto Project.
29 For this package, a work directory of
30 <code class="filename">tmp/work/qemux86-poky-linux/linux-yocto-3.0+git1+&lt;.....&gt;</code>,
31 referred to as <code class="filename"><a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">WORKDIR</a></code>, is created.
32 Within this directory, the source is unpacked to
33 <code class="filename">linux-qemux86-standard-build</code> and then patched by Quilt
34 (see the
35 "<a class="link" href="../dev-manual/using-a-quilt-workflow.html" target="_self">Modifying Package
36 Source Code with Quilt</a>" section in the Yocto Project Development Manual.
37 Within the <code class="filename">linux-qemux86-standard-build</code> directory,
38 standard Quilt directories <code class="filename">linux-3.0/patches</code>
39 and <code class="filename">linux-3.0/.pc</code> are created,
40 and standard Quilt commands can be used.
41 </p>
42<p>
43 There are other directories generated within WORKDIR.
44 The most important directory is WORKDIR<code class="filename">/temp/</code>, which has log files for each
45 task (<code class="filename">log.do_*.pid</code>) and contains the scripts BitBake runs for
46 each task (<code class="filename">run.do_*.pid</code>).
47 The WORKDIR<code class="filename">/image/</code> directory is where "make
48 install" places its output that is then split into sub-packages
49 within WORKDIR<code class="filename">/packages-split/</code>.
50 </p>
51</div></body>
52</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp.html
deleted file mode 100644
index 216d255c78..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp.html
+++ /dev/null
@@ -1,26 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.7. build/tmp/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-sstate-cache.html" title="5.2.6. build/sstate-cache/">
10<link rel="next" href="structure-build-tmp-buildstats.html" title="5.2.8. build/tmp/buildstats/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.7. build/tmp/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp"></a>5.2.7. <code class="filename">build/tmp/</code>
15</h3></div></div></div>
16<p>
17 This directory receives all the OpenEmbedded build system's output.
18 BitBake creates this directory if it does not exist.
19 As a last resort, to clean up a build and start it from scratch (other than the downloads),
20 you can remove everything in the <code class="filename">tmp</code> directory or get rid of the
21 directory completely.
22 If you do, you should also completely remove the <code class="filename">build/sstate-cache</code>
23 directory as well.
24 </p>
25</div></body>
26</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build.html
deleted file mode 100644
index c3b9ae5054..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build.html
+++ /dev/null
@@ -1,15 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2. The Build Directory - build/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-structure.html" title="Chapter 5. Source Directory Structure">
9<link rel="prev" href="structure-basic-top-level.html" title="5.1.11. LICENSE, README, and README.hardware">
10<link rel="next" href="structure-build-pseudodone.html" title="5.2.1. build/pseudodone">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2. The Build Directory - build/"><div class="titlepage"><div><div><h2 class="title" style="clear: both">
13<a name="structure-build"></a>5.2. The Build Directory - <code class="filename">build/</code>
14</h2></div></div></div></div></body>
15</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-bitbake.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-bitbake.html
deleted file mode 100644
index aca036d970..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-bitbake.html
+++ /dev/null
@@ -1,40 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.1. bitbake/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core.html" title="5.1. Top level core components">
10<link rel="next" href="structure-core-build.html" title="5.1.2. build/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.1. bitbake/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-bitbake"></a>5.1.1. <code class="filename">bitbake/</code>
15</h3></div></div></div>
16<p>
17 The <a class="ulink" href="source-directory" target="_self">Source Directory</a>
18 includes a copy of BitBake for ease of use.
19 The copy usually matches the current stable BitBake release from the BitBake project.
20 BitBake, a metadata interpreter, reads the Yocto Project metadata and runs the tasks
21 defined by that data.
22 Failures are usually from the metadata and not from BitBake itself.
23 Consequently, most users do not need to worry about BitBake.
24 </p>
25<p>
26 When you run the <code class="filename">bitbake</code> command, the wrapper script in
27 <code class="filename">scripts/</code> is executed to run the main BitBake executable,
28 which resides in the <code class="filename">bitbake/bin/</code> directory.
29 Sourcing the <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a>
30 script places the <code class="filename">scripts</code> and <code class="filename">bitbake/bin</code>
31 directories (in that order) into the shell's <code class="filename">PATH</code> environment
32 variable.
33 </p>
34<p>
35 For more information on BitBake, see the BitBake documentation
36 inculded in the <code class="filename">bitbake/doc/manual</code> directory of the
37 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
38 </p>
39</div></body>
40</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-build.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-build.html
deleted file mode 100644
index 23f5549b5b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-build.html
+++ /dev/null
@@ -1,33 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.2. build/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-bitbake.html" title="5.1.1. bitbake/">
10<link rel="next" href="handbook.html" title="5.1.3. documentation">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.2. build/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-build"></a>5.1.2. <code class="filename">build/</code>
15</h3></div></div></div>
16<p>
17 This directory contains user configuration files and the output
18 generated by the OpenEmbedded build system in its standard configuration where
19 the source tree is combined with the output.
20 The <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>
21 is created initially when you <code class="filename">source</code>
22 the OpenEmbedded build environment setup script <code class="filename">oe-init-build-env</code>.
23 </p>
24<p>
25 It is also possible to place output and configuration
26 files in a directory separate from the
27 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>
28 by providing a directory name when you <code class="filename">source</code>
29 the setup script.
30 For information on separating output from your local Source Directory files, see <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a>.
31 </p>
32</div></body>
33</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto-bsp.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto-bsp.html
deleted file mode 100644
index 29eff27053..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto-bsp.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.6. meta-yocto-bsp/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-meta-yocto.html" title="5.1.5. meta-yocto/">
10<link rel="next" href="structure-meta-hob.html" title="5.1.7. meta-hob/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.6. meta-yocto-bsp/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-meta-yocto-bsp"></a>5.1.6. <code class="filename">meta-yocto-bsp/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the Yocto Project reference
18 hardware BSPs.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto.html
deleted file mode 100644
index e9a8e8e56b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta-yocto.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.5. meta-yocto/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-meta.html" title="5.1.4. meta/">
10<link rel="next" href="structure-core-meta-yocto-bsp.html" title="5.1.6. meta-yocto-bsp/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.5. meta-yocto/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-meta-yocto"></a>5.1.5. <code class="filename">meta-yocto/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the configuration for the Poky
18 reference distribution.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta.html
deleted file mode 100644
index 9a7cee2c13..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-meta.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.4. meta/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="handbook.html" title="5.1.3. documentation">
10<link rel="next" href="structure-core-meta-yocto.html" title="5.1.5. meta-yocto/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.4. meta/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-meta"></a>5.1.4. <code class="filename">meta/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the OpenEmbedded Core metadata.
18 The directory holds recipes, common classes, and machine
19 configuration for emulated targets (qemux86, qemuarm,
20 and so on.)
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html
deleted file mode 100644
index 64266a9482..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html
+++ /dev/null
@@ -1,53 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.10. oe-init-build-env</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-scripts.html" title="5.1.9. scripts/">
10<link rel="next" href="structure-basic-top-level.html" title="5.1.11. LICENSE, README, and README.hardware">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.10. oe-init-build-env">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-script"></a>5.1.10. <code class="filename">oe-init-build-env</code>
15</h3></div></div></div>
16<p>
17 This script sets up the OpenEmbedded build environment.
18 Running this script with the <code class="filename">source</code> command in
19 a shell makes changes to <code class="filename">PATH</code> and sets other core BitBake variables based on the
20 current working directory.
21 You need to run this script before running BitBake commands.
22 The script uses other scripts within the <code class="filename">scripts</code> directory to do
23 the bulk of the work.
24 </p>
25<p>
26 By default, running this script without a Build Directory argument creates the
27 <code class="filename">build</code> directory.
28 If you provide a Build Directory argument when you <code class="filename">source</code>
29 the script, you direct OpenEmbedded build system to create a
30 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a> of your choice.
31 For example, the following command creates a Build Directory named
32 <code class="filename">mybuilds</code> that is outside of the
33 <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>:
34 </p>
35<pre class="literallayout">
36 $ source oe-init-build-env ~/mybuilds
37 </pre>
38<p>
39 </p>
40<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
41<h3 class="title">Note</h3>
42 The OpenEmbedded build system does not support file or directory names that
43 contain spaces.
44 If you attempt to run the <code class="filename">oe-init-build-env</code> script
45 from a Source Directory that contains spaces in either the filenames
46 or directory names, the script returns an error indicating no such
47 file or directory.
48 Be sure to use a Source Directory free of names containing spaces.
49 </div>
50<p>
51 </p>
52</div></body>
53</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-scripts.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-scripts.html
deleted file mode 100644
index 6bc3bed649..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-scripts.html
+++ /dev/null
@@ -1,28 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.9. scripts/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-meta-skeleton.html" title="5.1.8. meta-skeleton/">
10<link rel="next" href="structure-core-script.html" title="5.1.10. oe-init-build-env">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.9. scripts/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-core-scripts"></a>5.1.9. <code class="filename">scripts/</code>
15</h3></div></div></div>
16<p>
17 This directory contains various integration scripts that implement
18 extra functionality in the Yocto Project environment (e.g. QEMU scripts).
19 The <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a> script appends this
20 directory to the shell's <code class="filename">PATH</code> environment variable.
21 </p>
22<p>
23 The <code class="filename">scripts</code> directory has useful scripts that assist contributing
24 back to the Yocto Project, such as <code class="filename">create_pull_request</code> and
25 <code class="filename">send_pull_request</code>.
26 </p>
27</div></body>
28</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core.html
deleted file mode 100644
index 51b6994b08..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core.html
+++ /dev/null
@@ -1,14 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1. Top level core components</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-structure.html" title="Chapter 5. Source Directory Structure">
9<link rel="prev" href="ref-structure.html" title="Chapter 5. Source Directory Structure">
10<link rel="next" href="structure-core-bitbake.html" title="5.1.1. bitbake/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1. Top level core components"><div class="titlepage"><div><div><h2 class="title" style="clear: both">
13<a name="structure-core"></a>5.1. Top level core components</h2></div></div></div></div></body>
14</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-classes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-classes.html
deleted file mode 100644
index 34cc0ffe32..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-classes.html
+++ /dev/null
@@ -1,30 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.1. meta/classes/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta.html" title="5.3. The Metadata - meta/">
10<link rel="next" href="structure-meta-conf.html" title="5.3.2. meta/conf/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.1. meta/classes/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-classes"></a>5.3.1. <code class="filename">meta/classes/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the <code class="filename">*.bbclass</code> files.
18 Class files are used to abstract common code so it can be reused by multiple
19 packages.
20 Every package inherits the <code class="filename">base.bbclass</code> file.
21 Examples of other important classes are <code class="filename">autotools.bbclass</code>, which
22 in theory allows any Autotool-enabled package to work with the Yocto Project with minimal effort.
23 Another example is <code class="filename">kernel.bbclass</code> that contains common code and functions
24 for working with the Linux kernel.
25 Functions like image generation or packaging also have their specific class files
26 such as <code class="filename">image.bbclass</code>, <code class="filename">rootfs_*.bbclass</code> and
27 <code class="filename">package*.bbclass</code>.
28 </p>
29</div></body>
30</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-distro.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-distro.html
deleted file mode 100644
index b8b4fe0c01..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-distro.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.4. meta/conf/distro/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-conf-machine.html" title="5.3.3. meta/conf/machine/">
10<link rel="next" href="structure-meta-recipes-bsp.html" title="5.3.5. meta/recipes-bsp/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.4. meta/conf/distro/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-conf-distro"></a>5.3.4. <code class="filename">meta/conf/distro/</code>
15</h3></div></div></div>
16<p>
17 Any distribution-specific configuration is controlled from this directory.
18 For the Yocto Project, the <code class="filename">defaultsetup.conf</code> is the main file here.
19 This directory includes the versions and the
20 <code class="filename">SRCDATE</code> definitions for applications that are configured here.
21 An example of an alternative configuration might be <code class="filename">poky-bleeding.conf</code>.
22 Although this file mainly inherits its configuration from Poky.
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-machine.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-machine.html
deleted file mode 100644
index 80ccb8dedc..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf-machine.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.3. meta/conf/machine/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-conf.html" title="5.3.2. meta/conf/">
10<link rel="next" href="structure-meta-conf-distro.html" title="5.3.4. meta/conf/distro/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.3. meta/conf/machine/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-conf-machine"></a>5.3.3. <code class="filename">meta/conf/machine/</code>
15</h3></div></div></div>
16<p>
17 This directory contains all the machine configuration files.
18 If you set <code class="filename">MACHINE="qemux86"</code>,
19 the OpenEmbedded build system looks for a <code class="filename">qemux86.conf</code> file in this
20 directory.
21 The <code class="filename">include</code> directory contains various data common to multiple machines.
22 If you want to add support for a new machine to the Yocto Project, look in this directory.
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf.html
deleted file mode 100644
index da88f4b111..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-conf.html
+++ /dev/null
@@ -1,27 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.2. meta/conf/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-classes.html" title="5.3.1. meta/classes/">
10<link rel="next" href="structure-meta-conf-machine.html" title="5.3.3. meta/conf/machine/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.2. meta/conf/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-conf"></a>5.3.2. <code class="filename">meta/conf/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the core set of configuration files that start from
18 <code class="filename">bitbake.conf</code> and from which all other configuration
19 files are included.
20 See the include statements at the end of the file and you will note that even
21 <code class="filename">local.conf</code> is loaded from there.
22 While <code class="filename">bitbake.conf</code> sets up the defaults, you can often override
23 these by using the (<code class="filename">local.conf</code>) file, machine file or
24 the distribution configuration file.
25 </p>
26</div></body>
27</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-hob.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-hob.html
deleted file mode 100644
index a8fb22fc08..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-hob.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.7. meta-hob/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-core-meta-yocto-bsp.html" title="5.1.6. meta-yocto-bsp/">
10<link rel="next" href="structure-meta-skeleton.html" title="5.1.8. meta-skeleton/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.7. meta-hob/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-hob"></a>5.1.7. <code class="filename">meta-hob/</code>
15</h3></div></div></div>
16<p>
17 This directory contains template recipes used by the
18 <a class="ulink" href="http://www.yoctoproject.org/projects/hob" target="_self">Hob</a>
19 build UI.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-bsp.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-bsp.html
deleted file mode 100644
index 7adf2d392c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-bsp.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.5. meta/recipes-bsp/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-conf-distro.html" title="5.3.4. meta/conf/distro/">
10<link rel="next" href="structure-meta-recipes-connectivity.html" title="5.3.6. meta/recipes-connectivity/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.5. meta/recipes-bsp/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-bsp"></a>5.3.5. <code class="filename">meta/recipes-bsp/</code>
15</h3></div></div></div>
16<p>
17 This directory contains anything linking to specific hardware or hardware
18 configuration information such as "u-boot" and "grub".
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-connectivity.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-connectivity.html
deleted file mode 100644
index 112544e110..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-connectivity.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.6. meta/recipes-connectivity/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-bsp.html" title="5.3.5. meta/recipes-bsp/">
10<link rel="next" href="structure-meta-recipes-core.html" title="5.3.7. meta/recipes-core/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.6. meta/recipes-connectivity/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-connectivity"></a>5.3.6. <code class="filename">meta/recipes-connectivity/</code>
15</h3></div></div></div>
16<p>
17 This directory contains libraries and applications related to communication with other devices.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-core.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-core.html
deleted file mode 100644
index bd0542eb92..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-core.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.7. meta/recipes-core/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-connectivity.html" title="5.3.6. meta/recipes-connectivity/">
10<link rel="next" href="structure-meta-recipes-devtools.html" title="5.3.8. meta/recipes-devtools/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.7. meta/recipes-core/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-core"></a>5.3.7. <code class="filename">meta/recipes-core/</code>
15</h3></div></div></div>
16<p>
17 This directory contains what is needed to build a basic working Linux image
18 including commonly used dependencies.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-devtools.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-devtools.html
deleted file mode 100644
index 25a38d9f01..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-devtools.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.8. meta/recipes-devtools/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-core.html" title="5.3.7. meta/recipes-core/">
10<link rel="next" href="structure-meta-recipes-extended.html" title="5.3.9. meta/recipes-extended/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.8. meta/recipes-devtools/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-devtools"></a>5.3.8. <code class="filename">meta/recipes-devtools/</code>
15</h3></div></div></div>
16<p>
17 This directory contains tools that are primarily used by the build system.
18 The tools, however, can also be used on targets.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-extended.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-extended.html
deleted file mode 100644
index b5506ff651..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-extended.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.9. meta/recipes-extended/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-devtools.html" title="5.3.8. meta/recipes-devtools/">
10<link rel="next" href="structure-meta-recipes-gnome.html" title="5.3.10. meta/recipes-gnome/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.9. meta/recipes-extended/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-extended"></a>5.3.9. <code class="filename">meta/recipes-extended/</code>
15</h3></div></div></div>
16<p>
17 This directory contains non-essential applications that add features compared to the
18 alternatives in core.
19 You might need this directory for full tool functionality or for Linux Standard Base (LSB)
20 compliance.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-gnome.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-gnome.html
deleted file mode 100644
index 769447f2ff..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-gnome.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.10. meta/recipes-gnome/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-extended.html" title="5.3.9. meta/recipes-extended/">
10<link rel="next" href="structure-meta-recipes-graphics.html" title="5.3.11. meta/recipes-graphics/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.10. meta/recipes-gnome/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-gnome"></a>5.3.10. <code class="filename">meta/recipes-gnome/</code>
15</h3></div></div></div>
16<p>
17 This directory contains all things related to the GTK+ application framework.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-graphics.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-graphics.html
deleted file mode 100644
index 7a0a3e4253..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-graphics.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.11. meta/recipes-graphics/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-gnome.html" title="5.3.10. meta/recipes-gnome/">
10<link rel="next" href="structure-meta-recipes-kernel.html" title="5.3.12. meta/recipes-kernel/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.11. meta/recipes-graphics/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-graphics"></a>5.3.11. <code class="filename">meta/recipes-graphics/</code>
15</h3></div></div></div>
16<p>
17 This directory contains X and other graphically related system libraries
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-kernel.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-kernel.html
deleted file mode 100644
index 1cb7a06f81..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-kernel.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.12. meta/recipes-kernel/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-graphics.html" title="5.3.11. meta/recipes-graphics/">
10<link rel="next" href="structure-meta-recipes-multimedia.html" title="5.3.13. meta/recipes-multimedia/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.12. meta/recipes-kernel/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-kernel"></a>5.3.12. <code class="filename">meta/recipes-kernel/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the kernel and generic applications and libraries that
18 have strong kernel dependencies.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-multimedia.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-multimedia.html
deleted file mode 100644
index 08c9f3cda9..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-multimedia.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.13. meta/recipes-multimedia/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-kernel.html" title="5.3.12. meta/recipes-kernel/">
10<link rel="next" href="structure-meta-recipes-qt.html" title="5.3.14. meta/recipes-qt/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.13. meta/recipes-multimedia/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-multimedia"></a>5.3.13. <code class="filename">meta/recipes-multimedia/</code>
15</h3></div></div></div>
16<p>
17 This directory contains codecs and support utilities for audio, images and video.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-qt.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-qt.html
deleted file mode 100644
index bb6eca2742..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-qt.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.14. meta/recipes-qt/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-multimedia.html" title="5.3.13. meta/recipes-multimedia/">
10<link rel="next" href="structure-meta-recipes-rt.html" title="5.3.15. meta/recipes-rt/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.14. meta/recipes-qt/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-qt"></a>5.3.14. <code class="filename">meta/recipes-qt/</code>
15</h3></div></div></div>
16<p>
17 This directory contains all things related to the Qt application framework.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-rt.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-rt.html
deleted file mode 100644
index 249e442891..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-rt.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.15. meta/recipes-rt/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-qt.html" title="5.3.14. meta/recipes-qt/">
10<link rel="next" href="structure-meta-recipes-sato.html" title="5.3.16. meta/recipes-sato/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.15. meta/recipes-rt/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-rt"></a>5.3.15. <code class="filename">meta/recipes-rt/</code>
15</h3></div></div></div>
16<p>
17 This directory contains package and image recipes for using and testing
18 the <code class="filename">PREEMPT_RT</code> kernel.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-sato.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-sato.html
deleted file mode 100644
index d6a27ffb4f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-sato.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.16. meta/recipes-sato/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-rt.html" title="5.3.15. meta/recipes-rt/">
10<link rel="next" href="structure-meta-recipes-support.html" title="5.3.17. meta/recipes-support/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.16. meta/recipes-sato/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-sato"></a>5.3.16. <code class="filename">meta/recipes-sato/</code>
15</h3></div></div></div>
16<p>
17 This directory contains the Sato demo/reference UI/UX and its associated applications
18 and configuration data.
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-support.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-support.html
deleted file mode 100644
index 7e152acfa2..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-support.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.17. meta/recipes-support/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-sato.html" title="5.3.16. meta/recipes-sato/">
10<link rel="next" href="structure-meta-site.html" title="5.3.18. meta/site/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.17. meta/recipes-support/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-support"></a>5.3.17. <code class="filename">meta/recipes-support/</code>
15</h3></div></div></div>
16<p>
17 This directory contains recipes that used by other recipes, but that are not directly
18 included in images (i.e. dependencies of other recipes).
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-txt.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-txt.html
deleted file mode 100644
index 42bb7a678d..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-recipes-txt.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.19. meta/recipes.txt</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-site.html" title="5.3.18. meta/site/">
10<link rel="next" href="ref-bitbake.html" title="Chapter 6. BitBake">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.19. meta/recipes.txt">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-recipes-txt"></a>5.3.19. <code class="filename">meta/recipes.txt</code>
15</h3></div></div></div>
16<p>
17 This file is a description of the contents of <code class="filename">recipes-*</code>.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-site.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-site.html
deleted file mode 100644
index 567eec8221..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-site.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3.18. meta/site/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-meta.html" title="5.3. The Metadata - meta/">
9<link rel="prev" href="structure-meta-recipes-support.html" title="5.3.17. meta/recipes-support/">
10<link rel="next" href="structure-meta-recipes-txt.html" title="5.3.19. meta/recipes.txt">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3.18. meta/site/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-site"></a>5.3.18. <code class="filename">meta/site/</code>
15</h3></div></div></div>
16<p>
17 This directory contains a list of cached results for various architectures.
18 Because certain "autoconf" test results cannot be determined when cross-compiling due to
19 the tests not able to run on a live system, the information in this directory is
20 passed to "autoconf" for the various architectures.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-skeleton.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-skeleton.html
deleted file mode 100644
index b67bb60e48..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta-skeleton.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.1.8. meta-skeleton/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="structure-core.html" title="5.1. Top level core components">
9<link rel="prev" href="structure-meta-hob.html" title="5.1.7. meta-hob/">
10<link rel="next" href="structure-core-scripts.html" title="5.1.9. scripts/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.8. meta-skeleton/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-meta-skeleton"></a>5.1.8. <code class="filename">meta-skeleton/</code>
15</h3></div></div></div>
16<p>
17 This directory contains template recipes for BSP and kernel development.
18 </p>
19</div></body>
20</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta.html
deleted file mode 100644
index 7f132b54fb..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-meta.html
+++ /dev/null
@@ -1,21 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.3. The Metadata - meta/</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="ref-structure.html" title="Chapter 5. Source Directory Structure">
9<link rel="prev" href="structure-build-tmp-work.html" title="5.2.20. build/tmp/work/">
10<link rel="next" href="structure-meta-classes.html" title="5.3.1. meta/classes/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.3. The Metadata - meta/">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="structure-meta"></a>5.3. The Metadata - <code class="filename">meta/</code>
15</h2></div></div></div>
16<p>
17 As mentioned previously, metadata is the core of the Yocto Project.
18 Metadata has several important subdivisions:
19 </p>
20</div></body>
21</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/support.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/support.html
deleted file mode 100644
index 4e0a1efb0f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/support.html
+++ /dev/null
@@ -1,34 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.3.1. Support</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="x32.html" title="3.3. x32">
9<link rel="prev" href="x32.html" title="3.3. x32">
10<link rel="next" href="future-development-and-limitations.html" title="3.3.2. Future Development and Limitations">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.3.1. Support">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="support"></a>3.3.1. Support</h3></div></div></div>
15<p>
16 While the x32 psABI specifications are not fully finalized, this Yocto Project
17 release supports current development specifications of x32 psABI.
18 As of this release of the Yocto Project, x32 psABI support exists as follows:
19 </p>
20<div class="itemizedlist"><ul class="itemizedlist" type="disc">
21<li class="listitem"><p>You can create packages and images in x32 psABI format on x86_64 architecture targets.
22 </p></li>
23<li class="listitem"><p>You can use the x32 psABI support through the <code class="filename">meta-x32</code>
24 layer on top of the OE-core/Yocto layer.</p></li>
25<li class="listitem"><p>The toolchain from the <code class="filename">experimental/meta-x32</code> layer
26 is used for building x32 psABI program binaries.</p></li>
27<li class="listitem"><p>You can successfully build many recipes with the x32 toolchain.</p></li>
28<li class="listitem"><p>You can create and boot <code class="filename">core-image-minimal</code> and
29 <code class="filename">core-image-sato</code> images.</p></li>
30</ul></div>
31<p>
32 </p>
33</div></body>
34</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/technical-details.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/technical-details.html
deleted file mode 100644
index 1a54121c49..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/technical-details.html
+++ /dev/null
@@ -1,50 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 3. Technical Details</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="examining-build-history-information.html" title="2.4.2.4. Examining Build History Information">
10<link rel="next" href="usingpoky-components.html" title="3.1. Yocto Project Components">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 3. Technical Details">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="technical-details"></a>Chapter 3. Technical Details</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="usingpoky-components.html">3.1. Yocto Project Components</a></span></dt>
19<dd><dl>
20<dt><span class="section"><a href="usingpoky-components-bitbake.html">3.1.1. BitBake</a></span></dt>
21<dt><span class="section"><a href="usingpoky-components-metadata.html">3.1.2. Metadata (Recipes)</a></span></dt>
22<dt><span class="section"><a href="usingpoky-components-classes.html">3.1.3. Classes</a></span></dt>
23<dt><span class="section"><a href="usingpoky-components-configuration.html">3.1.4. Configuration</a></span></dt>
24</dl></dd>
25<dt><span class="section"><a href="shared-state-cache.html">3.2. Shared State Cache</a></span></dt>
26<dd><dl>
27<dt><span class="section"><a href="overall-architecture.html">3.2.1. Overall Architecture</a></span></dt>
28<dt><span class="section"><a href="checksums.html">3.2.2. Checksums (Signatures)</a></span></dt>
29<dt><span class="section"><a href="shared-state.html">3.2.3. Shared State</a></span></dt>
30<dt><span class="section"><a href="tips-and-tricks.html">3.2.4. Tips and Tricks</a></span></dt>
31</dl></dd>
32<dt><span class="section"><a href="x32.html">3.3. x32</a></span></dt>
33<dd><dl>
34<dt><span class="section"><a href="support.html">3.3.1. Support</a></span></dt>
35<dt><span class="section"><a href="future-development-and-limitations.html">3.3.2. Future Development and Limitations</a></span></dt>
36<dt><span class="section"><a href="using-x32-right-now.html">3.3.3. Using x32 Right Now</a></span></dt>
37</dl></dd>
38<dt><span class="section"><a href="licenses.html">3.4. Licenses</a></span></dt>
39<dd><dl>
40<dt><span class="section"><a href="usingpoky-configuring-LIC_FILES_CHKSUM.html">3.4.1. Tracking License Changes</a></span></dt>
41<dt><span class="section"><a href="enabling-commercially-licensed-recipes.html">3.4.2. Enabling Commercially Licensed Recipes</a></span></dt>
42</dl></dd>
43</dl>
44</div>
45<p>
46 This chapter provides technical details for various parts of the Yocto Project.
47 Currently, topics include Yocto Project components and shared state (sstate) cache.
48 </p>
49</div></body>
50</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/tips-and-tricks.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/tips-and-tricks.html
deleted file mode 100644
index 78773b954a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/tips-and-tricks.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.4. Tips and Tricks</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="shared-state-cache.html" title="3.2. Shared State Cache">
9<link rel="prev" href="shared-state.html" title="3.2.3. Shared State">
10<link rel="next" href="debugging.html" title="3.2.4.1. Debugging">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.4. Tips and Tricks">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="tips-and-tricks"></a>3.2.4. Tips and Tricks</h3></div></div></div>
15<p>
16 The code in the build system that supports incremental builds is not
17 simple code.
18 This section presents some tips and tricks that help you work around
19 issues related to shared state code.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ubuntu-packages.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ubuntu-packages.html
deleted file mode 100644
index 63c0118692..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ubuntu-packages.html
+++ /dev/null
@@ -1,60 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>1.3.2.1. Ubuntu</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="required-packages-for-the-host-development-system.html" title="1.3.2. Required Packages for the Host Development System">
9<link rel="prev" href="required-packages-for-the-host-development-system.html" title="1.3.2. Required Packages for the Host Development System">
10<link rel="next" href="fedora-packages.html" title="1.3.2.2. Fedora Packages">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="1.3.2.1. Ubuntu">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="ubuntu-packages"></a>1.3.2.1. Ubuntu</h4></div></div></div>
15<p>
16 The following list shows the required packages by function
17 given a supported Ubuntu Linux distribution:
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem">
21<p><span class="emphasis"><em>Essentials:</em></span>
22 Packages needed to build an image on a headless
23 system:
24 </p>
25<pre class="literallayout">
26 $ sudo apt-get install gawk wget git-core diffstat unzip texinfo \
27 build-essential chrpath
28 </pre>
29</li>
30<li class="listitem">
31<p><span class="emphasis"><em>Graphical Extras:</em></span>
32 Packages recommended if the host system has graphics support:
33 </p>
34<pre class="literallayout">
35 $ sudo apt-get install libsdl1.2-dev xterm
36 </pre>
37</li>
38<li class="listitem">
39<p><span class="emphasis"><em>Documentation:</em></span>
40 Packages needed if you are going to build out the
41 Yocto Project documentation manuals:
42 </p>
43<pre class="literallayout">
44 $ sudo apt-get install make xsltproc docbook-utils fop
45 </pre>
46</li>
47<li class="listitem">
48<p><span class="emphasis"><em>ADT Installer Extras:</em></span>
49 Packages needed if you are going to be using the
50 <a class="link" href="../adt-manual/using-the-adt-installer.html" target="_self">Application Development Toolkit (ADT) Installer</a>:
51 </p>
52<pre class="literallayout">
53 $ sudo apt-get install autoconf automake libtool libglib2.0-dev
54 </pre>
55</li>
56</ul></div>
57<p>
58 </p>
59</div></body>
60</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/understanding-what-the-build-history-contains.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/understanding-what-the-build-history-contains.html
deleted file mode 100644
index cdaa962f57..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/understanding-what-the-build-history-contains.html
+++ /dev/null
@@ -1,25 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.2. Understanding What the Build History Contains</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="maintaining-build-output-quality.html" title="2.4. Maintaining Build Output Quality">
9<link rel="prev" href="enabling-and-disabling-build-history.html" title="2.4.1. Enabling and Disabling Build History">
10<link rel="next" href="build-history-package-information.html" title="2.4.2.1. Build History Package Information">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.2. Understanding What the Build History Contains">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="understanding-what-the-build-history-contains"></a>2.4.2. Understanding What the Build History Contains</h3></div></div></div>
15<p>
16 Build history information is kept in
17 <a class="link" href="ref-variables-glos.html#var-TMPDIR" title="TMPDIR"><code class="filename">$TMPDIR</code></a><code class="filename">/buildhistory</code>
18 in the Build Directory.
19 The following is an example abbreviated listing:
20 </p>
21<table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="540"><tr style="height: 360px"><td align="center"><img src="figures/buildhistory.png" align="middle" width="540"></td></tr></table>
22<p>
23 </p>
24</div></body>
25</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/using-build-history-to-gather-image-information-only.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/using-build-history-to-gather-image-information-only.html
deleted file mode 100644
index 26c2a4d080..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/using-build-history-to-gather-image-information-only.html
+++ /dev/null
@@ -1,34 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.4.2.3. Using Build History to Gather Image Information Only</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="understanding-what-the-build-history-contains.html" title="2.4.2. Understanding What the Build History Contains">
9<link rel="prev" href="build-history-image-information.html" title="2.4.2.2. Build History Image Information">
10<link rel="next" href="examining-build-history-information.html" title="2.4.2.4. Examining Build History Information">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.4.2.3. Using Build History to Gather Image Information Only">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="using-build-history-to-gather-image-information-only"></a>2.4.2.3. Using Build History to Gather Image Information Only</h4></div></div></div>
15<p>
16 As you can see, build history produces image information,
17 including dependency graphs, so you can see why something
18 was pulled into the image.
19 If you are just interested in this information and not
20 interested in collecting history or any package information,
21 you can enable writing only image information without
22 any history by adding the following
23 to your <code class="filename">conf/local.conf</code> file found in the
24 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>:
25 </p>
26<pre class="literallayout">
27 INHERIT += "buildhistory"
28 BUILDHISTORY_COMMIT = "0"
29 BUILDHISTORY_FEATURES = "image"
30 </pre>
31<p>
32 </p>
33</div></body>
34</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/using-x32-right-now.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/using-x32-right-now.html
deleted file mode 100644
index 614b31ddaa..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/using-x32-right-now.html
+++ /dev/null
@@ -1,70 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.3.3. Using x32 Right Now</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="x32.html" title="3.3. x32">
9<link rel="prev" href="future-development-and-limitations.html" title="3.3.2. Future Development and Limitations">
10<link rel="next" href="licenses.html" title="3.4. Licenses">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.3.3. Using x32 Right Now">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="using-x32-right-now"></a>3.3.3. Using x32 Right Now</h3></div></div></div>
15<p>
16 Despite the fact the x32 psABI support is in development state for this release of the
17 Yocto Project, you can follow these steps to use the x32 spABI:
18 </p>
19<div class="itemizedlist"><ul class="itemizedlist" type="disc">
20<li class="listitem"><p>Add the <code class="filename">experimental/meta-x32</code> layer to your local
21 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
22 You can find the <code class="filename">experimental/meta-x32</code> source repository at
23 <a class="ulink" href="http://git.yoctoproject.org" target="_self">http://git.yoctoproject.org</a>.</p></li>
24<li class="listitem">
25<p>Edit your <code class="filename">conf/bblayers.conf</code> file so that it includes
26 the <code class="filename">meta-x32</code>.
27 Here is an example:
28 </p>
29<pre class="literallayout">
30 BBLAYERS ?= " \
31 /home/nitin/prj/poky.git/meta \
32 /home/nitin/prj/poky.git/meta-yocto \
33 /home/nitin/prj/poky.git/meta-yocto-bsp \
34 /home/nitin/prj/meta-x32.git \
35 "
36 </pre>
37</li>
38<li class="listitem">
39<p>Enable the x32 psABI tuning file for <code class="filename">x86_64</code>
40 machines by editing the <code class="filename">conf/local.conf</code> like this:
41 </p>
42<pre class="literallayout">
43 MACHINE = "qemux86-64"
44 DEFAULTTUNE = "x86-64-x32"
45 baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE', True) \
46 or 'INVALID'), True) or 'lib'}"
47 #MACHINE = "atom-pc"
48 #DEFAULTTUNE = "core2-64-x32"
49 </pre>
50</li>
51<li class="listitem">
52<p>As usual, use BitBake to build an image that supports the x32 psABI.
53 Here is an example:
54 </p>
55<pre class="literallayout">
56 $ bitake core-image-sato
57 </pre>
58</li>
59<li class="listitem">
60<p>As usual, run your image using QEMU:
61 </p>
62<pre class="literallayout">
63 $ runqemu qemux86-64 core-image-sato
64 </pre>
65</li>
66</ul></div>
67<p>
68 </p>
69</div></body>
70</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html
deleted file mode 100644
index e702578a24..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html
+++ /dev/null
@@ -1,58 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4.1.2. Explanation of Syntax</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-configuring-LIC_FILES_CHKSUM.html" title="3.4.1. Tracking License Changes">
9<link rel="prev" href="usingpoky-specifying-LIC_FILES_CHKSUM.html" title="3.4.1.1. Specifying the LIC_FILES_CHKSUM Variable">
10<link rel="next" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.1.2. Explanation of Syntax">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax"></a>3.4.1.2. Explanation of Syntax</h4></div></div></div>
15<p>
16 As mentioned in the previous section, the
17 <code class="filename">LIC_FILES_CHKSUM</code> variable lists all the
18 important files that contain the license text for the source code.
19 It is possible to specify a checksum for an entire file, or a specific section of a
20 file (specified by beginning and ending line numbers with the "beginline" and "endline"
21 parameters, respectively).
22 The latter is useful for source files with a license notice header,
23 README documents, and so forth.
24 If you do not use the "beginline" parameter, then it is assumed that the text begins on the
25 first line of the file.
26 Similarly, if you do not use the "endline" parameter, it is assumed that the license text
27 ends with the last line of the file.
28 </p>
29<p>
30 The "md5" parameter stores the md5 checksum of the license text.
31 If the license text changes in any way as compared to this parameter
32 then a mismatch occurs.
33 This mismatch triggers a build failure and notifies the developer.
34 Notification allows the developer to review and address the license text changes.
35 Also note that if a mismatch occurs during the build, the correct md5
36 checksum is placed in the build log and can be easily copied to the recipe.
37 </p>
38<p>
39 There is no limit to how many files you can specify using the
40 <code class="filename">LIC_FILES_CHKSUM</code> variable.
41 Generally, however, every project requires a few specifications for license tracking.
42 Many projects have a "COPYING" file that stores the license information for all the source
43 code files.
44 This practice allows you to just track the "COPYING" file as long as it is kept up to date.
45 </p>
46<div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;">
47<h3 class="title">Tip</h3>
48 If you specify an empty or invalid "md5" parameter, BitBake returns an md5 mis-match
49 error and displays the correct "md5" parameter value during the build.
50 The correct parameter is also captured in the build log.
51 </div>
52<div class="tip" title="Tip" style="margin-left: 0.5in; margin-right: 0.5in;">
53<h3 class="title">Tip</h3>
54 If the whole file contains only license text, you do not need to use the "beginline" and
55 "endline" parameters.
56 </div>
57</div></body>
58</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-build.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-build.html
deleted file mode 100644
index c1fa0e6c00..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-build.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.1. Running a Build</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
9<link rel="prev" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
10<link rel="next" href="build-overview.html" title="2.1.1. Build Overview">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1. Running a Build">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="usingpoky-build"></a>2.1. Running a Build</h2></div></div></div>
15<p>
16 This section provides a summary of the build process and provides information
17 for less obvious aspects of the build process.
18 For general information on how to build an image using the OpenEmbedded build
19 system, see the
20 "<a class="link" href="../yocto-project-qs/building-image.html" target="_self">Building an Image</a>"
21 section of the Yocto Project Quick Start.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html
deleted file mode 100644
index 184ffdbd2c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html
+++ /dev/null
@@ -1,66 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.1.1. BitBake</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-components.html" title="3.1. Yocto Project Components">
9<link rel="prev" href="usingpoky-components.html" title="3.1. Yocto Project Components">
10<link rel="next" href="usingpoky-components-metadata.html" title="3.1.2. Metadata (Recipes)">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.1. BitBake">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-components-bitbake"></a>3.1.1. BitBake</h3></div></div></div>
15<p>
16 BitBake is the tool at the heart of the OpenEmbedded build system and is responsible
17 for parsing the metadata, generating a list of tasks from it,
18 and then executing those tasks.
19 To see a list of the options BitBake supports, use the following help command:
20 </p>
21<pre class="literallayout">
22 $ bitbake --help
23 </pre>
24<p>
25 </p>
26<p>
27 The most common usage for BitBake is <code class="filename">bitbake &lt;packagename&gt;</code>, where
28 <code class="filename">packagename</code> is the name of the package you want to build
29 (referred to as the "target" in this manual).
30 The target often equates to the first part of a <code class="filename">.bb</code> filename.
31 So, to run the <code class="filename">matchbox-desktop_1.2.3.bb</code> file, you
32 might type the following:
33 </p>
34<pre class="literallayout">
35 $ bitbake matchbox-desktop
36 </pre>
37<p>
38 Several different versions of <code class="filename">matchbox-desktop</code> might exist.
39 BitBake chooses the one selected by the distribution configuration.
40 You can get more details about how BitBake chooses between different
41 target versions and providers in the
42 "<a class="link" href="ref-bitbake-providers.html" title="6.2. Preferences and Providers">Preferences and Providers</a>" section.
43 </p>
44<p>
45 BitBake also tries to execute any dependent tasks first.
46 So for example, before building <code class="filename">matchbox-desktop</code>, BitBake
47 would build a cross compiler and <code class="filename">eglibc</code> if they had not already
48 been built.
49 </p>
50<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
51<h3 class="title">Note</h3>This release of the Yocto Project does not support the <code class="filename">glibc</code>
52 GNU version of the Unix standard C library. By default, the OpenEmbedded build system
53 builds with <code class="filename">eglibc</code>.</div>
54<p>
55 </p>
56<p>
57 A useful BitBake option to consider is the <code class="filename">-k</code> or
58 <code class="filename">--continue</code> option.
59 This option instructs BitBake to try and continue processing the job as much
60 as possible even after encountering an error.
61 When an error occurs, the target that
62 failed and those that depend on it cannot be remade.
63 However, when you use this option other dependencies can still be processed.
64 </p>
65</div></body>
66</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-classes.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-classes.html
deleted file mode 100644
index 92427061ea..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-classes.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.1.3. Classes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-components.html" title="3.1. Yocto Project Components">
9<link rel="prev" href="usingpoky-components-metadata.html" title="3.1.2. Metadata (Recipes)">
10<link rel="next" href="usingpoky-components-configuration.html" title="3.1.4. Configuration">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.3. Classes">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-components-classes"></a>3.1.3. Classes</h3></div></div></div>
15<p>
16 Class files (<code class="filename">.bbclass</code>) contain information that is useful to share
17 between metadata files.
18 An example is the Autotools class, which contains
19 common settings for any application that Autotools uses.
20 The "<a class="link" href="ref-classes.html" title="Chapter 7. Classes">Classes</a>" chapter provides details
21 about common classes and how to use them.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-configuration.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-configuration.html
deleted file mode 100644
index 49e4e14649..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-configuration.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.1.4. Configuration</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-components.html" title="3.1. Yocto Project Components">
9<link rel="prev" href="usingpoky-components-classes.html" title="3.1.3. Classes">
10<link rel="next" href="shared-state-cache.html" title="3.2. Shared State Cache">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.4. Configuration">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-components-configuration"></a>3.1.4. Configuration</h3></div></div></div>
15<p>
16 The configuration files (<code class="filename">.conf</code>) define various configuration variables
17 that govern the OpenEmbedded build process.
18 These files fall into several areas that define machine configuration options,
19 distribution configuration options, compiler tuning options, general common configuration
20 options and user configuration options (<code class="filename">local.conf</code>, which is found
21 in the <a class="ulink" href="build-directory" target="_self">Build Directory</a>).
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-metadata.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-metadata.html
deleted file mode 100644
index 4f73445d8f..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-metadata.html
+++ /dev/null
@@ -1,29 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.1.2. Metadata (Recipes)</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-components.html" title="3.1. Yocto Project Components">
9<link rel="prev" href="usingpoky-components-bitbake.html" title="3.1.1. BitBake">
10<link rel="next" href="usingpoky-components-classes.html" title="3.1.3. Classes">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.2. Metadata (Recipes)">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-components-metadata"></a>3.1.2. Metadata (Recipes)</h3></div></div></div>
15<p>
16 The <code class="filename">.bb</code> files are usually referred to as "recipes."
17 In general, a recipe contains information about a single piece of software.
18 The information includes the location from which to download the source patches
19 (if any are needed), which special configuration options to apply,
20 how to compile the source files, and how to package the compiled output.
21 </p>
22<p>
23 The term "package" can also be used to describe recipes.
24 However, since the same word is used for the packaged output from the OpenEmbedded
25 build system (i.e. <code class="filename">.ipk</code> or <code class="filename">.deb</code> files),
26 this document avoids using the term "package" when referring to recipes.
27 </p>
28</div></body>
29</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components.html
deleted file mode 100644
index ccd3ae5fbd..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components.html
+++ /dev/null
@@ -1,52 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.1. Yocto Project Components</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="technical-details.html" title="Chapter 3. Technical Details">
9<link rel="prev" href="technical-details.html" title="Chapter 3. Technical Details">
10<link rel="next" href="usingpoky-components-bitbake.html" title="3.1.1. BitBake">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1. Yocto Project Components">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="usingpoky-components"></a>3.1. Yocto Project Components</h2></div></div></div>
15<p>
16 The BitBake task executor together with various types of configuration files form the
17 OpenEmbedded Core.
18 This section overviews the BitBake task executor and the
19 configuration files by describing what they are used for and how they interact.
20 </p>
21<p>
22 BitBake handles the parsing and execution of the data files.
23 The data itself is of various types:
24 </p>
25<div class="itemizedlist"><ul class="itemizedlist" type="disc">
26<li class="listitem"><p><span class="emphasis"><em>Recipes:</em></span> Provides details about particular
27 pieces of software</p></li>
28<li class="listitem"><p><span class="emphasis"><em>Class Data:</em></span> An abstraction of common build
29 information (e.g. how to build a Linux kernel).</p></li>
30<li class="listitem"><p><span class="emphasis"><em>Configuration Data:</em></span> Defines machine-specific settings,
31 policy decisions, etc.
32 Configuration data acts as the glue to bind everything together.</p></li>
33</ul></div>
34<p>
35 For more information on data, see the
36 "<a class="link" href="../dev-manual/yocto-project-terms.html" target="_self">Yocto Project Terms</a>"
37 section in the Yocto Project Development Manual.
38 </p>
39<p>
40 BitBake knows how to combine multiple data sources together and refers to each data source
41 as a layer.
42 For information on layers, see the
43 "<a class="link" href="../dev-manual/understanding-and-creating-layers.html" target="_self">Understanding and
44 Creating Layers</a>" section of the Yocto Project Development Manual.
45 </p>
46<p>
47 Following are some brief details on these core components.
48 For more detailed information on these components see the
49 "<a class="link" href="ref-structure.html" title="Chapter 5. Source Directory Structure">Directory Structure</a>" chapter.
50 </p>
51</div></body>
52</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-configuring-LIC_FILES_CHKSUM.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-configuring-LIC_FILES_CHKSUM.html
deleted file mode 100644
index ffcfd24e15..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-configuring-LIC_FILES_CHKSUM.html
+++ /dev/null
@@ -1,23 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4.1. Tracking License Changes</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="licenses.html" title="3.4. Licenses">
9<link rel="prev" href="licenses.html" title="3.4. Licenses">
10<link rel="next" href="usingpoky-specifying-LIC_FILES_CHKSUM.html" title="3.4.1.1. Specifying the LIC_FILES_CHKSUM Variable">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.1. Tracking License Changes">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-configuring-LIC_FILES_CHKSUM"></a>3.4.1. Tracking License Changes</h3></div></div></div>
15<p>
16 The license of an upstream project might change in the future.
17 In order to prevent these changes going unnoticed, the
18 <code class="filename"><a class="link" href="ref-variables-glos.html#var-LIC_FILES_CHKSUM" title="LIC_FILES_CHKSUM">LIC_FILES_CHKSUM</a></code>
19 variable tracks changes to the license text. The checksums are validated at the end of the
20 configure step, and if the checksums do not match, the build will fail.
21 </p>
22</div></body>
23</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-bitbake.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-bitbake.html
deleted file mode 100644
index 06a3b7f9fa..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-bitbake.html
+++ /dev/null
@@ -1,30 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.4. General BitBake Problems</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging-dependencies.html" title="2.3.3. Dependency Graphs">
10<link rel="next" href="usingpoky-debugging-buildfile.html" title="2.3.5. Building with No Dependencies">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.4. General BitBake Problems">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-bitbake"></a>2.3.4. General BitBake Problems</h3></div></div></div>
15<p>
16 You can see debug output from BitBake by using the <code class="filename">-D</code> option.
17 The debug output gives more information about what BitBake
18 is doing and the reason behind it.
19 Each <code class="filename">-D</code> option you use increases the logging level.
20 The most common usage is <code class="filename">-DDD</code>.
21 </p>
22<p>
23 The output from <code class="filename">bitbake -DDD -v targetname</code> can reveal why
24 BitBake chose a certain version of a package or why BitBake
25 picked a certain provider.
26 This command could also help you in a situation where you think BitBake did something
27 unexpected.
28 </p>
29</div></body>
30</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-buildfile.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-buildfile.html
deleted file mode 100644
index 9450f1aaff..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-buildfile.html
+++ /dev/null
@@ -1,24 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.5. Building with No Dependencies</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging-bitbake.html" title="2.3.4. General BitBake Problems">
10<link rel="next" href="usingpoky-debugging-variables.html" title="2.3.6. Variables">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.5. Building with No Dependencies">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-buildfile"></a>2.3.5. Building with No Dependencies</h3></div></div></div>
15<p>
16 If you really want to build a specific <code class="filename">.bb</code> file, you can use
17 the command form <code class="filename">bitbake -b &lt;somepath/somefile.bb&gt;</code>.
18 This command form does not check for dependencies so you should use it
19 only when you know its dependencies already exist.
20 You can also specify fragments of the filename.
21 In this case, BitBake checks for a unique match.
22 </p>
23</div></body>
24</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-dependencies.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-dependencies.html
deleted file mode 100644
index c48b00e97a..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-dependencies.html
+++ /dev/null
@@ -1,26 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.3. Dependency Graphs</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging-taskrunning.html" title="2.3.2. Running Specific Tasks">
10<link rel="next" href="usingpoky-debugging-bitbake.html" title="2.3.4. General BitBake Problems">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.3. Dependency Graphs">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-dependencies"></a>2.3.3. Dependency Graphs</h3></div></div></div>
15<p>
16 Sometimes it can be hard to see why BitBake wants to build some other packages before a given
17 package you have specified.
18 The <code class="filename">bitbake -g targetname</code> command creates the
19 <code class="filename">depends.dot</code>, <code class="filename">package-depends.dot</code>,
20 and <code class="filename">task-depends.dot</code> files in the current directory.
21 These files show the package and task dependencies and are useful for debugging problems.
22 You can use the <code class="filename">bitbake -g -u depexp targetname</code> command to
23 display the results in a more human-readable form.
24 </p>
25</div></body>
26</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-others.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-others.html
deleted file mode 100644
index a83f4cc4e4..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-others.html
+++ /dev/null
@@ -1,34 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.8. Other Tips</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="logging-with-bash.html" title="2.3.7.2. Logging With Bash">
10<link rel="next" href="maintaining-build-output-quality.html" title="2.4. Maintaining Build Output Quality">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.8. Other Tips">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-others"></a>2.3.8. Other Tips</h3></div></div></div>
15<p>
16 Here are some other tips that you might find useful:
17 </p>
18<div class="itemizedlist"><ul class="itemizedlist" type="disc">
19<li class="listitem"><p>When adding new packages, it is worth watching for
20 undesirable items making their way into compiler command lines.
21 For example, you do not want references to local system files like
22 <code class="filename">/usr/lib/</code> or <code class="filename">/usr/include/</code>.
23 </p></li>
24<li class="listitem"><p>If you want to remove the psplash boot splashscreen,
25 add <code class="filename">psplash=false</code> to the kernel command line.
26 Doing so prevents psplash from loading and thus allows you to see the console.
27 It is also possible to switch out of the splashscreen by
28 switching the virtual console (e.g. Fn+Left or Fn+Right on a Zaurus).
29 </p></li>
30</ul></div>
31<p>
32 </p>
33</div></body>
34</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskfailures.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskfailures.html
deleted file mode 100644
index 709af32619..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskfailures.html
+++ /dev/null
@@ -1,27 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.1. Task Failures</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
10<link rel="next" href="usingpoky-debugging-taskrunning.html" title="2.3.2. Running Specific Tasks">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.1. Task Failures">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-taskfailures"></a>2.3.1. Task Failures</h3></div></div></div>
15<p>The log file for shell tasks is available in
16 <code class="filename">${WORKDIR}/temp/log.do_taskname.pid</code>.
17 For example, the <code class="filename">compile</code> task for the QEMU minimal image for the x86
18 machine (<code class="filename">qemux86</code>) might be
19 <code class="filename">tmp/work/qemux86-poky-linux/core-image-minimal-1.0-r0/temp/log.do_compile.20830</code>.
20 To see what BitBake runs to generate that log, look at the corresponding
21 <code class="filename">run.do_taskname.pid</code> file located in the same directory.
22 </p>
23<p>
24 Presently, the output from Python tasks is sent directly to the console.
25 </p>
26</div></body>
27</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html
deleted file mode 100644
index 998d9d03c7..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-taskrunning.html
+++ /dev/null
@@ -1,68 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.2. Running Specific Tasks</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging-taskfailures.html" title="2.3.1. Task Failures">
10<link rel="next" href="usingpoky-debugging-dependencies.html" title="2.3.3. Dependency Graphs">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.2. Running Specific Tasks">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-taskrunning"></a>2.3.2. Running Specific Tasks</h3></div></div></div>
15<p>
16 Any given package consists of a set of tasks.
17 The standard BitBake behavior in most cases is: <code class="filename">fetch</code>,
18 <code class="filename">unpack</code>,
19 <code class="filename">patch</code>, <code class="filename">configure</code>,
20 <code class="filename">compile</code>, <code class="filename">install</code>, <code class="filename">package</code>,
21 <code class="filename">package_write</code>, and <code class="filename">build</code>.
22 The default task is <code class="filename">build</code> and any tasks on which it depends
23 build first.
24 Some tasks exist, such as <code class="filename">devshell</code>, that are not part of the
25 default build chain.
26 If you wish to run a task that is not part of the default build chain, you can use the
27 <code class="filename">-c</code> option in BitBake as follows:
28 </p>
29<pre class="literallayout">
30 $ bitbake matchbox-desktop -c devshell
31 </pre>
32<p>
33 </p>
34<p>
35 If you wish to rerun a task, use the <code class="filename">-f</code> force option.
36 For example, the following sequence forces recompilation after changing files in the
37 working directory.
38 </p>
39<pre class="literallayout">
40 $ bitbake matchbox-desktop
41 .
42 .
43 [make some changes to the source code in the working directory]
44 .
45 .
46 $ bitbake matchbox-desktop -c compile -f
47 $ bitbake matchbox-desktop
48 </pre>
49<p>
50 </p>
51<p>
52 This sequence first builds <code class="filename">matchbox-desktop</code> and then recompiles it.
53 The last command reruns all tasks (basically the packaging tasks) after the compile.
54 BitBake recognizes that the <code class="filename">compile</code> task was rerun and therefore
55 understands that the other tasks also need to be run again.
56 </p>
57<p>
58 You can view a list of tasks in a given package by running the
59 <code class="filename">listtasks</code> task as follows:
60 </p>
61<pre class="literallayout">
62 $ bitbake matchbox-desktop -c listtasks
63 </pre>
64<p>
65 The results are in the file <code class="filename">${WORKDIR}/temp/log.do_listtasks</code>.
66 </p>
67</div></body>
68</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-variables.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-variables.html
deleted file mode 100644
index ae185be166..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging-variables.html
+++ /dev/null
@@ -1,22 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.6. Variables</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
9<link rel="prev" href="usingpoky-debugging-buildfile.html" title="2.3.5. Building with No Dependencies">
10<link rel="next" href="recipe-logging-mechanisms.html" title="2.3.7. Recipe Logging Mechanisms">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.6. Variables">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="usingpoky-debugging-variables"></a>2.3.6. Variables</h3></div></div></div>
15<p>
16 The <code class="filename">-e</code> option dumps the resulting environment for
17 either the configuration (no package specified) or for a
18 specific package when specified; or <code class="filename">-b recipename</code>
19 to show the environment from parsing a single recipe file only.
20 </p>
21</div></body>
22</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html
deleted file mode 100644
index 9a8b72dc96..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-debugging.html
+++ /dev/null
@@ -1,26 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3. Debugging Build Failures</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
9<link rel="prev" href="usingpoky-install.html" title="2.2. Installing and Using the Result">
10<link rel="next" href="usingpoky-debugging-taskfailures.html" title="2.3.1. Task Failures">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3. Debugging Build Failures">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="usingpoky-debugging"></a>2.3. Debugging Build Failures</h2></div></div></div>
15<p>
16 The exact method for debugging build failures depends on the nature of the
17 problem and on the system's area from which the bug originates.
18 Standard debugging practices such as comparison against the last
19 known working version with examination of the changes and the re-application of steps
20 to identify the one causing the problem are
21 valid for the Yocto Project just as they are for any other system.
22 Even though it is impossible to detail every possible potential failure,
23 this section provides some general tips to aid in debugging.
24 </p>
25</div></body>
26</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-install.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-install.html
deleted file mode 100644
index d8d60e1c6b..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-install.html
+++ /dev/null
@@ -1,28 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.2. Installing and Using the Result</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky.html" title="Chapter 2. Using the Yocto Project">
9<link rel="prev" href="building-an-image-using-gpl-components.html" title="2.1.2. Building an Image Using GPL Components">
10<link rel="next" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.2. Installing and Using the Result">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="usingpoky-install"></a>2.2. Installing and Using the Result</h2></div></div></div>
15<p>
16 Once an image has been built, it often needs to be installed.
17 The images and kernels built by the OpenEmbedded build system are placed in the
18 <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a> in
19 <code class="filename">tmp/deploy/images</code>.
20 For information on how to run pre-built images such as <code class="filename">qemux86</code>
21 and <code class="filename">qemuarm</code>, see the
22 "<a class="link" href="../yocto-project-qs/using-pre-built.html" target="_self">Using Pre-Built Binaries and QEMU</a>"
23 section in the Yocto Project Quick Start.
24 For information about how to install these images, see the documentation for your
25 particular board/machine.
26 </p>
27</div></body>
28</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-specifying-LIC_FILES_CHKSUM.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-specifying-LIC_FILES_CHKSUM.html
deleted file mode 100644
index b518fce8a1..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-specifying-LIC_FILES_CHKSUM.html
+++ /dev/null
@@ -1,57 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.4.1.1. Specifying the LIC_FILES_CHKSUM Variable</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="usingpoky-configuring-LIC_FILES_CHKSUM.html" title="3.4.1. Tracking License Changes">
9<link rel="prev" href="usingpoky-configuring-LIC_FILES_CHKSUM.html" title="3.4.1. Tracking License Changes">
10<link rel="next" href="usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html" title="3.4.1.2. Explanation of Syntax">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.1.1. Specifying the LIC_FILES_CHKSUM Variable">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="usingpoky-specifying-LIC_FILES_CHKSUM"></a>3.4.1.1. Specifying the <code class="filename">LIC_FILES_CHKSUM</code> Variable</h4></div></div></div>
15<p>
16 The <code class="filename">LIC_FILES_CHKSUM</code>
17 variable contains checksums of the license text in the source code for the recipe.
18 Following is an example of how to specify <code class="filename">LIC_FILES_CHKSUM</code>:
19 </p>
20<pre class="literallayout">
21 LIC_FILES_CHKSUM = "file://COPYING;md5=xxxx \
22 file://licfile1.txt;beginline=5;endline=29;md5=yyyy \
23 file://licfile2.txt;endline=50;md5=zzzz \
24 ..."
25 </pre>
26<p>
27 </p>
28<p>
29 The build system uses the
30 <code class="filename"><a class="link" href="ref-variables-glos.html#var-S" title="S">S</a></code> variable as the
31 default directory used when searching files listed in
32 <code class="filename">LIC_FILES_CHKSUM</code>.
33 The previous example employs the default directory.
34 </p>
35<p>
36 You can also use relative paths as shown in the following example:
37 </p>
38<pre class="literallayout">
39 LIC_FILES_CHKSUM = "file://src/ls.c;startline=5;endline=16;\
40 md5=bb14ed3c4cda583abc85401304b5cd4e"
41 LIC_FILES_CHKSUM = "file://../license.html;md5=5c94767cedb5d6987c902ac850ded2c6"
42 </pre>
43<p>
44 </p>
45<p>
46 In this example, the first line locates a file in
47 <code class="filename">${S}/src/ls.c</code>.
48 The second line refers to a file in
49 <code class="filename"><a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">WORKDIR</a></code>, which is the parent
50 of <code class="filename"><a class="link" href="ref-variables-glos.html#var-S" title="S">S</a></code>.
51 </p>
52<p>
53 Note that this variable is mandatory for all recipes, unless the
54 <code class="filename">LICENSE</code> variable is set to "CLOSED".
55 </p>
56</div></body>
57</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky.html
deleted file mode 100644
index 95be1f1041..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky.html
+++ /dev/null
@@ -1,48 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>Chapter 2. Using the Yocto Project</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="index.html" title="The Yocto Project Reference Manual">
9<link rel="prev" href="intro-getit-dev.html" title="1.5. Development Checkouts">
10<link rel="next" href="usingpoky-build.html" title="2.1. Running a Build">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 2. Using the Yocto Project">
13<div class="titlepage"><div><div><h2 class="title">
14<a name="usingpoky"></a>Chapter 2. Using the Yocto Project</h2></div></div></div>
15<div class="toc">
16<p><b>Table of Contents</b></p>
17<dl>
18<dt><span class="section"><a href="usingpoky-build.html">2.1. Running a Build</a></span></dt>
19<dd><dl>
20<dt><span class="section"><a href="build-overview.html">2.1.1. Build Overview</a></span></dt>
21<dt><span class="section"><a href="building-an-image-using-gpl-components.html">2.1.2. Building an Image Using GPL Components</a></span></dt>
22</dl></dd>
23<dt><span class="section"><a href="usingpoky-install.html">2.2. Installing and Using the Result</a></span></dt>
24<dt><span class="section"><a href="usingpoky-debugging.html">2.3. Debugging Build Failures</a></span></dt>
25<dd><dl>
26<dt><span class="section"><a href="usingpoky-debugging-taskfailures.html">2.3.1. Task Failures</a></span></dt>
27<dt><span class="section"><a href="usingpoky-debugging-taskrunning.html">2.3.2. Running Specific Tasks</a></span></dt>
28<dt><span class="section"><a href="usingpoky-debugging-dependencies.html">2.3.3. Dependency Graphs</a></span></dt>
29<dt><span class="section"><a href="usingpoky-debugging-bitbake.html">2.3.4. General BitBake Problems</a></span></dt>
30<dt><span class="section"><a href="usingpoky-debugging-buildfile.html">2.3.5. Building with No Dependencies</a></span></dt>
31<dt><span class="section"><a href="usingpoky-debugging-variables.html">2.3.6. Variables</a></span></dt>
32<dt><span class="section"><a href="recipe-logging-mechanisms.html">2.3.7. Recipe Logging Mechanisms</a></span></dt>
33<dt><span class="section"><a href="usingpoky-debugging-others.html">2.3.8. Other Tips</a></span></dt>
34</dl></dd>
35<dt><span class="section"><a href="maintaining-build-output-quality.html">2.4. Maintaining Build Output Quality</a></span></dt>
36<dd><dl>
37<dt><span class="section"><a href="enabling-and-disabling-build-history.html">2.4.1. Enabling and Disabling Build History</a></span></dt>
38<dt><span class="section"><a href="understanding-what-the-build-history-contains.html">2.4.2. Understanding What the Build History Contains</a></span></dt>
39</dl></dd>
40</dl>
41</div>
42<p>
43 This chapter describes common usage for the Yocto Project.
44 The information is introductory in nature as other manuals in the Yocto Project
45 documentation set provide more details on how to use the Yocto Project.
46 </p>
47</div></body>
48</html>
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/x32.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/x32.html
deleted file mode 100644
index 5be350886c..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/x32.html
+++ /dev/null
@@ -1,35 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.3. x32</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="technical-details.html" title="Chapter 3. Technical Details">
9<link rel="prev" href="invalidating-shared-state.html" title="3.2.4.2. Invalidating Shared State">
10<link rel="next" href="support.html" title="3.3.1. Support">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.3. x32">
13<div class="titlepage"><div><div><h2 class="title" style="clear: both">
14<a name="x32"></a>3.3. x32</h2></div></div></div>
15<p>
16 x32 is a new processor-specific Application Binary Interface (psABI) for x86_64.
17 An ABI defines the calling conventions between functions in a processing environment.
18 The interface determines what registers are used and what the sizes are for various C data types.
19 </p>
20<p>
21 Some processing environments prefer using 32-bit applications even when running
22 on Intel 64-bit platforms.
23 Consider the i386 psABI, which is a very old 32-bit ABI for Intel 64-bit platforms.
24 The i386 psABI does not provide efficient use and access of the Intel 64-bit processor resources,
25 leaving the system underutilized.
26 Now consider the x86_64 psABI.
27 This ABI is newer and uses 64-bits for data sizes and program pointers.
28 The extra bits increase the footprint size of the programs, libraries,
29 and also increases the memory and file system size requirements.
30 Executing under the x32 psABI enables user programs to utilize CPU and system resources
31 more efficiently while keeping the memory footprint of the applications low.
32 Extra bits are used for registers but not for addressing mechanisms.
33 </p>
34</div></body>
35</html>
diff --git a/documentation/ref-manual/eclipse/poky-ref-manual-toc.xml b/documentation/ref-manual/eclipse/poky-ref-manual-toc.xml
deleted file mode 100644
index 8624641cf5..0000000000
--- a/documentation/ref-manual/eclipse/poky-ref-manual-toc.xml
+++ /dev/null
@@ -1,217 +0,0 @@
1<?xml version="1.0" encoding="utf-8" standalone="no"?>
2<toc label="The Yocto Project Reference Manual" topic="html/poky-ref-manual/index.html">
3 <topic label="Introduction" href="html/poky-ref-manual/intro.html">
4 <topic label="Introduction" href="html/poky-ref-manual/intro-welcome.html"/>
5 <topic label="Documentation Overview" href="html/poky-ref-manual/intro-manualoverview.html"/>
6 <topic label="System Requirements" href="html/poky-ref-manual/intro-requirements.html">
7 <topic label="Supported Linux Distributions" href="html/poky-ref-manual/detailed-supported-distros.html"/>
8 <topic label="Required Packages for the Host Development System" href="html/poky-ref-manual/required-packages-for-the-host-development-system.html">
9 <topic label="Ubuntu" href="html/poky-ref-manual/ubuntu-packages.html"/>
10 <topic label="Fedora Packages" href="html/poky-ref-manual/fedora-packages.html"/>
11 <topic label="OpenSUSE Packages" href="html/poky-ref-manual/opensuse-packages.html"/>
12 <topic label="CentOS Packages" href="html/poky-ref-manual/centos-packages.html"/>
13 </topic>
14 </topic>
15 <topic label="Obtaining the Yocto Project" href="html/poky-ref-manual/intro-getit.html"/>
16 <topic label="Development Checkouts" href="html/poky-ref-manual/intro-getit-dev.html"/>
17 </topic>
18 <topic label="Using the Yocto Project" href="html/poky-ref-manual/usingpoky.html">
19 <topic label="Running a Build" href="html/poky-ref-manual/usingpoky-build.html">
20 <topic label="Build Overview" href="html/poky-ref-manual/build-overview.html"/>
21 <topic label="Building an Image Using GPL Components" href="html/poky-ref-manual/building-an-image-using-gpl-components.html"/>
22 </topic>
23 <topic label="Installing and Using the Result" href="html/poky-ref-manual/usingpoky-install.html"/>
24 <topic label="Debugging Build Failures" href="html/poky-ref-manual/usingpoky-debugging.html">
25 <topic label="Task Failures" href="html/poky-ref-manual/usingpoky-debugging-taskfailures.html"/>
26 <topic label="Running Specific Tasks" href="html/poky-ref-manual/usingpoky-debugging-taskrunning.html"/>
27 <topic label="Dependency Graphs" href="html/poky-ref-manual/usingpoky-debugging-dependencies.html"/>
28 <topic label="General BitBake Problems" href="html/poky-ref-manual/usingpoky-debugging-bitbake.html"/>
29 <topic label="Building with No Dependencies" href="html/poky-ref-manual/usingpoky-debugging-buildfile.html"/>
30 <topic label="Variables" href="html/poky-ref-manual/usingpoky-debugging-variables.html"/>
31 <topic label="Recipe Logging Mechanisms" href="html/poky-ref-manual/recipe-logging-mechanisms.html">
32 <topic label="Logging With Python" href="html/poky-ref-manual/logging-with-python.html"/>
33 <topic label="Logging With Bash" href="html/poky-ref-manual/logging-with-bash.html"/>
34 </topic>
35 <topic label="Other Tips" href="html/poky-ref-manual/usingpoky-debugging-others.html"/>
36 </topic>
37 <topic label="Maintaining Build Output Quality" href="html/poky-ref-manual/maintaining-build-output-quality.html">
38 <topic label="Enabling and Disabling Build History" href="html/poky-ref-manual/enabling-and-disabling-build-history.html"/>
39 <topic label="Understanding What the Build History Contains" href="html/poky-ref-manual/understanding-what-the-build-history-contains.html">
40 <topic label="Build History Package Information" href="html/poky-ref-manual/build-history-package-information.html"/>
41 <topic label="Build History Image Information" href="html/poky-ref-manual/build-history-image-information.html"/>
42 <topic label="Using Build History to Gather Image Information Only" href="html/poky-ref-manual/using-build-history-to-gather-image-information-only.html"/>
43 <topic label="Examining Build History Information" href="html/poky-ref-manual/examining-build-history-information.html"/>
44 </topic>
45 </topic>
46 </topic>
47 <topic label="Technical Details" href="html/poky-ref-manual/technical-details.html">
48 <topic label="Yocto Project Components" href="html/poky-ref-manual/usingpoky-components.html">
49 <topic label="BitBake" href="html/poky-ref-manual/usingpoky-components-bitbake.html"/>
50 <topic label="Metadata (Recipes)" href="html/poky-ref-manual/usingpoky-components-metadata.html"/>
51 <topic label="Classes" href="html/poky-ref-manual/usingpoky-components-classes.html"/>
52 <topic label="Configuration" href="html/poky-ref-manual/usingpoky-components-configuration.html"/>
53 </topic>
54 <topic label="Shared State Cache" href="html/poky-ref-manual/shared-state-cache.html">
55 <topic label="Overall Architecture" href="html/poky-ref-manual/overall-architecture.html"/>
56 <topic label="Checksums (Signatures)" href="html/poky-ref-manual/checksums.html"/>
57 <topic label="Shared State" href="html/poky-ref-manual/shared-state.html"/>
58 <topic label="Tips and Tricks" href="html/poky-ref-manual/tips-and-tricks.html">
59 <topic label="Debugging" href="html/poky-ref-manual/debugging.html"/>
60 <topic label="Invalidating Shared State" href="html/poky-ref-manual/invalidating-shared-state.html"/>
61 </topic>
62 </topic>
63 <topic label="x32" href="html/poky-ref-manual/x32.html">
64 <topic label="Support" href="html/poky-ref-manual/support.html"/>
65 <topic label="Future Development and Limitations" href="html/poky-ref-manual/future-development-and-limitations.html"/>
66 <topic label="Using x32 Right Now" href="html/poky-ref-manual/using-x32-right-now.html"/>
67 </topic>
68 <topic label="Licenses" href="html/poky-ref-manual/licenses.html">
69 <topic label="Tracking License Changes" href="html/poky-ref-manual/usingpoky-configuring-LIC_FILES_CHKSUM.html">
70 <topic label="Specifying the LIC_FILES_CHKSUM Variable" href="html/poky-ref-manual/usingpoky-specifying-LIC_FILES_CHKSUM.html"/>
71 <topic label="Explanation of Syntax" href="html/poky-ref-manual/usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax.html"/>
72 </topic>
73 <topic label="Enabling Commercially Licensed Recipes" href="html/poky-ref-manual/enabling-commercially-licensed-recipes.html">
74 <topic label="License Flag Matching" href="html/poky-ref-manual/license-flag-matching.html"/>
75 <topic label="Other Variables Related to Commercial Licenses" href="html/poky-ref-manual/other-variables-related-to-commercial-licenses.html"/>
76 </topic>
77 </topic>
78 </topic>
79 <topic label="Migrating to a Newer Yocto Project Release" href="html/poky-ref-manual/migration.html">
80 <topic label="Moving to the Yocto Project 1.3 Release" href="html/poky-ref-manual/moving-to-the-yocto-project-1.3-release.html">
81 <topic label="Local Configuration" href="html/poky-ref-manual/1.3-local-configuration.html">
82 <topic label="SSTATE_MIRRORS" href="html/poky-ref-manual/migration-1.3-sstate-mirrors.html"/>
83 <topic label="bblayers.conf" href="html/poky-ref-manual/migration-1.3-bblayers-conf.html"/>
84 </topic>
85 <topic label="Recipes" href="html/poky-ref-manual/1.3-recipes.html">
86 <topic label="Python Function Whitespace" href="html/poky-ref-manual/migration-1.3-python-function-whitespace.html"/>
87 <topic label="proto= in SRC_URI" href="html/poky-ref-manual/migration-1.3-proto=-in-src-uri.html"/>
88 <topic label="nativesdk" href="html/poky-ref-manual/migration-1.3-nativesdk.html"/>
89 <topic label="Task Recipes" href="html/poky-ref-manual/migration-1.3-task-recipes.html"/>
90 <topic label="IMAGE_FEATURES" href="html/poky-ref-manual/migration-1.3-image-features.html"/>
91 <topic label="Removed Recipes" href="html/poky-ref-manual/migration-1.3-removed-recipes.html"/>
92 </topic>
93 </topic>
94 </topic>
95 <topic label="Source Directory Structure" href="html/poky-ref-manual/ref-structure.html">
96 <topic label="Top level core components" href="html/poky-ref-manual/structure-core.html">
97 <topic label="bitbake/" href="html/poky-ref-manual/structure-core-bitbake.html"/>
98 <topic label="build/" href="html/poky-ref-manual/structure-core-build.html"/>
99 <topic label="documentation" href="html/poky-ref-manual/handbook.html"/>
100 <topic label="meta/" href="html/poky-ref-manual/structure-core-meta.html"/>
101 <topic label="meta-yocto/" href="html/poky-ref-manual/structure-core-meta-yocto.html"/>
102 <topic label="meta-yocto-bsp/" href="html/poky-ref-manual/structure-core-meta-yocto-bsp.html"/>
103 <topic label="meta-hob/" href="html/poky-ref-manual/structure-meta-hob.html"/>
104 <topic label="meta-skeleton/" href="html/poky-ref-manual/structure-meta-skeleton.html"/>
105 <topic label="scripts/" href="html/poky-ref-manual/structure-core-scripts.html"/>
106 <topic label="oe-init-build-env" href="html/poky-ref-manual/structure-core-script.html"/>
107 <topic label="LICENSE, README, and README.hardware" href="html/poky-ref-manual/structure-basic-top-level.html"/>
108 </topic>
109 <topic label="The Build Directory - build/" href="html/poky-ref-manual/structure-build.html">
110 <topic label="build/pseudodone" href="html/poky-ref-manual/structure-build-pseudodone.html"/>
111 <topic label="build/conf/local.conf" href="html/poky-ref-manual/structure-build-conf-local.conf.html"/>
112 <topic label="build/conf/bblayers.conf" href="html/poky-ref-manual/structure-build-conf-bblayers.conf.html"/>
113 <topic label="build/conf/sanity_info" href="html/poky-ref-manual/structure-build-conf-sanity_info.html"/>
114 <topic label="build/downloads/" href="html/poky-ref-manual/structure-build-downloads.html"/>
115 <topic label="build/sstate-cache/" href="html/poky-ref-manual/structure-build-sstate-cache.html"/>
116 <topic label="build/tmp/" href="html/poky-ref-manual/structure-build-tmp.html"/>
117 <topic label="build/tmp/buildstats/" href="html/poky-ref-manual/structure-build-tmp-buildstats.html"/>
118 <topic label="build/tmp/cache/" href="html/poky-ref-manual/structure-build-tmp-cache.html"/>
119 <topic label="build/tmp/deploy/" href="html/poky-ref-manual/structure-build-tmp-deploy.html"/>
120 <topic label="build/tmp/deploy/deb/" href="html/poky-ref-manual/structure-build-tmp-deploy-deb.html"/>
121 <topic label="build/tmp/deploy/rpm/" href="html/poky-ref-manual/structure-build-tmp-deploy-rpm.html"/>
122 <topic label="build/tmp/deploy/licenses/" href="html/poky-ref-manual/structure-build-tmp-deploy-licenses.html"/>
123 <topic label="build/tmp/deploy/images/" href="html/poky-ref-manual/structure-build-tmp-deploy-images.html"/>
124 <topic label="build/tmp/deploy/ipk/" href="html/poky-ref-manual/structure-build-tmp-deploy-ipk.html"/>
125 <topic label="build/tmp/sysroots/" href="html/poky-ref-manual/structure-build-tmp-sysroots.html"/>
126 <topic label="build/tmp/stamps/" href="html/poky-ref-manual/structure-build-tmp-stamps.html"/>
127 <topic label="build/tmp/log/" href="html/poky-ref-manual/structure-build-tmp-log.html"/>
128 <topic label="build/tmp/pkgdata/" href="html/poky-ref-manual/structure-build-tmp-pkgdata.html"/>
129 <topic label="build/tmp/work/" href="html/poky-ref-manual/structure-build-tmp-work.html"/>
130 </topic>
131 <topic label="The Metadata - meta/" href="html/poky-ref-manual/structure-meta.html">
132 <topic label="meta/classes/" href="html/poky-ref-manual/structure-meta-classes.html"/>
133 <topic label="meta/conf/" href="html/poky-ref-manual/structure-meta-conf.html"/>
134 <topic label="meta/conf/machine/" href="html/poky-ref-manual/structure-meta-conf-machine.html"/>
135 <topic label="meta/conf/distro/" href="html/poky-ref-manual/structure-meta-conf-distro.html"/>
136 <topic label="meta/recipes-bsp/" href="html/poky-ref-manual/structure-meta-recipes-bsp.html"/>
137 <topic label="meta/recipes-connectivity/" href="html/poky-ref-manual/structure-meta-recipes-connectivity.html"/>
138 <topic label="meta/recipes-core/" href="html/poky-ref-manual/structure-meta-recipes-core.html"/>
139 <topic label="meta/recipes-devtools/" href="html/poky-ref-manual/structure-meta-recipes-devtools.html"/>
140 <topic label="meta/recipes-extended/" href="html/poky-ref-manual/structure-meta-recipes-extended.html"/>
141 <topic label="meta/recipes-gnome/" href="html/poky-ref-manual/structure-meta-recipes-gnome.html"/>
142 <topic label="meta/recipes-graphics/" href="html/poky-ref-manual/structure-meta-recipes-graphics.html"/>
143 <topic label="meta/recipes-kernel/" href="html/poky-ref-manual/structure-meta-recipes-kernel.html"/>
144 <topic label="meta/recipes-multimedia/" href="html/poky-ref-manual/structure-meta-recipes-multimedia.html"/>
145 <topic label="meta/recipes-qt/" href="html/poky-ref-manual/structure-meta-recipes-qt.html"/>
146 <topic label="meta/recipes-rt/" href="html/poky-ref-manual/structure-meta-recipes-rt.html"/>
147 <topic label="meta/recipes-sato/" href="html/poky-ref-manual/structure-meta-recipes-sato.html"/>
148 <topic label="meta/recipes-support/" href="html/poky-ref-manual/structure-meta-recipes-support.html"/>
149 <topic label="meta/site/" href="html/poky-ref-manual/structure-meta-site.html"/>
150 <topic label="meta/recipes.txt" href="html/poky-ref-manual/structure-meta-recipes-txt.html"/>
151 </topic>
152 </topic>
153 <topic label="BitBake" href="html/poky-ref-manual/ref-bitbake.html">
154 <topic label="Parsing" href="html/poky-ref-manual/ref-bitbake-parsing.html"/>
155 <topic label="Preferences and Providers" href="html/poky-ref-manual/ref-bitbake-providers.html"/>
156 <topic label="Dependencies" href="html/poky-ref-manual/ref-bitbake-dependencies.html"/>
157 <topic label="The Task List" href="html/poky-ref-manual/ref-bitbake-tasklist.html"/>
158 <topic label="Running a Task" href="html/poky-ref-manual/ref-bitbake-runtask.html"/>
159 <topic label="BitBake Command Line" href="html/poky-ref-manual/ref-bitbake-commandline.html"/>
160 <topic label="Fetchers" href="html/poky-ref-manual/ref-bitbake-fetchers.html"/>
161 </topic>
162 <topic label="Classes" href="html/poky-ref-manual/ref-classes.html">
163 <topic label="The base class - base.bbclass" href="html/poky-ref-manual/ref-classes-base.html"/>
164 <topic label="Autotooled Packages - autotools.bbclass" href="html/poky-ref-manual/ref-classes-autotools.html"/>
165 <topic label="Alternatives - update-alternatives.bbclass" href="html/poky-ref-manual/ref-classes-update-alternatives.html"/>
166 <topic label="Initscripts - update-rc.d.bbclass" href="html/poky-ref-manual/ref-classes-update-rc.d.html"/>
167 <topic label="Binary config scripts - binconfig.bbclass" href="html/poky-ref-manual/ref-classes-binconfig.html"/>
168 <topic label="Debian renaming - debian.bbclass" href="html/poky-ref-manual/ref-classes-debian.html"/>
169 <topic label="Pkg-config - pkgconfig.bbclass" href="html/poky-ref-manual/ref-classes-pkgconfig.html"/>
170 <topic label="Distribution of sources - src_distribute_local.bbclass" href="html/poky-ref-manual/ref-classes-src-distribute.html"/>
171 <topic label="Perl modules - cpan.bbclass" href="html/poky-ref-manual/ref-classes-perl.html"/>
172 <topic label="Python extensions - distutils.bbclass" href="html/poky-ref-manual/ref-classes-distutils.html"/>
173 <topic label="Developer Shell - devshell.bbclass" href="html/poky-ref-manual/ref-classes-devshell.html"/>
174 <topic label="Package Groups - packagegroup.bbclass" href="html/poky-ref-manual/ref-classes-packagegroup.html"/>
175 <topic label="Packaging - package*.bbclass" href="html/poky-ref-manual/ref-classes-package.html"/>
176 <topic label="Building kernels - kernel.bbclass" href="html/poky-ref-manual/ref-classes-kernel.html"/>
177 <topic label="Creating images - image.bbclass and rootfs*.bbclass" href="html/poky-ref-manual/ref-classes-image.html"/>
178 <topic label="Host System sanity checks - sanity.bbclass" href="html/poky-ref-manual/ref-classes-sanity.html"/>
179 <topic label="Generated output quality assurance checks - insane.bbclass" href="html/poky-ref-manual/ref-classes-insane.html"/>
180 <topic label="Autotools configuration data cache - siteinfo.bbclass" href="html/poky-ref-manual/ref-classes-siteinfo.html"/>
181 <topic label="Adding Users - useradd.bbclass" href="html/poky-ref-manual/ref-classes-useradd.html"/>
182 <topic label="Using External Source - externalsrc.bbclass" href="html/poky-ref-manual/ref-classes-externalsrc.html"/>
183 <topic label="Other Classes" href="html/poky-ref-manual/ref-classes-others.html"/>
184 </topic>
185 <topic label="Images" href="html/poky-ref-manual/ref-images.html"/>
186 <topic label="Reference: Features" href="html/poky-ref-manual/ref-features.html">
187 <topic label="Distro" href="html/poky-ref-manual/ref-features-distro.html"/>
188 <topic label="Machine" href="html/poky-ref-manual/ref-features-machine.html"/>
189 <topic label="Images" href="html/poky-ref-manual/ref-features-image.html"/>
190 <topic label="Feature Backfilling" href="html/poky-ref-manual/ref-features-backfill.html"/>
191 </topic>
192 <topic label="Variables Glossary" href="html/poky-ref-manual/ref-variables-glos.html">
193 <topic label="Glossary" href="html/poky-ref-manual/ref-variables-glos.html#ref-variables-glossary"/>
194 </topic>
195 <topic label="Variable Context" href="html/poky-ref-manual/ref-varlocality.html">
196 <topic label="Configuration" href="html/poky-ref-manual/ref-varlocality-configuration.html">
197 <topic label="Distribution (Distro)" href="html/poky-ref-manual/ref-varlocality-config-distro.html"/>
198 <topic label="Machine" href="html/poky-ref-manual/ref-varlocality-config-machine.html"/>
199 <topic label="Local" href="html/poky-ref-manual/ref-varlocality-config-local.html"/>
200 </topic>
201 <topic label="Recipes" href="html/poky-ref-manual/ref-varlocality-recipes.html">
202 <topic label="Required" href="html/poky-ref-manual/ref-varlocality-recipe-required.html"/>
203 <topic label="Dependencies" href="html/poky-ref-manual/ref-varlocality-recipe-dependencies.html"/>
204 <topic label="Paths" href="html/poky-ref-manual/ref-varlocality-recipe-paths.html"/>
205 <topic label="Extra Build Information" href="html/poky-ref-manual/ref-varlocality-recipe-build.html"/>
206 </topic>
207 </topic>
208 <topic label="FAQ" href="html/poky-ref-manual/faq.html"/>
209 <topic label="Contributing to the Yocto Project" href="html/poky-ref-manual/resources.html">
210 <topic label="Introduction" href="html/poky-ref-manual/resources-intro.html"/>
211 <topic label="Tracking Bugs" href="html/poky-ref-manual/resources-bugtracker.html"/>
212 <topic label="Mailing lists" href="html/poky-ref-manual/resources-mailinglist.html"/>
213 <topic label="Internet Relay Chat (IRC)" href="html/poky-ref-manual/resources-irc.html"/>
214 <topic label="Links" href="html/poky-ref-manual/resources-links.html"/>
215 <topic label="Contributions" href="html/poky-ref-manual/resources-contributions.html"/>
216 </topic>
217</toc>
diff --git a/documentation/ref-manual/ref-manual.xml b/documentation/ref-manual/ref-manual.xml
index ba7019e257..d93710bc39 100644
--- a/documentation/ref-manual/ref-manual.xml
+++ b/documentation/ref-manual/ref-manual.xml
@@ -17,7 +17,7 @@
17 </mediaobject> 17 </mediaobject>
18 18
19 <title> 19 <title>
20 The Yocto Project Reference Manual 20 Yocto Project Reference Manual
21 </title> 21 </title>
22 22
23 <authorgroup> 23 <authorgroup>