summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/adt-manual/adt-prepare.xml22
-rw-r--r--documentation/bsp-guide/bsp.xml6
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml18
-rw-r--r--documentation/dev-manual/dev-manual-model.xml6
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml4
-rw-r--r--documentation/kernel-dev/kernel-dev-maint-appx.xml4
-rw-r--r--documentation/ref-manual/migration.xml6
-rw-r--r--documentation/ref-manual/ref-bitbake.xml2
-rw-r--r--documentation/ref-manual/ref-features.xml2
-rw-r--r--documentation/ref-manual/ref-variables.xml20
-rw-r--r--documentation/ref-manual/technical-details.xml6
-rw-r--r--documentation/ref-manual/usingpoky.xml2
12 files changed, 49 insertions, 49 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 02416b3cda..df9d5b0f76 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -106,7 +106,7 @@
106 build environment while also creating the default 106 build environment while also creating the default
107 Build Directory, and run the BitBake command that 107 Build Directory, and run the BitBake command that
108 results in the tarball 108 results in the tarball
109 <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: 109 <filename>poky/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
110 <note> 110 <note>
111 Before using BitBake to build the ADT tarball, be 111 Before using BitBake to build the ADT tarball, be
112 sure to make sure your 112 sure to make sure your
@@ -136,7 +136,7 @@
136 a top-level directory named <filename>adt-installer</filename>: 136 a top-level directory named <filename>adt-installer</filename>:
137 <literallayout class='monospaced'> 137 <literallayout class='monospaced'>
138 $ cd ~ 138 $ cd ~
139 $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME 139 $ cp poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME
140 $ tar -xjf adt_installer.tar.bz2 140 $ tar -xjf adt_installer.tar.bz2
141 </literallayout> 141 </literallayout>
142 Unpacking it creates the directory <filename>adt-installer</filename>, 142 Unpacking it creates the directory <filename>adt-installer</filename>,
@@ -206,7 +206,7 @@
206 When you run the installer, the environment must use a 206 When you run the installer, the environment must use a
207 host <filename>gcc</filename>: 207 host <filename>gcc</filename>:
208 <literallayout class='monospaced'> 208 <literallayout class='monospaced'>
209 $ cd ~/adt-installer 209 $ cd adt-installer
210 $ ./adt_installer 210 $ ./adt_installer
211 </literallayout> 211 </literallayout>
212 Once the installer begins to run, you are asked to enter the 212 Once the installer begins to run, you are asked to enter the
@@ -303,7 +303,7 @@
303 The first thing the installer prompts you for is the 303 The first thing the installer prompts you for is the
304 directory into which you want to install the toolchain. 304 directory into which you want to install the toolchain.
305 The default directory used is 305 The default directory used is
306 <filename>opt/poky/&DISTRO;</filename>. 306 <filename>/opt/poky/&DISTRO;</filename>.
307 If you do not have write permissions for the directory 307 If you do not have write permissions for the directory
308 into which you are installing the toolchain, the 308 into which you are installing the toolchain, the
309 toolchain installer notifies you and exits. 309 toolchain installer notifies you and exits.
@@ -545,7 +545,7 @@
545 the toolchain environment script in the 545 the toolchain environment script in the
546 <filename>tmp</filename> directory. 546 <filename>tmp</filename> directory.
547 If you installed the toolchain by hand, the environment setup 547 If you installed the toolchain by hand, the environment setup
548 script is located in <filename>opt/poky/&DISTRO;</filename>. 548 script is located in <filename>/opt/poky/&DISTRO;</filename>.
549 </para> 549 </para>
550 550
551 <para> 551 <para>
@@ -563,16 +563,16 @@
563 built filesystem that is located in the 563 built filesystem that is located in the
564 <filename>~/Downloads</filename> directory. 564 <filename>~/Downloads</filename> directory.
565 Furthermore, this command extracts the root filesystem into the 565 Furthermore, this command extracts the root filesystem into the
566 <filename>$HOME/qemux86-sato</filename> directory: 566 <filename>qemux86-sato</filename> directory:
567 <literallayout class='monospaced'> 567 <literallayout class='monospaced'>
568 $ cd ~ 568 $ cd ~
569 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux 569 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
570 $ runqemu-extract-sdk \ 570 $ runqemu-extract-sdk \
571 ~Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \ 571 ~/Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
572 $HOME/qemux86-sato 572 $HOME/qemux86-sato
573 </literallayout> 573 </literallayout>
574 You could now point to the target sysroot at 574 You could now point to the target sysroot at
575 <filename>$HOME/qemux86-sato</filename>. 575 <filename>qemux86-sato</filename>.
576 </para> 576 </para>
577 </section> 577 </section>
578</section> 578</section>
@@ -625,13 +625,13 @@
625 <note> 625 <note>
626 By default, this toolchain does not build static binaries. 626 By default, this toolchain does not build static binaries.
627 If you want to use the toolchain to build these types of libraries, 627 If you want to use the toolchain to build these types of libraries,
628 you need to be sure your image has the appropriate static 628 you need to be sure your image has the appropriate static
629 development libraries. 629 development libraries.
630 Use the 630 Use the
631 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink> 631 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'><filename>IMAGE_INSTALL</filename></ulink>
632 variable inside your <filename>local.conf</filename> file to 632 variable inside your <filename>local.conf</filename> file to
633 install the appropriate library packages. 633 install the appropriate library packages.
634 Following is an example using <filename>eglibc</filename> static 634 Following is an example using <filename>eglibc</filename> static
635 development libraries: 635 development libraries:
636 <literallayout class='monospaced'> 636 <literallayout class='monospaced'>
637 IMAGE_INSTALL_append = " eglibc-staticdev" 637 IMAGE_INSTALL_append = " eglibc-staticdev"
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index c85e7e0883..9a8f3af573 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -562,7 +562,7 @@
562 <para> 562 <para>
563 For example, suppose you had some configuration options in a file called 563 For example, suppose you had some configuration options in a file called
564 <filename>network_configs.cfg</filename>. 564 <filename>network_configs.cfg</filename>.
565 You can place that file inside a directory named <filename>/linux-yocto</filename> and then add 565 You can place that file inside a directory named <filename>linux-yocto</filename> and then add
566 a <filename>SRC_URI</filename> statement such as the following to the append file. 566 a <filename>SRC_URI</filename> statement such as the following to the append file.
567 When the OpenEmbedded build system builds the kernel, the configuration options are 567 When the OpenEmbedded build system builds the kernel, the configuration options are
568 picked up and applied. 568 picked up and applied.
@@ -748,7 +748,7 @@
748 <listitem><para>Instructions on how to boot the BSP build from 748 <listitem><para>Instructions on how to boot the BSP build from
749 the BSP layer.</para></listitem> 749 the BSP layer.</para></listitem>
750 <listitem><para>Instructions on how to boot the binary images 750 <listitem><para>Instructions on how to boot the binary images
751 contained in the <filename>/binary</filename> directory, 751 contained in the <filename>binary</filename> directory,
752 if present.</para></listitem> 752 if present.</para></listitem>
753 <listitem><para>Information on any known bugs or issues that users 753 <listitem><para>Information on any known bugs or issues that users
754 should know about when either building or booting the BSP 754 should know about when either building or booting the BSP
@@ -759,7 +759,7 @@
759 <filename>meta-&lt;bsp_name&gt;</filename> directory. 759 <filename>meta-&lt;bsp_name&gt;</filename> directory.
760 This file specifies exactly where you can find the sources used to 760 This file specifies exactly where you can find the sources used to
761 generate the binary images contained in the 761 generate the binary images contained in the
762 <filename>/binary</filename> directory, if present. 762 <filename>binary</filename> directory, if present.
763 See the 763 See the
764 <ulink url='&YOCTO_GIT_URL;/cgit.cgi/meta-intel/tree/meta-fri2/README.sources'><filename>README.sources</filename></ulink> 764 <ulink url='&YOCTO_GIT_URL;/cgit.cgi/meta-intel/tree/meta-fri2/README.sources'><filename>README.sources</filename></ulink>
765 file for the Fish River Island 2 BSP in the <filename>meta-fri2</filename> BSP layer 765 file for the Fish River Island 2 BSP in the <filename>meta-fri2</filename> BSP layer
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 4aecb449f3..7d5063b79b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -357,7 +357,7 @@
357 to cause the build to use your own version of 357 to cause the build to use your own version of
358 the file. 358 the file.
359 For example, an append file in your layer at 359 For example, an append file in your layer at
360 <filename>/meta-one/recipes-core/base-files/base-files.bbappend</filename> 360 <filename>meta-one/recipes-core/base-files/base-files.bbappend</filename>
361 could extend 361 could extend
362 <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESPATH'><filename>FILESPATH</filename></ulink> 362 <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESPATH'><filename>FILESPATH</filename></ulink>
363 using 363 using
@@ -369,7 +369,7 @@
369 The build for machine "one" will pick up your 369 The build for machine "one" will pick up your
370 machine-specific file as long as you have the 370 machine-specific file as long as you have the
371 file in 371 file in
372 <filename>/meta-one/recipes-core/base-files/base-files/</filename>. 372 <filename>meta-one/recipes-core/base-files/base-files/</filename>.
373 However, if you are building for a different 373 However, if you are building for a different
374 machine and the 374 machine and the
375 <filename>bblayers.conf</filename> file includes 375 <filename>bblayers.conf</filename> file includes
@@ -384,9 +384,9 @@
384 the file in a subdirectory specific to the 384 the file in a subdirectory specific to the
385 machine. 385 machine.
386 For example, rather than placing the file in 386 For example, rather than placing the file in
387 <filename>/meta-one/recipes-core/base-files/base-files/</filename> 387 <filename>meta-one/recipes-core/base-files/base-files/</filename>
388 as shown above, put it in 388 as shown above, put it in
389 <filename>/meta-one/recipes-core/base-files/base-files/one/</filename>. 389 <filename>meta-one/recipes-core/base-files/base-files/one/</filename>.
390 Not only does this make sure the file is used 390 Not only does this make sure the file is used
391 only when building for machine "one" but the 391 only when building for machine "one" but the
392 build process locates the file more quickly.</para> 392 build process locates the file more quickly.</para>
@@ -1957,7 +1957,7 @@
1957 <link linkend='source-directory'>Source Directory</link> 1957 <link linkend='source-directory'>Source Directory</link>
1958 top-level folder is <filename>~/poky</filename>: 1958 top-level folder is <filename>~/poky</filename>:
1959 <literallayout class='monospaced'> 1959 <literallayout class='monospaced'>
1960 $ cd ~/poky 1960 $ cd poky
1961 $ source oe-init-build-env 1961 $ source oe-init-build-env
1962 $ bitbake linux-yocto -c menuconfig 1962 $ bitbake linux-yocto -c menuconfig
1963 </literallayout> 1963 </literallayout>
@@ -2006,7 +2006,7 @@
2006 <filename>x86</filename> architecture, the 2006 <filename>x86</filename> architecture, the
2007 <filename>.config</filename> file would be located here: 2007 <filename>.config</filename> file would be located here:
2008 <literallayout class='monospaced'> 2008 <literallayout class='monospaced'>
2009 ~/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.4.11+git1+84f... 2009 poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.4.11+git1+84f...
2010 ...656ed30-r1/linux-qemux86-standard-build 2010 ...656ed30-r1/linux-qemux86-standard-build
2011 </literallayout> 2011 </literallayout>
2012 <note> 2012 <note>
@@ -2079,7 +2079,7 @@
2079 kernel's configuration. 2079 kernel's configuration.
2080 For example, suppose you had a set of configuration options in a file called 2080 For example, suppose you had a set of configuration options in a file called
2081 <filename>myconfig.cfg</filename>. 2081 <filename>myconfig.cfg</filename>.
2082 If you put that file inside a directory named <filename>/linux-yocto</filename> 2082 If you put that file inside a directory named <filename>linux-yocto</filename>
2083 that resides in the same directory as the kernel's append file and then add 2083 that resides in the same directory as the kernel's append file and then add
2084 a <filename>SRC_URI</filename> statement such as the following to the kernel's append file, 2084 a <filename>SRC_URI</filename> statement such as the following to the kernel's append file,
2085 those configuration options will be picked up and applied when the kernel is built. 2085 those configuration options will be picked up and applied when the kernel is built.
@@ -5271,7 +5271,7 @@
5271 <listitem><para>You have checked out the 5271 <listitem><para>You have checked out the
5272 <filename>dora-toaster</filename> branch: 5272 <filename>dora-toaster</filename> branch:
5273 <literallayout class='monospaced'> 5273 <literallayout class='monospaced'>
5274 $ cd ~/poky 5274 $ cd poky
5275 $ git checkout -b dora-toaster origin/dora-toaster 5275 $ git checkout -b dora-toaster origin/dora-toaster
5276 </literallayout></para></listitem> 5276 </literallayout></para></listitem>
5277 <listitem><para>Be sure your build machine has 5277 <listitem><para>Be sure your build machine has
@@ -5629,7 +5629,7 @@
5629 <para> 5629 <para>
5630 Downloaded archives reside in the 5630 Downloaded archives reside in the
5631 <link linkend='build-directory'>Build Directory</link> in 5631 <link linkend='build-directory'>Build Directory</link> in
5632 <filename>/tmp</filename> and are cleared up when they are no longer in use. 5632 <filename>tmp</filename> and are cleared up when they are no longer in use.
5633 </para> 5633 </para>
5634 5634
5635 <para> 5635 <para>
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 46cd5b30a1..8b0bfc6fa8 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -1675,7 +1675,7 @@
1675 the following is the work directory for the <filename>acl</filename> recipe that 1675 the following is the work directory for the <filename>acl</filename> recipe that
1676 creates the <filename>acl</filename> package: 1676 creates the <filename>acl</filename> package:
1677 <literallayout class='monospaced'> 1677 <literallayout class='monospaced'>
1678 ~/poky/build/tmp/work/i586-poky-linux/acl/2.2.51-r3/ 1678 poky/build/tmp/work/i586-poky-linux/acl/2.2.51-r3/
1679 </literallayout> 1679 </literallayout>
1680 </para> 1680 </para>
1681 1681
@@ -1691,8 +1691,8 @@
1691 for the <filename>acl</filename> package that is being 1691 for the <filename>acl</filename> package that is being
1692 built for a MIPS-based device: 1692 built for a MIPS-based device:
1693 <literallayout class='monospaced'> 1693 <literallayout class='monospaced'>
1694 ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2 1694 poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2
1695 ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2/acl-2.2.51 1695 poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2/acl-2.2.51
1696 </literallayout> 1696 </literallayout>
1697 </para> 1697 </para>
1698 1698
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 0dc4bd58bb..600c789a6d 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -1462,8 +1462,8 @@
1462 <para>For help on using these scripts, simply provide the 1462 <para>For help on using these scripts, simply provide the
1463 <filename>-h</filename> argument as follows: 1463 <filename>-h</filename> argument as follows:
1464 <literallayout class='monospaced'> 1464 <literallayout class='monospaced'>
1465 $ ~/poky/scripts/create-pull-request -h 1465 $ poky/scripts/create-pull-request -h
1466 $ ~/poky/scripts/send-pull-request -h 1466 $ poky/scripts/send-pull-request -h
1467 </literallayout></para></listitem> 1467 </literallayout></para></listitem>
1468 </itemizedlist> 1468 </itemizedlist>
1469 </para> 1469 </para>
diff --git a/documentation/kernel-dev/kernel-dev-maint-appx.xml b/documentation/kernel-dev/kernel-dev-maint-appx.xml
index 5f9788aa31..a7c144ff75 100644
--- a/documentation/kernel-dev/kernel-dev-maint-appx.xml
+++ b/documentation/kernel-dev/kernel-dev-maint-appx.xml
@@ -45,7 +45,7 @@
45 Here is an example that assumes the local Git repository for the kernel is in 45 Here is an example that assumes the local Git repository for the kernel is in
46 a top-level directory named <filename>linux-yocto-3.4</filename>: 46 a top-level directory named <filename>linux-yocto-3.4</filename>:
47 <literallayout class='monospaced'> 47 <literallayout class='monospaced'>
48 $ cd ~/linux-yocto-3.4 48 $ cd linux-yocto-3.4
49 $ git checkout -b meta origin/meta 49 $ git checkout -b meta origin/meta
50 </literallayout> 50 </literallayout>
51 Once you have checked out and switched to the <filename>meta</filename> branch, 51 Once you have checked out and switched to the <filename>meta</filename> branch,
@@ -208,7 +208,7 @@
208 the build tree directory. 208 the build tree directory.
209 The files include the final <filename>.config</filename> file, all the <filename>.o</filename> 209 The files include the final <filename>.config</filename> file, all the <filename>.o</filename>
210 files, the <filename>.a</filename> files, and so forth. 210 files, the <filename>.a</filename> files, and so forth.
211 Since each machine or BSP has its own separate 211 Since each machine or BSP has its own separate
212 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> 212 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
213 in its own separate branch 213 in its own separate branch
214 of the Git repository, you can easily switch between different builds. 214 of the Git repository, you can easily switch between different builds.
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index a3a3e88a07..dc24628e3c 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -829,10 +829,10 @@
829 </section> 829 </section>
830 830
831 <section id='migration-1.5-run'> 831 <section id='migration-1.5-run'>
832 <title><filename>/run</filename></title> 832 <title><filename>run</filename></title>
833 833
834 <para> 834 <para>
835 The <filename>/run</filename> directory from the Filesystem 835 The <filename>run</filename> directory from the Filesystem
836 Hierarchy Standard 3.0 has been introduced. 836 Hierarchy Standard 3.0 has been introduced.
837 You can find some of the implications for this change 837 You can find some of the implications for this change
838 <ulink url='http://cgit.openembedded.org/openembedded-core/commit/?id=0e326280a15b0f2c4ef2ef4ec441f63f55b75873'>here</ulink>. 838 <ulink url='http://cgit.openembedded.org/openembedded-core/commit/?id=0e326280a15b0f2c4ef2ef4ec441f63f55b75873'>here</ulink>.
@@ -1033,7 +1033,7 @@
1033 </para></listitem> 1033 </para></listitem>
1034 <listitem><para> 1034 <listitem><para>
1035 <filename>base-files</filename>: Remove the unnecessary 1035 <filename>base-files</filename>: Remove the unnecessary
1036 <filename>/media/xxx</filename> directories. 1036 <filename>media/xxx</filename> directories.
1037 </para></listitem> 1037 </para></listitem>
1038 <listitem><para> 1038 <listitem><para>
1039 <filename>alsa-state</filename>: Provide an empty 1039 <filename>alsa-state</filename>: Provide an empty
diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml
index b587d46caa..e24ea45281 100644
--- a/documentation/ref-manual/ref-bitbake.xml
+++ b/documentation/ref-manual/ref-bitbake.xml
@@ -222,7 +222,7 @@
222 <para> 222 <para>
223 As each task completes, a timestamp is written to the directory specified by the 223 As each task completes, a timestamp is written to the directory specified by the
224 <filename><link linkend='var-STAMP'>STAMP</link></filename> variable. 224 <filename><link linkend='var-STAMP'>STAMP</link></filename> variable.
225 On subsequent runs, BitBake looks within the <filename>/build/tmp/stamps</filename> 225 On subsequent runs, BitBake looks within the <filename>build/tmp/stamps</filename>
226 directory and does not rerun 226 directory and does not rerun
227 tasks that are already completed unless a timestamp is found to be invalid. 227 tasks that are already completed unless a timestamp is found to be invalid.
228 Currently, invalid timestamps are only considered on a per 228 Currently, invalid timestamps are only considered on a per
diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml
index 3f216e3a64..dedcf67e33 100644
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -38,7 +38,7 @@
38 Here is an example that discovers the recipes whose build is potentially 38 Here is an example that discovers the recipes whose build is potentially
39 changed based on a given feature: 39 changed based on a given feature:
40 <literallayout class='monospaced'> 40 <literallayout class='monospaced'>
41 $ cd $HOME/poky 41 $ cd poky
42 $ git grep 'contains.*MACHINE_FEATURES.*&lt;feature&gt;' 42 $ git grep 'contains.*MACHINE_FEATURES.*&lt;feature&gt;'
43 </literallayout> 43 </literallayout>
44 </para> 44 </para>
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 84deee8899..2b0e8909fe 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -701,10 +701,10 @@
701 <para> 701 <para>
702 The following example uses a complete regular expression 702 The following example uses a complete regular expression
703 to tell BitBake to ignore all recipe and recipe append 703 to tell BitBake to ignore all recipe and recipe append
704 files in the <filename>/meta-ti/recipes-misc/</filename> 704 files in the <filename>meta-ti/recipes-misc/</filename>
705 directory: 705 directory:
706 <literallayout class='monospaced'> 706 <literallayout class='monospaced'>
707 BBMASK = "/meta-ti/recipes-misc/" 707 BBMASK = "meta-ti/recipes-misc/"
708 </literallayout> 708 </literallayout>
709 If you want to mask out multiple directories or recipes, 709 If you want to mask out multiple directories or recipes,
710 use the vertical bar to separate the regular expression 710 use the vertical bar to separate the regular expression
@@ -999,7 +999,7 @@
999 <filename>/etc</filename> or <filename>${bindir}</filename> rather 999 <filename>/etc</filename> or <filename>${bindir}</filename> rather
1000 than <filename>/usr/bin</filename>. 1000 than <filename>/usr/bin</filename>.
1001 You can find a list of these variables at the top of the 1001 You can find a list of these variables at the top of the
1002 <filename>/meta/conf/bitbake.conf</filename> file in the 1002 <filename>meta/conf/bitbake.conf</filename> file in the
1003 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 1003 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
1004 </note> 1004 </note>
1005 </glossdef> 1005 </glossdef>
@@ -1036,7 +1036,7 @@
1036 <glossdef> 1036 <glossdef>
1037 <para> 1037 <para>
1038 Specifies the parent directory of the OpenEmbedded 1038 Specifies the parent directory of the OpenEmbedded
1039 Core Metadata layer (i.e. <filename>/meta</filename>). 1039 Core Metadata layer (i.e. <filename>meta</filename>).
1040 </para> 1040 </para>
1041 1041
1042 <para> 1042 <para>
@@ -1362,7 +1362,7 @@
1362 <para> 1362 <para>
1363 You can set this directory by defining the 1363 You can set this directory by defining the
1364 <filename>DL_DIR</filename> variable in the 1364 <filename>DL_DIR</filename> variable in the
1365 <filename>/conf/local.conf</filename> file. 1365 <filename>conf/local.conf</filename> file.
1366 This directory is self-maintaining and you should not have 1366 This directory is self-maintaining and you should not have
1367 to touch it. 1367 to touch it.
1368 By default, the directory is <filename>downloads</filename> 1368 By default, the directory is <filename>downloads</filename>
@@ -1712,7 +1712,7 @@
1712 <filename>/etc</filename>, or <filename>${bindir}</filename> rather 1712 <filename>/etc</filename>, or <filename>${bindir}</filename> rather
1713 than <filename>/usr/bin</filename>. 1713 than <filename>/usr/bin</filename>.
1714 You can find a list of these variables at the top of the 1714 You can find a list of these variables at the top of the
1715 <filename>/meta/conf/bitbake.conf</filename> file in the 1715 <filename>meta/conf/bitbake.conf</filename> file in the
1716 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 1716 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
1717 </note> 1717 </note>
1718 1718
@@ -2068,7 +2068,7 @@
2068 to a default value using the <filename>?=</filename> operator, using a 2068 to a default value using the <filename>?=</filename> operator, using a
2069 <filename>+=</filename> operation against <filename>IMAGE_INSTALL</filename> 2069 <filename>+=</filename> operation against <filename>IMAGE_INSTALL</filename>
2070 will result in unexpected behavior when used in 2070 will result in unexpected behavior when used in
2071 <filename>/conf/local.conf</filename>. 2071 <filename>conf/local.conf</filename>.
2072 Furthermore, the same operation from within an image recipe may or may not 2072 Furthermore, the same operation from within an image recipe may or may not
2073 succeed depending on the specific situation. 2073 succeed depending on the specific situation.
2074 In both these cases, the behavior is contrary to how most users expect 2074 In both these cases, the behavior is contrary to how most users expect
@@ -4770,7 +4770,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
4770 to keep the unpacked recipe for <filename>db</filename> 4770 to keep the unpacked recipe for <filename>db</filename>
4771 is the following: 4771 is the following:
4772 <literallayout class='monospaced'> 4772 <literallayout class='monospaced'>
4773 ~/poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/db-5.1.19 4773 poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/db-5.1.19
4774 </literallayout> 4774 </literallayout>
4775 </para> 4775 </para>
4776 </glossdef> 4776 </glossdef>
@@ -5888,7 +5888,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
5888 In this case, the working directory the build system uses to build 5888 In this case, the working directory the build system uses to build
5889 the <filename>v86d</filename> package is the following: 5889 the <filename>v86d</filename> package is the following:
5890 <literallayout class='monospaced'> 5890 <literallayout class='monospaced'>
5891 ~/poky/build/tmp/work/qemux86-poky-linux/v86d/01.9-r0 5891 poky/build/tmp/work/qemux86-poky-linux/v86d/01.9-r0
5892 </literallayout> 5892 </literallayout>
5893 </para> 5893 </para>
5894 5894
@@ -5905,7 +5905,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
5905 the <filename>acl</filename> recipe, which is being built for a 5905 the <filename>acl</filename> recipe, which is being built for a
5906 MIPS-based device, is the following: 5906 MIPS-based device, is the following:
5907 <literallayout class='monospaced'> 5907 <literallayout class='monospaced'>
5908 ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2 5908 poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2
5909 </literallayout> 5909 </literallayout>
5910 </para> 5910 </para>
5911 </glossdef> 5911 </glossdef>
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 4d1c2e3f4e..6d4c6b712c 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1149,7 +1149,7 @@
1149 recipe-by-recipe basis through the <filename>LICENSE_FLAGS</filename> variable 1149 recipe-by-recipe basis through the <filename>LICENSE_FLAGS</filename> variable
1150 definition in the affected recipe. 1150 definition in the affected recipe.
1151 For instance, the 1151 For instance, the
1152 <filename>$HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename> 1152 <filename>poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename>
1153 recipe contains the following statement: 1153 recipe contains the following statement:
1154 <literallayout class='monospaced'> 1154 <literallayout class='monospaced'>
1155 LICENSE_FLAGS = "commercial" 1155 LICENSE_FLAGS = "commercial"
@@ -1165,7 +1165,7 @@
1165 <filename>LICENSE_FLAGS_WHITELIST</filename> variable, which is a variable 1165 <filename>LICENSE_FLAGS_WHITELIST</filename> variable, which is a variable
1166 typically defined in your <filename>local.conf</filename> file. 1166 typically defined in your <filename>local.conf</filename> file.
1167 For example, to enable 1167 For example, to enable
1168 the <filename>$HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename> 1168 the <filename>poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename>
1169 package, you could add either the string 1169 package, you could add either the string
1170 "commercial_gst-plugins-ugly" or the more general string 1170 "commercial_gst-plugins-ugly" or the more general string
1171 "commercial" to <filename>LICENSE_FLAGS_WHITELIST</filename>. 1171 "commercial" to <filename>LICENSE_FLAGS_WHITELIST</filename>.
@@ -1312,7 +1312,7 @@
1312 <para> 1312 <para>
1313 Other helpful variables related to commercial 1313 Other helpful variables related to commercial
1314 license handling exist and are defined in the 1314 license handling exist and are defined in the
1315 <filename>$HOME/poky/meta/conf/distro/include/default-distrovars.inc</filename> file: 1315 <filename>poky/meta/conf/distro/include/default-distrovars.inc</filename> file:
1316 <literallayout class='monospaced'> 1316 <literallayout class='monospaced'>
1317 COMMERCIAL_AUDIO_PLUGINS ?= "" 1317 COMMERCIAL_AUDIO_PLUGINS ?= ""
1318 COMMERCIAL_VIDEO_PLUGINS ?= "" 1318 COMMERCIAL_VIDEO_PLUGINS ?= ""
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 49166e15bf..b9df733f3f 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -62,7 +62,7 @@
62 <para> 62 <para>
63 The <filename>target</filename> is the name of the recipe you want to build. 63 The <filename>target</filename> is the name of the recipe you want to build.
64 Common targets are the images in <filename>meta/recipes-core/images</filename>, 64 Common targets are the images in <filename>meta/recipes-core/images</filename>,
65 <filename>/meta/recipes-sato/images</filename>, etc. all found in the 65 <filename>meta/recipes-sato/images</filename>, etc. all found in the
66 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 66 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
67 Or, the target can be the name of a recipe for a specific piece of software such as 67 Or, the target can be the name of a recipe for a specific piece of software such as
68 BusyBox. 68 BusyBox.