summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/poky-ref-manual/extendpoky.xml17
1 files changed, 9 insertions, 8 deletions
diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml
index 4fc30534ba..73fe0d53fe 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -305,8 +305,8 @@ IMAGE_INSTALL += "strace"
305 variable lists the task packages to build along with the complementary 305 variable lists the task packages to build along with the complementary
306 -dbg and -dev packages. 306 -dbg and -dev packages.
307 For each package added, you can use 307 For each package added, you can use
308 <glossterm><link linkend='var-PACKAGES'>RDEPENDS</link></glossterm> 308 <glossterm><link linkend='var-RDEPENDS'>RDEPENDS</link></glossterm>
309 and <glossterm><link linkend='var-PACKAGES'>RRECOMMENDS</link></glossterm> 309 and <glossterm><link linkend='var-RRECOMMENDS'>RRECOMMENDS</link></glossterm>
310 entries to provide a list of packages the parent task package should contain. 310 entries to provide a list of packages the parent task package should contain.
311 Following is an example: 311 Following is an example:
312 </para> 312 </para>
@@ -336,7 +336,7 @@ RDEPENDS_task-custom-tools = "\
336 336
337RRECOMMENDS_task-custom-tools = "\ 337RRECOMMENDS_task-custom-tools = "\
338 kernel-module-oprofile" 338 kernel-module-oprofile"
339</programlisting> 339 </programlisting>
340 </para> 340 </para>
341 <para> 341 <para>
342 In the previous example, two task packages are created with their dependencies and their 342 In the previous example, two task packages are created with their dependencies and their
@@ -562,7 +562,7 @@ BBLAYERS = " \
562 /path/to/poky/meta-emenlow \ 562 /path/to/poky/meta-emenlow \
563 /path/to/poky/meta-extras \ 563 /path/to/poky/meta-extras \
564 " 564 "
565</literallayout> 565 </literallayout>
566 </para> 566 </para>
567 567
568 <para> 568 <para>
@@ -588,7 +588,7 @@ BBFILE_PRIORITY_emenlow = "6"
588 </para> 588 </para>
589 <para> 589 <para>
590 In the previous example, the recipes for the layers are added to 590 In the previous example, the recipes for the layers are added to
591 <glossterm> <link linkend='var-BBFILES'>BBFILES</link></glossterm>. 591 <glossterm><link linkend='var-BBFILES'>BBFILES</link></glossterm>.
592 The <glossterm><link linkend='var-BBFILE_COLLECTIONS'>BBFILE_COLLECTIONS</link></glossterm> 592 The <glossterm><link linkend='var-BBFILE_COLLECTIONS'>BBFILE_COLLECTIONS</link></glossterm>
593 variable is then appended with the layer name. 593 variable is then appended with the layer name.
594 The <glossterm><link linkend='var-BBFILE_PATTERN'>BBFILE_PATTERN</link></glossterm> variable 594 The <glossterm><link linkend='var-BBFILE_PATTERN'>BBFILE_PATTERN</link></glossterm> variable
@@ -784,7 +784,8 @@ BBFILE_PRIORITY_emenlow = "6"
784 <literallayout class='monospaced'> 784 <literallayout class='monospaced'>
785src/gz all http://www.mysite.com/somedir/deploy/ipk/all 785src/gz all http://www.mysite.com/somedir/deploy/ipk/all
786src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a 786src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a
787src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard</literallayout> 787src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard
788 </literallayout>
788 </section> 789 </section>
789 </section> 790 </section>
790 791
@@ -857,7 +858,7 @@ quilt refresh
857 </programlisting> 858 </programlisting>
858 859
859 You can find the resulting patch file in the 860 You can find the resulting patch file in the
860 <filename class="directory">patches/</filename> subdirectory of the source 861 <filename>patches/</filename> subdirectory of the source
861 (<glossterm><link linkend='var-S'>S</link></glossterm>) directory. 862 (<glossterm><link linkend='var-S'>S</link></glossterm>) directory.
862 For future builds you should copy the patch into Poky metadata and add it into the 863 For future builds you should copy the patch into Poky metadata and add it into the
863 <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm> of a recipe. 864 <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm> of a recipe.
@@ -883,7 +884,7 @@ SRC_URI += "file://NAME-OF-PATCH.patch"
883 </para> 884 </para>
884 885
885 <section id="usingpoky-specifying-LIC_FILES_CHKSUM"> 886 <section id="usingpoky-specifying-LIC_FILES_CHKSUM">
886 <title>Specifying the LIC_FILES_CHKSUM Variable </title> 887 <title>Specifying the LIC_FILES_CHKSUM Variable</title>
887 <para> 888 <para>
888 The <glossterm><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></glossterm> 889 The <glossterm><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></glossterm>
889 variable contains checksums of the license text in the recipe source code. 890 variable contains checksums of the license text in the recipe source code.