summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-03-17 08:21:21 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-18 17:22:21 +0000
commit885415ffd1e24dd08af98129a905ab4f06649949 (patch)
treedf3c01030eae2262c247a91aeac1461c90af7d55 /documentation
parent5622f546c8fa70d276127d6dfbabe90a48523e2f (diff)
downloadpoky-885415ffd1e24dd08af98129a905ab4f06649949.tar.gz
documentation/poky-ref-manual/extendpoky.xml: Spell check
A spell check performed on this chapter. (From OE-Core rev: 20ef5e573e0c835a2f359f61aa89993c3a2244a1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/poky-ref-manual/extendpoky.xml30
1 files changed, 15 insertions, 15 deletions
diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml
index d7d2c6cdde..951468d46c 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -46,7 +46,7 @@
46 "do_install" tasks. 46 "do_install" tasks.
47 The <glossterm><link linkend='var-S'>S</link></glossterm> variable defines the 47 The <glossterm><link linkend='var-S'>S</link></glossterm> variable defines the
48 directory containing the source code, which is set to <glossterm><link linkend='var-WORKDIR'> 48 directory containing the source code, which is set to <glossterm><link linkend='var-WORKDIR'>
49 WORKDIR</link></glossterm> in this case - the directory Bitbake uses for the build. 49 WORKDIR</link></glossterm> in this case - the directory BitBake uses for the build.
50 </para> 50 </para>
51 <programlisting> 51 <programlisting>
52DESCRIPTION = "Simple helloworld application" 52DESCRIPTION = "Simple helloworld application"
@@ -68,7 +68,7 @@ do_install() {
68} 68}
69 </programlisting> 69 </programlisting>
70 <para> 70 <para>
71 By default, the "helloworld", "helloworld-dbg" and "hellworld-dev" 71 By default, the "helloworld", "helloworld-dbg" and "helloworld-dev"
72 packages are built. 72 packages are built.
73 For information on how to customize the packaging process, see 73 For information on how to customize the packaging process, see
74 <link linkend='usingpoky-extend-addpkg-files'>Controlling Package Content</link>. 74 <link linkend='usingpoky-extend-addpkg-files'>Controlling Package Content</link>.
@@ -81,7 +81,7 @@ do_install() {
81 Applications that use autotools such as <filename>autoconf</filename> and 81 Applications that use autotools such as <filename>autoconf</filename> and
82 <filename>automake</filename> require a recipe that has a source archive listed in 82 <filename>automake</filename> require a recipe that has a source archive listed in
83 <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm> and 83 <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm> and
84 <filename>also inherits autotools</filename>, which instructs Bitbake to use the 84 <filename>also inherits autotools</filename>, which instructs BitBake to use the
85 <filename>autotools.bbclass</filename> file, which contains the definitions of all the steps 85 <filename>autotools.bbclass</filename> file, which contains the definitions of all the steps
86 needed to build an autotooled application. 86 needed to build an autotooled application.
87 The result of the build is automatically packaged. 87 The result of the build is automatically packaged.
@@ -114,13 +114,13 @@ inherit autotools gettext
114 <para> 114 <para>
115 Applications that use GNU <filename>make</filename> also require a recipe that has 115 Applications that use GNU <filename>make</filename> also require a recipe that has
116 the source archive listed in <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm>. 116 the source archive listed in <glossterm><link linkend='var-SRC_URI'>SRC_URI</link></glossterm>.
117 You do not need to add a <function>do_compile</function> step since by default Bitbake 117 You do not need to add a <function>do_compile</function> step since by default BitBake
118 starts the <filename>make</filename> command to compile the application. 118 starts the <filename>make</filename> command to compile the application.
119 If you need additional <filename>make</filename> options you should store them in the 119 If you need additional <filename>make</filename> options you should store them in the
120 <glossterm><link linkend='var-EXTRA_OEMAKE'>EXTRA_OEMAKE</link></glossterm> variable. 120 <glossterm><link linkend='var-EXTRA_OEMAKE'>EXTRA_OEMAKE</link></glossterm> variable.
121 Bitbake passes these options into the <filename>make</filename> GNU invocation. 121 BitBake passes these options into the <filename>make</filename> GNU invocation.
122 Note that a "do_install" task is still required. 122 Note that a "do_install" task is still required.
123 Otherwise Bitbake runs an empty "do_install" task by default. 123 Otherwise BitBake runs an empty "do_install" task by default.
124 </para> 124 </para>
125 <para> 125 <para>
126 Some applications might require extra parameters to be passed to the compiler. 126 Some applications might require extra parameters to be passed to the compiler.
@@ -529,7 +529,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
529 <section id="usingpoky-changes"> 529 <section id="usingpoky-changes">
530 <title>Making and Maintaining Changes</title> 530 <title>Making and Maintaining Changes</title>
531 <para> 531 <para>
532 Because Poky offers extreme configurability and flexibility, we recognize that people will want 532 Because Poky is extremely configurable and flexible, we recognize that people will want
533 to extend, configure or optimize Poky for their specific uses. 533 to extend, configure or optimize Poky for their specific uses.
534 To best keep pace with future Poky changes we recommend you make controlled changes to Poky. 534 To best keep pace with future Poky changes we recommend you make controlled changes to Poky.
535 </para> 535 </para>
@@ -541,12 +541,12 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
541 </para> 541 </para>
542 542
543 <section id="usingpoky-changes-layers"> 543 <section id="usingpoky-changes-layers">
544 <title>Bitbake Layers</title> 544 <title>BitBake Layers</title>
545 <para> 545 <para>
546 Often, people want to extend Poky either by adding packages 546 Often, people want to extend Poky either by adding packages
547 or by overriding files contained within Poky to add their own 547 or by overriding files contained within Poky to add their own
548 functionality. 548 functionality.
549 Bitbake has a powerful mechanism called 549 BitBake has a powerful mechanism called
550 "layers", which provides a way to handle this extension in a fully 550 "layers", which provides a way to handle this extension in a fully
551 supported and non-invasive fashion. 551 supported and non-invasive fashion.
552 </para> 552 </para>
@@ -575,7 +575,7 @@ BBLAYERS = " \
575 </para> 575 </para>
576 576
577 <para> 577 <para>
578 Bitbake parses each <filename>conf/layer.conf</filename> file for each layer in BBLAYERS 578 BitBake parses each <filename>conf/layer.conf</filename> file for each layer in BBLAYERS
579 and adds the recipes, classes and configuration contained within the layer to Poky. 579 and adds the recipes, classes and configuration contained within the layer to Poky.
580 To create your own layer, independent of the main Poky repository, 580 To create your own layer, independent of the main Poky repository,
581 simply create a directory with a <filename>conf/layer.conf</filename> file and 581 simply create a directory with a <filename>conf/layer.conf</filename> file and
@@ -613,14 +613,14 @@ BBFILE_PRIORITY_emenlow = "6"
613 Note the use of the <glossterm><link linkend='var-LAYERDIR'>LAYERDIR</link></glossterm> 613 Note the use of the <glossterm><link linkend='var-LAYERDIR'>LAYERDIR</link></glossterm>
614 variable with the immediate expansion operator. 614 variable with the immediate expansion operator.
615 The LAYERDIR variable expands to the directory of the current layer and 615 The LAYERDIR variable expands to the directory of the current layer and
616 requires the immediate expansion operator so that Bitbake does not wait to expand the variable 616 requires the immediate expansion operator so that BitBake does not wait to expand the variable
617 when it's parsing a different directory. 617 when it's parsing a different directory.
618 </para> 618 </para>
619 <para> 619 <para>
620 Bitbake can locate where other bbclass and configuration files are applied through 620 BitBake can locate where other bbclass and configuration files are applied through
621 the <glossterm><link linkend='var-BBPATH'>BBPATH</link></glossterm> 621 the <glossterm><link linkend='var-BBPATH'>BBPATH</link></glossterm>
622 environment variable. 622 environment variable.
623 For these cases, Bitbake uses the first file with the matching name found in BBPATH. 623 For these cases, BitBake uses the first file with the matching name found in BBPATH.
624 This is similar to the way the PATH variable is used for binaries. 624 This is similar to the way the PATH variable is used for binaries.
625 We recommend, therefore, that you use unique bbclass and configuration file names in your 625 We recommend, therefore, that you use unique bbclass and configuration file names in your
626 custom layer. 626 custom layer.
@@ -747,7 +747,7 @@ BBFILE_PRIORITY_emenlow = "6"
747 <para> 747 <para>
748 The core component of any development effort with Poky is often an 748 The core component of any development effort with Poky is often an
749 automated build testing framework and an image generation process. 749 automated build testing framework and an image generation process.
750 You can use these core components to check that the metadata is buildable, 750 You can use these core components to check that the metadata can be built,
751 highlight when commits break the build, and provide up-to-date images that 751 highlight when commits break the build, and provide up-to-date images that
752 allow people to test the end result and use it as a base platform for further 752 allow people to test the end result and use it as a base platform for further
753 development. 753 development.
@@ -969,7 +969,7 @@ LIC_FILES_CHKSUM = "file://../license.html;md5=5c94767cedb5d6987c902ac850ded2c6"
969 This practice allow you to just track the "COPYING" file as long as it is kept up to date. 969 This practice allow you to just track the "COPYING" file as long as it is kept up to date.
970 </para> 970 </para>
971 <tip> 971 <tip>
972 If you specify an empty or invalid "md5" parameter, Bitbake returns an md5 mis-match 972 If you specify an empty or invalid "md5" parameter, BitBake returns an md5 mis-match
973 error and displays the correct "md5" parameter value during the build. The correct parameter 973 error and displays the correct "md5" parameter value during the build. The correct parameter
974 is also captured in the build log. 974 is also captured in the build log.
975 </tip> 975 </tip>