summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/bsp-guide/bsp.xml4
-rw-r--r--documentation/poky-ref-manual/development.xml2
-rw-r--r--documentation/poky-ref-manual/faq.xml10
-rw-r--r--documentation/poky-ref-manual/ref-bitbake.xml4
-rw-r--r--documentation/poky-ref-manual/ref-classes.xml6
-rw-r--r--documentation/poky-ref-manual/ref-images.xml2
-rw-r--r--documentation/poky-ref-manual/ref-structure.xml8
-rw-r--r--documentation/poky-ref-manual/ref-variables.xml10
-rw-r--r--documentation/poky-ref-manual/resources.xml2
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml2
10 files changed, 25 insertions, 25 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 492a7956d2..7f793c896e 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -131,7 +131,7 @@
131 meta-crownbay/conf/machine/crownbay.conf 131 meta-crownbay/conf/machine/crownbay.conf
132 meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay/machconfig 132 meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay/machconfig
133 meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend 133 meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
134 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xcorg.conf 134 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xorg.conf
135 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 135 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
136 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore 136 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore
137 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin_1.7.99.2.bb 137 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin_1.7.99.2.bb
@@ -355,7 +355,7 @@
355 All files that are needed for the BSP to support a display are kept here. 355 All files that are needed for the BSP to support a display are kept here.
356 For example, in the Crownbay BSP several display support files exist: 356 For example, in the Crownbay BSP several display support files exist:
357 <literallayout class='monospaced'> 357 <literallayout class='monospaced'>
358 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xcorg.conf 358 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xorg.conf
359 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 359 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
360 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore 360 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore
361 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin_1.7.99.2.bb 361 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin_1.7.99.2.bb
diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml
index 53e6904545..15f40fed6b 100644
--- a/documentation/poky-ref-manual/development.xml
+++ b/documentation/poky-ref-manual/development.xml
@@ -292,7 +292,7 @@
292 <para>It is worth remembering that when using <filename>devshell</filename> 292 <para>It is worth remembering that when using <filename>devshell</filename>
293 you need to use the full compiler name such as <filename>arm-poky-linux-gnueabi-gcc</filename> 293 you need to use the full compiler name such as <filename>arm-poky-linux-gnueabi-gcc</filename>
294 instead of just using <filename>gcc</filename>. 294 instead of just using <filename>gcc</filename>.
295 The same applies to other applications such as <filename>bintuils</filename>, 295 The same applies to other applications such as <filename>binutils</filename>,
296 <filename>libtool</filename> and so forth. 296 <filename>libtool</filename> and so forth.
297 The Yocto Project has setup environment variables such as <filename>CC</filename> 297 The Yocto Project has setup environment variables such as <filename>CC</filename>
298 to assist applications, such as <filename>make</filename> to find the correct tools.</para> 298 to assist applications, such as <filename>make</filename> to find the correct tools.</para>
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
index 0982d9d953..6a1f741aca 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -124,7 +124,7 @@
124 </question> 124 </question>
125 <answer> 125 <answer>
126 <para> 126 <para>
127 The <ulink url='http://vernier.com/labquest/'>Vernier Labquest</ulink> is using Poky (for more about the Labquest see the case study at OpenedHand). There are a number of pre-production devices using Poky and we will announce those as soon as they are released. 127 The <ulink url='http://vernier.com/labquest/'>Vernier LabQuest</ulink> is using Poky (for more about the LabQuest see the case study at OpenedHand). There are a number of pre-production devices using Poky and we will announce those as soon as they are released.
128 </para> 128 </para>
129 </answer> 129 </answer>
130 </qandaentry> 130 </qandaentry>
@@ -299,7 +299,7 @@
299 <qandaentry> 299 <qandaentry>
300 <question> 300 <question>
301 <para> 301 <para>
302 I'm using Ubuntu Intrepid and am seeing build failures. Whats wrong? 302 I'm using Ubuntu Intrepid and am seeing build failures. Whats wrong?
303 </para> 303 </para>
304 </question> 304 </question>
305 <answer> 305 <answer>
@@ -315,7 +315,7 @@
315 <qandaentry> 315 <qandaentry>
316 <question> 316 <question>
317 <para> 317 <para>
318 Whats the difference between foo and foo-native? 318 Whats the difference between foo and foo-native?
319 </para> 319 </para>
320 </question> 320 </question>
321 <answer> 321 <answer>
@@ -473,7 +473,7 @@
473 <answer> 473 <answer>
474 <para> 474 <para>
475 The way Poky obtains source code is highly configurable. 475 The way Poky obtains source code is highly configurable.
476 You can setup Poky to get source code in most environmnents if 476 You can setup Poky to get source code in most environments if
477 HTTP transport is available. 477 HTTP transport is available.
478 </para> 478 </para>
479 <para> 479 <para>
@@ -501,7 +501,7 @@
501 <para> 501 <para>
502 These changes cause Poky to intercept GIT, FTP, HTTP, and HTTPS 502 These changes cause Poky to intercept GIT, FTP, HTTP, and HTTPS
503 requests and direct them to the <filename>http://</filename> sources mirror. 503 requests and direct them to the <filename>http://</filename> sources mirror.
504 You can use <filename>file://</filename> urls to point to local directories 504 You can use <filename>file://</filename> URLs to point to local directories
505 or network shares as well. 505 or network shares as well.
506 </para> 506 </para>
507 <para> 507 <para>
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index f0816103d8..b11bd5a2fd 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -70,7 +70,7 @@
70 The <filename>base.bbclass</filename> file is always included. 70 The <filename>base.bbclass</filename> file is always included.
71 Other classes that are specified in the configuration using the 71 Other classes that are specified in the configuration using the
72 <filename><link linkend='var-INHERIT'>INHERIT</link></filename> 72 <filename><link linkend='var-INHERIT'>INHERIT</link></filename>
73 variable are also inculded. 73 variable are also included.
74 Class files are searched for in a <filename>classes</filename> subdirectory 74 Class files are searched for in a <filename>classes</filename> subdirectory
75 under the paths in <filename>BBPATH</filename> in the same way as 75 under the paths in <filename>BBPATH</filename> in the same way as
76 configuration files. 76 configuration files.
@@ -128,7 +128,7 @@
128 <para> 128 <para>
129 Sometimes a target might have multiple providers. 129 Sometimes a target might have multiple providers.
130 A common example is "virtual/kernel", which is provided by each kernel package. 130 A common example is "virtual/kernel", which is provided by each kernel package.
131 Each machine often elects the best kernel provider by using a line similar to the 131 Each machine often selects the best kernel provider by using a line similar to the
132 following in the machine configuration file: 132 following in the machine configuration file:
133 </para> 133 </para>
134 134
diff --git a/documentation/poky-ref-manual/ref-classes.xml b/documentation/poky-ref-manual/ref-classes.xml
index d054df1204..905538d878 100644
--- a/documentation/poky-ref-manual/ref-classes.xml
+++ b/documentation/poky-ref-manual/ref-classes.xml
@@ -81,7 +81,7 @@
81 <title>Alternatives - <filename>update-alternatives.bbclass</filename></title> 81 <title>Alternatives - <filename>update-alternatives.bbclass</filename></title>
82 82
83 <para> 83 <para>
84 Several programs can fulfill the same or similar function and be installed with the same name. 84 Several programs can fulfil the same or similar function and be installed with the same name.
85 For example, the <filename>ar</filename> command is available from the 85 For example, the <filename>ar</filename> command is available from the
86 <filename>busybox</filename>, <filename>binutils</filename> and 86 <filename>busybox</filename>, <filename>binutils</filename> and
87 <filename>elfutils</filename> packages. 87 <filename>elfutils</filename> packages.
@@ -211,7 +211,7 @@
211 Recipes for Perl modules are simple. 211 Recipes for Perl modules are simple.
212 These recipes usually only need to point to the source's archive and then inherit the 212 These recipes usually only need to point to the source's archive and then inherit the
213 proper <filename>.bbclass</filename> file. 213 proper <filename>.bbclass</filename> file.
214 Building is split into two methods dependling on which method the module authors used. 214 Building is split into two methods depending on which method the module authors used.
215 </para> 215 </para>
216 216
217 <para> 217 <para>
@@ -360,7 +360,7 @@
360 used to provide cached test results so these tests can be skipped over but 360 used to provide cached test results so these tests can be skipped over but
361 still make the correct values available. 361 still make the correct values available.
362 The <filename><link linkend='structure-meta-site'>meta/site directory</link></filename> 362 The <filename><link linkend='structure-meta-site'>meta/site directory</link></filename>
363 contains test results sorted into different categories such as architecture, endianess, and 363 contains test results sorted into different categories such as architecture, endianness, and
364 the libc used. 364 the libc used.
365 Site information provides a list of files containing data relevant to 365 Site information provides a list of files containing data relevant to
366 the current build in the 366 the current build in the
diff --git a/documentation/poky-ref-manual/ref-images.xml b/documentation/poky-ref-manual/ref-images.xml
index 19a2a37efd..c67a01fbe0 100644
--- a/documentation/poky-ref-manual/ref-images.xml
+++ b/documentation/poky-ref-manual/ref-images.xml
@@ -86,7 +86,7 @@
86 from a USB device or CD as is.</para></listitem> 86 from a USB device or CD as is.</para></listitem>
87 <listitem><para><emphasis><filename>core-image-clutter</filename>:</emphasis> 87 <listitem><para><emphasis><filename>core-image-clutter</filename>:</emphasis>
88 An image with support for the Open GL-based toolkit Clutter, which enables development of 88 An image with support for the Open GL-based toolkit Clutter, which enables development of
89 rich and animated graphical user interaces.</para></listitem> 89 rich and animated graphical user interfaces.</para></listitem>
90 <listitem><para><emphasis><filename>core-image-sato</filename>:</emphasis> 90 <listitem><para><emphasis><filename>core-image-sato</filename>:</emphasis>
91 An image with Sato support, a mobile environment and visual style that works well 91 An image with Sato support, a mobile environment and visual style that works well
92 with mobile devices. 92 with mobile devices.
diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index 3e3b7944d3..be81faf586 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -173,7 +173,7 @@
173 <title><filename>build/pseudodone</filename></title> 173 <title><filename>build/pseudodone</filename></title>
174 174
175 <para> 175 <para>
176 This tag file indicates that the intitial pseudo binary was created. 176 This tag file indicates that the initial pseudo binary was created.
177 The file is built the first time BitBake is invoked. 177 The file is built the first time BitBake is invoked.
178 </para> 178 </para>
179 </section> 179 </section>
@@ -468,7 +468,7 @@
468 Any distribution-specific configuration is controlled from this directory. 468 Any distribution-specific configuration is controlled from this directory.
469 The Yocto Project only contains the Yocto Project distribution so 469 The Yocto Project only contains the Yocto Project distribution so
470 <filename>defaultsetup.conf</filename> is the main file here. 470 <filename>defaultsetup.conf</filename> is the main file here.
471 This directory includes the versions and SRCDATES for applications that are configured here. 471 This directory includes the versions and SRCDATEs for applications that are configured here.
472 An example of an alternative configuration is <filename>poky-bleeding.conf</filename> 472 An example of an alternative configuration is <filename>poky-bleeding.conf</filename>
473 although this file mainly inherits its configuration from the Yocto Project itself. 473 although this file mainly inherits its configuration from the Yocto Project itself.
474 </para> 474 </para>
@@ -479,7 +479,7 @@
479 479
480 <para> 480 <para>
481 This directory contains anything linking to specific hardware or hardware configuration information 481 This directory contains anything linking to specific hardware or hardware configuration information
482 such as "uboot" and "grub". 482 such as "u-boot" and "grub".
483 </para> 483 </para>
484 </section> 484 </section>
485 485
@@ -575,7 +575,7 @@
575 575
576 <para> 576 <para>
577 This directory contains recipes that used by other recipes, but that are not directly 577 This directory contains recipes that used by other recipes, but that are not directly
578 included in images (i.e. depenendies of other recipes). 578 included in images (i.e. dependencies of other recipes).
579 </para> 579 </para>
580 </section> 580 </section>
581 581
diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml
index 40ef56d368..e60f2ae5ae 100644
--- a/documentation/poky-ref-manual/ref-variables.xml
+++ b/documentation/poky-ref-manual/ref-variables.xml
@@ -76,7 +76,7 @@
76 <glossdef> 76 <glossdef>
77 <para>Identifies layer-specific <filename>.bbfiles</filename>, which contain recipes 77 <para>Identifies layer-specific <filename>.bbfiles</filename>, which contain recipes
78 used by BitBake to build software. 78 used by BitBake to build software.
79 The Variable is appended with a layer name.</para> 79 The variable is appended with a layer name.</para>
80 </glossdef> 80 </glossdef>
81 </glossentry> 81 </glossentry>
82 82
@@ -322,7 +322,7 @@
322 <filename><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></filename> 322 <filename><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></filename>
323 variable generally configured in image recipes. 323 variable generally configured in image recipes.
324 You can use this variable to add more features in addition to those. 324 You can use this variable to add more features in addition to those.
325 Here are some exmaples of features you can add:</para> 325 Here are some examples of features you can add:</para>
326 <literallayout class='monospaced'> 326 <literallayout class='monospaced'>
327 "dbg-pkgs" - Adds -dbg packages for all installed packages 327 "dbg-pkgs" - Adds -dbg packages for all installed packages
328 including symbol information for debugging and 328 including symbol information for debugging and
@@ -647,7 +647,7 @@
647 647
648 <glossentry id='var-PACKAGE_DESCRIPTION'><glossterm>PACKAGE_DESCRIPTION</glossterm> 648 <glossentry id='var-PACKAGE_DESCRIPTION'><glossterm>PACKAGE_DESCRIPTION</glossterm>
649 <glossdef> 649 <glossdef>
650 <para>The long form description of the binary package for packaging sytems such as 650 <para>The long form description of the binary package for packaging systems such as
651 <filename>ipkg</filename>, <filename>rpm</filename> or <filename>debian</filename>. 651 <filename>ipkg</filename>, <filename>rpm</filename> or <filename>debian</filename>.
652 By default, this variable inherits <filename>DESCRIPTION</filename>.</para> 652 By default, this variable inherits <filename>DESCRIPTION</filename>.</para>
653 </glossdef> 653 </glossdef>
@@ -664,7 +664,7 @@
664 <glossentry id='var-PACKAGE_SUMMARY'><glossterm>PACKAGE_SUMMARY</glossterm> 664 <glossentry id='var-PACKAGE_SUMMARY'><glossterm>PACKAGE_SUMMARY</glossterm>
665 <glossdef> 665 <glossdef>
666 <para>The short (72 character limit suggested) summary of the binary 666 <para>The short (72 character limit suggested) summary of the binary
667 package for packaging sytems such as <filename>ipkg</filename>, 667 package for packaging systems such as <filename>ipkg</filename>,
668 <filename>rpm</filename> or <filename>debian</filename>. 668 <filename>rpm</filename> or <filename>debian</filename>.
669 By default, this variable inherits <filename>DESCRIPTION</filename>.</para> 669 By default, this variable inherits <filename>DESCRIPTION</filename>.</para>
670 </glossdef> 670 </glossdef>
@@ -1026,7 +1026,7 @@
1026 <glossentry id='var-TERMCMD'><glossterm>TERMCMD</glossterm> 1026 <glossentry id='var-TERMCMD'><glossterm>TERMCMD</glossterm>
1027 <glossdef> 1027 <glossdef>
1028 <para> 1028 <para>
1029 This command is used by BitBake to lauch a terminal window with a 1029 This command is used by BitBake to launch a terminal window with a
1030 shell. 1030 shell.
1031 The shell is unspecified so the user's default shell is used. 1031 The shell is unspecified so the user's default shell is used.
1032 By default, the variable is set to "gnome-terminal" but it can 1032 By default, the variable is set to "gnome-terminal" but it can
diff --git a/documentation/poky-ref-manual/resources.xml b/documentation/poky-ref-manual/resources.xml
index eae37fe136..69e998b6ed 100644
--- a/documentation/poky-ref-manual/resources.xml
+++ b/documentation/poky-ref-manual/resources.xml
@@ -72,7 +72,7 @@
72 <itemizedlist> 72 <itemizedlist>
73 <listitem><para> 73 <listitem><para>
74 <ulink url='http://yoctoproject.org'>The Yocto Project website</ulink> - The home site 74 <ulink url='http://yoctoproject.org'>The Yocto Project website</ulink> - The home site
75 for Yocto Project. 75 for the Yocto Project.
76 </para></listitem> 76 </para></listitem>
77<!-- <listitem><para> 77<!-- <listitem><para>
78 <ulink url='http://pokylinux.org'>The Poky website</ulink> - The home site 78 <ulink url='http://pokylinux.org'>The Poky website</ulink> - The home site
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index d26b2b7984..4abe93f146 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -468,7 +468,7 @@
468 Here are some other tips that you might find useful: 468 Here are some other tips that you might find useful:
469 <itemizedlist> 469 <itemizedlist>
470 <listitem><para>When adding new packages, it is worth watching for 470 <listitem><para>When adding new packages, it is worth watching for
471 undesireable items making their way into compiler command lines. 471 undesirable items making their way into compiler command lines.
472 For example, you do not want references to local system files like 472 For example, you do not want references to local system files like
473 <filename>/usr/lib/</filename> or <filename>/usr/include/</filename>. 473 <filename>/usr/lib/</filename> or <filename>/usr/include/</filename>.
474 </para></listitem> 474 </para></listitem>