summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml18
1 files changed, 9 insertions, 9 deletions
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>