diff options
author | Robert P. J. Day <rpjday@crashcourse.ca> | 2012-06-19 07:14:52 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-06-21 13:03:07 +0100 |
commit | f3e184af046cb72328f66183501fa03c710383fe (patch) | |
tree | 36bb968d39ad3067a78b02cd3b12fb0d8a6aea94 /documentation/dev-manual | |
parent | a291d007b697c9d5bfe223f737455f6a61bdaf8f (diff) | |
download | poky-f3e184af046cb72328f66183501fa03c710383fe.tar.gz |
documentation/dev-manual/dev-manual-newbie.xml: Typos fixed.
Typoes/fixes to chapter 3.
(From yocto-docs rev: 5cf906df6ae8a729a8f10510a89e570ed9d900e7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 1f41d1e935..6a8d39caae 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
@@ -23,7 +23,7 @@ | |||
23 | Open source philosophy is characterized by software development directed by peer production | 23 | Open source philosophy is characterized by software development directed by peer production |
24 | and collaboration through an active community of developers. | 24 | and collaboration through an active community of developers. |
25 | Contrast this to the more standard centralized development models used by commercial software | 25 | Contrast this to the more standard centralized development models used by commercial software |
26 | companies where a finite set of developers produce a product for sale using a defined set | 26 | companies where a finite set of developers produces a product for sale using a defined set |
27 | of procedures that ultimately result in an end product whose architecture and source material | 27 | of procedures that ultimately result in an end product whose architecture and source material |
28 | are closed to the public. | 28 | are closed to the public. |
29 | </para> | 29 | </para> |
@@ -97,7 +97,7 @@ | |||
97 | <para> | 97 | <para> |
98 | Most teams have many pieces of software undergoing active development at any given time. | 98 | Most teams have many pieces of software undergoing active development at any given time. |
99 | You can derive large benefits by putting these pieces under the control of a source | 99 | You can derive large benefits by putting these pieces under the control of a source |
100 | control system that is compatible with the Yocto Project (i.e. Git or Subversion (SVN). | 100 | control system that is compatible with the Yocto Project (i.e. Git or Subversion (SVN)). |
101 | You can then set the autobuilder to pull the latest revisions of the packages | 101 | You can then set the autobuilder to pull the latest revisions of the packages |
102 | and test the latest commits by the builds. | 102 | and test the latest commits by the builds. |
103 | This practice quickly highlights issues. | 103 | This practice quickly highlights issues. |
@@ -239,14 +239,14 @@ | |||
239 | tools and utilities that allow you to develop software for targeted architectures. | 239 | tools and utilities that allow you to develop software for targeted architectures. |
240 | This toolchain contains cross-compilers, linkers, and debuggers that are specific to | 240 | This toolchain contains cross-compilers, linkers, and debuggers that are specific to |
241 | an architecture. | 241 | an architecture. |
242 | You can use the Yocto Project to build cross-development toolchains in tarball form that when | 242 | You can use the Yocto Project to build cross-development toolchains in tarball form that, when |
243 | unpacked contain the development tools you need to cross-compile and test your software. | 243 | unpacked, contain the development tools you need to cross-compile and test your software. |
244 | The Yocto Project ships with images that contain toolchains for supported architectures | 244 | The Yocto Project ships with images that contain toolchains for supported architectures |
245 | as well. | 245 | as well. |
246 | Sometimes this toolchain is referred to as the meta-toolchain.</para></listitem> | 246 | Sometimes this toolchain is referred to as the meta-toolchain.</para></listitem> |
247 | <listitem><para><emphasis>Image:</emphasis> An image is the result produced when | 247 | <listitem><para><emphasis>Image:</emphasis> An image is the result produced when |
248 | BitBake processes a given collection of recipes and related metadata. | 248 | BitBake processes a given collection of recipes and related metadata. |
249 | Images are the binary output that runs on specific hardware and for specific | 249 | Images are the binary output that run on specific hardware and for specific |
250 | use cases. | 250 | use cases. |
251 | For a list of the supported image types that the Yocto Project provides, see the | 251 | For a list of the supported image types that the Yocto Project provides, see the |
252 | "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" | 252 | "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" |
@@ -530,9 +530,9 @@ | |||
530 | $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; | 530 | $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; |
531 | </literallayout> | 531 | </literallayout> |
532 | In this example, the name of the top-level directory of your local Yocto Project | 532 | In this example, the name of the top-level directory of your local Yocto Project |
533 | Files Git repository is <filename>poky</filename>. | 533 | Files Git repository is <filename>poky</filename>, |
534 | And, the name of the local working area (or local branch) you have created and checked | 534 | and the name of the local working area (or local branch) you have created and checked |
535 | out is named <filename>&DISTRO_NAME;</filename>. | 535 | out is <filename>&DISTRO_NAME;</filename>. |
536 | The files in your repository now reflect the same files that are in the | 536 | The files in your repository now reflect the same files that are in the |
537 | <filename>&DISTRO_NAME;</filename> development branch of the Yocto Project's | 537 | <filename>&DISTRO_NAME;</filename> development branch of the Yocto Project's |
538 | <filename>poky</filename> repository. | 538 | <filename>poky</filename> repository. |