summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTimo Mueller <timo.mueller@bmw-carit.de>2013-02-08 15:16:33 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:25:35 (GMT)
commita41a805500cab281fba15bd8e5d3e60b88d0d4be (patch)
tree9973678912b57cfdef5b1f9676794a556b4d8966
parent768152340898cbb9faed6e8865a4e35c69833230 (diff)
downloadpoky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi, the generation of eclipse help files has been merged from the timo branch to the master. Since the creation of the timo branch there have been some changes to the master branch (e.g. new documentation, renamed documentation). This patch set does some cleanup for the renamed documentation and adds eclipse help generation support to the new documentation. 01: Removes the 'the' from the document titles 02..04: Cleanup obsolete artifacts resulting from the merge 05..08: Add eclipse help generation for ref-manual 09..13: Add eclipse help generation for kernel-dev 14..18: Add eclipse help generation for profile-manual Best regards, Timo This patch set originally contained 18 patches. I (Scott Rifenbark) had to push these changes as two parts. This is the first part. It does not include creation of the three cusomization files. (From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/Makefile21
-rw-r--r--documentation/adt-manual/adt-manual.xml2
-rw-r--r--documentation/bsp-guide/bsp-guide.xml2
-rw-r--r--documentation/dev-manual/dev-manual.xml2
-rw-r--r--documentation/kernel-dev/kernel-dev-customization.xsl9
-rw-r--r--documentation/kernel-dev/kernel-dev.xml4
-rw-r--r--documentation/poky-ref-manual/poky-ref-manual-eclipse-customization.xsl27
-rw-r--r--documentation/profile-manual/profile-manual-customization.xsl9
-rw-r--r--documentation/profile-manual/profile-manual.xml4
-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
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml2
194 files changed, 35 insertions, 11175 deletions
diff --git a/documentation/Makefile b/documentation/Makefile
index 2668f31..5272ee5 100644
--- a/documentation/Makefile
+++ b/documentation/Makefile
@@ -227,13 +227,8 @@ STYLESHEET = $(DOC)/*.css
227endif 227endif
228 228
229ifeq ($(DOC),profile-manual) 229ifeq ($(DOC),profile-manual)
230XSLTOPTS = --stringparam html.stylesheet profile-manual-style.css \ 230XSLTOPTS = --xinclude
231 --stringparam chapter.autolabel 1 \ 231ALLPREQ = html pdf eclipse tarball
232 --stringparam appendix.autolabel A \
233 --stringparam section.autolabel 1 \
234 --stringparam section.label.includes.component.label 1 \
235 --xinclude
236ALLPREQ = html pdf tarball
237TARFILES = profile-manual.html profile-manual.pdf profile-manual-style.css \ 232TARFILES = profile-manual.html profile-manual.pdf profile-manual-style.css \
238 figures/profile-title.png figures/kernelshark-all.png \ 233 figures/profile-title.png figures/kernelshark-all.png \
239 figures/kernelshark-choose-events.png figures/kernelshark-i915-display.png \ 234 figures/kernelshark-choose-events.png figures/kernelshark-i915-display.png \
@@ -323,9 +318,17 @@ eclipse: eclipse-generate eclipse-resolve-links
323.PHONY : eclipse-generate eclipse-resolve-links 318.PHONY : eclipse-generate eclipse-resolve-links
324 319
325eclipse-generate: 320eclipse-generate:
326ifeq ($(DOC),mega-manual) 321ifeq ($(filter $(DOC), adt-manual bsp-guide dev-manual kernel-dev profile-manual ref-manual yocto-project-qs),)
327 @echo " " 322 @echo " "
328 @echo "ERROR: You cannot generate eclipse documentation for the mega-manual" 323 @echo "ERROR: You can only create eclipse documentation"
324 @echo " of the following documentation parts:"
325 @echo " - adt-manual"
326 @echo " - bsp-guide"
327 @echo " - dev-manual"
328 @echo " - kernel-dev"
329 @echo " - profile-manual"
330 @echo " - ref-manual"
331 @echo " - yocto-project-qs"
329 @echo " " 332 @echo " "
330else 333else
331 @echo " " 334 @echo " "
diff --git a/documentation/adt-manual/adt-manual.xml b/documentation/adt-manual/adt-manual.xml
index 479a492..fc1bc80 100644
--- a/documentation/adt-manual/adt-manual.xml
+++ b/documentation/adt-manual/adt-manual.xml
@@ -17,7 +17,7 @@
17 </mediaobject> 17 </mediaobject>
18 18
19 <title> 19 <title>
20 The Yocto Project Application Developer's Guide 20 Yocto Project Application Developer's Guide
21 </title> 21 </title>
22 22
23 <authorgroup> 23 <authorgroup>
diff --git a/documentation/bsp-guide/bsp-guide.xml b/documentation/bsp-guide/bsp-guide.xml
index 1cb2001..57c8458 100644
--- a/documentation/bsp-guide/bsp-guide.xml
+++ b/documentation/bsp-guide/bsp-guide.xml
@@ -17,7 +17,7 @@
17 </mediaobject> 17 </mediaobject>
18 18
19 <title> 19 <title>
20 The Yocto Project Board Support Package Developer's Guide 20 Yocto Project Board Support Package Developer's Guide
21 </title> 21 </title>
22 22
23 <authorgroup> 23 <authorgroup>
diff --git a/documentation/dev-manual/dev-manual.xml b/documentation/dev-manual/dev-manual.xml
index b902aaa..1a1c5e1 100644
--- a/documentation/dev-manual/dev-manual.xml
+++ b/documentation/dev-manual/dev-manual.xml
@@ -17,7 +17,7 @@
17 </mediaobject> 17 </mediaobject>
18 18
19 <title> 19 <title>
20 The Yocto Project Development Manual 20 Yocto Project Development Manual
21 </title> 21 </title>
22 22
23 <authorgroup> 23 <authorgroup>
diff --git a/documentation/kernel-dev/kernel-dev-customization.xsl b/documentation/kernel-dev/kernel-dev-customization.xsl
index 8eb6905..43e9dad 100644
--- a/documentation/kernel-dev/kernel-dev-customization.xsl
+++ b/documentation/kernel-dev/kernel-dev-customization.xsl
@@ -1,8 +1,11 @@
1<?xml version='1.0'?> 1<?xml version='1.0'?>
2<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> 2<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0">
3
4 <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl" />
5 3
6<!-- <xsl:param name="generate.toc" select="'article nop'"></xsl:param> --> 4 <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl" />
7 5
6 <xsl:param name="html.stylesheet" select="'kernel-dev-style.css'" />
7 <xsl:param name="chapter.autolabel" select="1" />
8 <xsl:param name="appendix.autolabel">A</xsl:param>
9 <xsl:param name="section.autolabel" select="1" />
10 <xsl:param name="section.label.includes.component.label" select="1" />
8</xsl:stylesheet> 11</xsl:stylesheet>
diff --git a/documentation/kernel-dev/kernel-dev.xml b/documentation/kernel-dev/kernel-dev.xml
index 9682d54..d040a10 100644
--- a/documentation/kernel-dev/kernel-dev.xml
+++ b/documentation/kernel-dev/kernel-dev.xml
@@ -16,7 +16,9 @@
16 </imageobject> 16 </imageobject>
17 </mediaobject> 17 </mediaobject>
18 18
19 <title></title> 19 <title>
20 Yocto Project Linux Kernel Development Manual
21 </title>
20 22
21 <authorgroup> 23 <authorgroup>
22 <author> 24 <author>
diff --git a/documentation/poky-ref-manual/poky-ref-manual-eclipse-customization.xsl b/documentation/poky-ref-manual/poky-ref-manual-eclipse-customization.xsl
deleted file mode 100644
index 3412208..0000000
--- a/documentation/poky-ref-manual/poky-ref-manual-eclipse-customization.xsl
+++ /dev/null
@@ -1,27 +0,0 @@
1<?xml version='1.0'?>
2<xsl:stylesheet
3 xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
4 xmlns="http://www.w3.org/1999/xhtml"
5 xmlns:fo="http://www.w3.org/1999/XSL/Format"
6 version="1.0">
7
8 <xsl:import
9 href="http://docbook.sourceforge.net/release/xsl/current/eclipse/eclipse3.xsl" />
10
11 <xsl:param name="chunker.output.indent" select="'yes'"/>
12 <xsl:param name="chunk.quietly" select="1"/>
13 <xsl:param name="chunk.first.sections" select="1"/>
14 <xsl:param name="chunk.section.depth" select="10"/>
15 <xsl:param name="use.id.as.filename" select="1"/>
16 <xsl:param name="ulink.target" select="'_self'" />
17 <xsl:param name="base.dir" select="'html/poky-ref-manual/'"/>
18 <xsl:param name="html.stylesheet" select="'../book.css'"/>
19 <xsl:param name="eclipse.manifest" select="0"/>
20 <xsl:param name="create.plugin.xml" select="0"/>
21 <xsl:param name="suppress.navigation" select="1"/>
22 <xsl:param name="generate.index" select="0"/>
23 <xsl:param name="chapter.autolabel" select="1" />
24 <xsl:param name="appendix.autolabel" select="A" />
25 <xsl:param name="section.autolabel" select="1" />
26 <xsl:param name="section.label.includes.component.label" select="1" />
27</xsl:stylesheet>
diff --git a/documentation/profile-manual/profile-manual-customization.xsl b/documentation/profile-manual/profile-manual-customization.xsl
index 8eb6905..ead52ee 100644
--- a/documentation/profile-manual/profile-manual-customization.xsl
+++ b/documentation/profile-manual/profile-manual-customization.xsl
@@ -1,8 +1,11 @@
1<?xml version='1.0'?> 1<?xml version='1.0'?>
2<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> 2<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0">
3
4 <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl" />
5 3
6<!-- <xsl:param name="generate.toc" select="'article nop'"></xsl:param> --> 4 <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl" />
7 5
6 <xsl:param name="html.stylesheet" select="'profile-manual-style.css'" />
7 <xsl:param name="chapter.autolabel" select="1" />
8 <xsl:param name="appendix.autolabel">A</xsl:param>
9 <xsl:param name="section.autolabel" select="1" />
10 <xsl:param name="section.label.includes.component.label" select="1" />
8</xsl:stylesheet> 11</xsl:stylesheet>
diff --git a/documentation/profile-manual/profile-manual.xml b/documentation/profile-manual/profile-manual.xml
index bd392fd..02c55bc 100644
--- a/documentation/profile-manual/profile-manual.xml
+++ b/documentation/profile-manual/profile-manual.xml
@@ -16,7 +16,9 @@
16 </imageobject> 16 </imageobject>
17 </mediaobject> 17 </mediaobject>
18 18
19 <title></title> 19 <title>
20 Yocto Project Profiling and Tracing Manual
21 </title>
20 22
21 <authorgroup> 23 <authorgroup>
22 <author> 24 <author>
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 d4a9f08..0000000
--- 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 6996694..0000000
--- 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 f1b0f9e..0000000
--- 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 370481d..0000000
--- 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 4ee4185..0000000
--- 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 12073d5..0000000
--- 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 05463bc..0000000
--- 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 5dccce9..0000000
--- 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 80a19f9..0000000
--- 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 6222ae5..0000000
--- 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 06be8f5..0000000
--- 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 9ecf3cc..0000000
--- 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 0fa3f74..0000000
--- 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 8b8cafb..0000000
--- 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 d1dc7d1..0000000
--- 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 cd09ff8..0000000
--- 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 9588191..0000000
--- 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 70ef005..0000000
--- 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 9edb4b9..0000000
--- 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 0a25903..0000000
--- 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 56fa85f..0000000
--- 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 7f8e368..0000000
--- 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 3cab8ac..0000000
--- 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 378b87f..0000000
--- 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 1ff7cdc..0000000
--- 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 425f179..0000000
--- 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 8909689..0000000
--- 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 3af03e9..0000000
--- 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 3cea310..0000000
--- 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 e57b647..0000000
--- 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>