summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-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 7167ae3c35..ad8918dcb8 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -257,14 +257,14 @@ fi
257 </section> 257 </section>
258 258
259 <section id='usingpoky-extend-customimage'> 259 <section id='usingpoky-extend-customimage'>
260 <title>Customising Images</title> 260 <title>Customizing Images</title>
261 <para> 261 <para>
262 You can customize Poky images to satisfy particular requirements. 262 You can customize Poky images to satisfy particular requirements.
263 This section describes several methods and provides guidelines for each. 263 This section describes several methods and provides guidelines for each.
264 </para> 264 </para>
265 265
266 <section id='usingpoky-extend-customimage-custombb'> 266 <section id='usingpoky-extend-customimage-custombb'>
267 <title>Customising Images Using Custom .bb Files</title> 267 <title>Customizing Images Using Custom .bb Files</title>
268 <para> 268 <para>
269 One way to get additional software into an image is to create a custom image. 269 One way to get additional software into an image is to create a custom image.
270 The following example shows the form for the two lines you need: 270 The following example shows the form for the two lines you need:
@@ -295,7 +295,7 @@ IMAGE_INSTALL += "strace"
295 </section> 295 </section>
296 296
297 <section id='usingpoky-extend-customimage-customtasks'> 297 <section id='usingpoky-extend-customimage-customtasks'>
298 <title>Customising Images Using Custom Tasks</title> 298 <title>Customizing Images Using Custom Tasks</title>
299 <para> 299 <para>
300 For complex custom images, the best approach is to create a custom task package 300 For complex custom images, the best approach is to create a custom task package
301 that is used to build the image or images. 301 that is used to build the image or images.
@@ -350,7 +350,7 @@ RRECOMMENDS_task-custom-tools = "\
350 </section> 350 </section>
351 351
352 <section id='usingpoky-extend-customimage-imagefeatures'> 352 <section id='usingpoky-extend-customimage-imagefeatures'>
353 <title>Customising Images Using Custom IMAGE_FEATURES</title> 353 <title>Customizing Images Using Custom IMAGE_FEATURES</title>
354 <para> 354 <para>
355 Ultimately users might want to add extra image "features" as used by Poky with the 355 Ultimately users might want to add extra image "features" as used by Poky with the
356 <glossterm><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></glossterm> 356 <glossterm><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></glossterm>
@@ -368,9 +368,9 @@ RRECOMMENDS_task-custom-tools = "\
368 </section> 368 </section>
369 369
370 <section id='usingpoky-extend-customimage-localconf'> 370 <section id='usingpoky-extend-customimage-localconf'>
371 <title>Customising Images Using local.conf</title> 371 <title>Customizing Images Using local.conf</title>
372 <para> 372 <para>
373 It is possible to customise image contents by abusing variables used by distribution 373 It is possible to customize image contents by abusing variables used by distribution
374 maintainers in local.conf. 374 maintainers in local.conf.
375 This method only allows the addition of packages and is not recommended. 375 This method only allows the addition of packages and is not recommended.
376 </para> 376 </para>
@@ -497,7 +497,7 @@ COMPATIBLE_MACHINE = '(qemux86|qemumips)'
497 Reasonable defaults are used in most cases, but if customization is 497 Reasonable defaults are used in most cases, but if customization is
498 necessary you need to create a <filename>machconfig</filename> file 498 necessary you need to create a <filename>machconfig</filename> file
499 under <filename>meta/packages/formfactor/files/MACHINENAME/</filename>, 499 under <filename>meta/packages/formfactor/files/MACHINENAME/</filename>,
500 where <literal>MACHINENAME</literal> is the name for which this infomation 500 where <literal>MACHINENAME</literal> is the name for which this information
501 applies. 501 applies.
502 For information about the settings available and the defaults, see 502 For information about the settings available and the defaults, see
503 <filename>meta/packages/formfactor/files/config</filename>. 503 <filename>meta/packages/formfactor/files/config</filename>.
@@ -521,8 +521,8 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
521 <section id="usingpoky-changes"> 521 <section id="usingpoky-changes">
522 <title>Making and Maintaining Changes</title> 522 <title>Making and Maintaining Changes</title>
523 <para> 523 <para>
524 Because Poky offers extreme configurability and fliexibility, we recognize that people will want 524 Because Poky offers extreme configurability and flexibility, we recognize that people will want
525 to extend, configure or optimise Poky for their specific uses. 525 to extend, configure or optimize Poky for their specific uses.
526 To best keep pace with future Poky changes we recommend you make controlled changes to Poky. 526 To best keep pace with future Poky changes we recommend you make controlled changes to Poky.
527 </para> 527 </para>
528 <para> 528 <para>
@@ -546,7 +546,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
546 The Poky tree includes several additional layers such as meta-emenlow and meta-extras 546 The Poky tree includes several additional layers such as meta-emenlow and meta-extras
547 that demonstrate this functionality. 547 that demonstrate this functionality.
548 The meta-emenlow layer is an example layer that by default is enabled. 548 The meta-emenlow layer is an example layer that by default is enabled.
549 However, the meta-extras repostory is not enabled by default. 549 However, the meta-extras repository is not enabled by default.
550 It is easy though to enable any layer. 550 It is easy though to enable any layer.
551 You simply add the layer's path to the 551 You simply add the layer's path to the
552 <glossterm><link linkend='var-BBLAYERS'>BBLAYERS</link></glossterm> variable in your 552 <glossterm><link linkend='var-BBLAYERS'>BBLAYERS</link></glossterm> variable in your
@@ -612,7 +612,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
612 Bitbake can locate where other bbclass and configuration files are applied through 612 Bitbake can locate where other bbclass and configuration files are applied through
613 the <glossterm><link linkend='var-BBPATH'>BBPATH</link></glossterm> 613 the <glossterm><link linkend='var-BBPATH'>BBPATH</link></glossterm>
614 environment variable. 614 environment variable.
615 For these cases, Bitake uses the first file with the matching name found in BBPATH. 615 For these cases, Bitbake uses the first file with the matching name found in BBPATH.
616 This is similar to the way the PATH variable is used for binaries. 616 This is similar to the way the PATH variable is used for binaries.
617 We recommend, therefore, that you use unique bbclass and configuration file names in your 617 We recommend, therefore, that you use unique bbclass and configuration file names in your
618 custom layer. 618 custom layer.
@@ -659,7 +659,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
659 <literallayout class='monospaced'> 659 <literallayout class='monospaced'>
660 bitbake/data.py: Add emit_func() and generate_dependencies() functions 660 bitbake/data.py: Add emit_func() and generate_dependencies() functions
661 661
662 These functions allow generation of dependency data between funcitons and 662 These functions allow generation of dependency data between functions and
663 variables allowing moves to be made towards generating checksums and allowing 663 variables allowing moves to be made towards generating checksums and allowing
664 use of the dependency information in other parts of bitbake. 664 use of the dependency information in other parts of bitbake.
665 665
@@ -711,7 +711,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
711 opkg upgrade</filename> (or similar commands for dpkg/apt or rpm-based systems). 711 opkg upgrade</filename> (or similar commands for dpkg/apt or rpm-based systems).
712 </para> 712 </para>
713 <para> 713 <para>
714 The goal is to ensure Poky has upgradable packages in all cases. 714 The goal is to ensure Poky has upgradeable packages in all cases.
715 </para> 715 </para>
716 </section> 716 </section>
717 717
@@ -775,7 +775,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
775 <section id="usingpoky-changes-updatingimages"> 775 <section id="usingpoky-changes-updatingimages">
776 <title>Updating Existing Images</title> 776 <title>Updating Existing Images</title>
777 <para> 777 <para>
778 Often, rather than reflashing a new image you might wish to install updated 778 Often, rather than re-flashing a new image you might wish to install updated
779 packages into an existing running system. 779 packages into an existing running system.
780 You can do this by first sharing the 780 You can do this by first sharing the
781 <filename class="directory">tmp/deploy/ipk/</filename> directory 781 <filename class="directory">tmp/deploy/ipk/</filename> directory
@@ -927,7 +927,7 @@ LIC_FILES_CHKSUM = "file://../license.html;md5=5c94767cedb5d6987c902ac850ded2c6"
927 As mentioned in the previous section the LIC_FILES_CHKSUM variable lists all the 927 As mentioned in the previous section the LIC_FILES_CHKSUM variable lists all the
928 important files that contain the license text for the source code. 928 important files that contain the license text for the source code.
929 Using this variable you can specify the line on which the license text starts and ends 929 Using this variable you can specify the line on which the license text starts and ends
930 by supplyiing "beginline" and "endline" parameters. 930 by supplying "beginline" and "endline" parameters.
931 If you do not use the "beginline" parameter then it is assumed that the text begins on the 931 If you do not use the "beginline" parameter then it is assumed that the text begins on the
932 first line of the file. 932 first line of the file.
933 Similarly, if you do not use the "endline" parameter it is assumed that the license text 933 Similarly, if you do not use the "endline" parameter it is assumed that the license text