diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-07-13 11:28:34 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-07-17 10:54:09 +0100 |
commit | 402383637b9a20614bc56221f86ff5b9013519d2 (patch) | |
tree | 9cf339114663f68d3927b9c51706d17680724971 /documentation/poky-ref-manual/technical-details.xml | |
parent | 30f491637c9e4d366eef6cfe2e7e3966d02f3bd7 (diff) | |
download | poky-402383637b9a20614bc56221f86ff5b9013519d2.tar.gz |
documentation/poky-ref-manual: Fixed various references to YP
I did a scrub for "Yocto Project" and found some that could be
changed.
(From yocto-docs rev: 985062b6a9320e8a3ca3d3dafb6516db4fbc5bd5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/technical-details.xml')
-rw-r--r-- | documentation/poky-ref-manual/technical-details.xml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml index 2c6f7c2b98..717015be5c 100644 --- a/documentation/poky-ref-manual/technical-details.xml +++ b/documentation/poky-ref-manual/technical-details.xml | |||
@@ -15,7 +15,7 @@ | |||
15 | 15 | ||
16 | <para> | 16 | <para> |
17 | The BitBake task executor together with various types of configuration files form the | 17 | The BitBake task executor together with various types of configuration files form the |
18 | Yocto Project core. | 18 | OpenEmbedded Core. |
19 | This section overviews the BitBake task executor and the | 19 | This section overviews the BitBake task executor and the |
20 | configuration files by describing what they are used for and how they interact. | 20 | configuration files by describing what they are used for and how they interact. |
21 | </para> | 21 | </para> |
@@ -55,7 +55,7 @@ | |||
55 | <title>BitBake</title> | 55 | <title>BitBake</title> |
56 | 56 | ||
57 | <para> | 57 | <para> |
58 | BitBake is the tool at the heart of the Yocto Project and is responsible | 58 | BitBake is the tool at the heart of the OpenEmbedded build system and is responsible |
59 | for parsing the metadata, generating a list of tasks from it, | 59 | for parsing the metadata, generating a list of tasks from it, |
60 | and then executing those tasks. | 60 | and then executing those tasks. |
61 | To see a list of the options BitBake supports, use the following help command: | 61 | To see a list of the options BitBake supports, use the following help command: |
@@ -115,8 +115,8 @@ | |||
115 | 115 | ||
116 | <para> | 116 | <para> |
117 | The term "package" can also be used to describe recipes. | 117 | The term "package" can also be used to describe recipes. |
118 | However, since the same word is used for the packaged output from the Yocto | 118 | However, since the same word is used for the packaged output from the OpenEmbedded |
119 | Project (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files), | 119 | build system (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files), |
120 | this document avoids using the term "package" when referring to recipes. | 120 | this document avoids using the term "package" when referring to recipes. |
121 | </para> | 121 | </para> |
122 | </section> | 122 | </section> |
@@ -143,7 +143,7 @@ | |||
143 | These files fall into several areas that define machine configuration options, | 143 | These files fall into several areas that define machine configuration options, |
144 | distribution configuration options, compiler tuning options, general common configuration | 144 | distribution configuration options, compiler tuning options, general common configuration |
145 | options and user configuration options (<filename>local.conf</filename>, which is found | 145 | options and user configuration options (<filename>local.conf</filename>, which is found |
146 | in the Yocto Project files build directory). | 146 | in the <ulink url='build-directory'>build directory</ulink>). |
147 | </para> | 147 | </para> |
148 | </section> | 148 | </section> |
149 | </section> | 149 | </section> |
@@ -171,7 +171,7 @@ | |||
171 | <para> | 171 | <para> |
172 | The Yocto Project implements shared state code that supports incremental builds. | 172 | The Yocto Project implements shared state code that supports incremental builds. |
173 | The implementation of the shared state code answers the following questions that | 173 | The implementation of the shared state code answers the following questions that |
174 | were fundamental roadblocks within the Yocto Project incremental build support system: | 174 | were fundamental roadblocks within the OpenEmbedded incremental build support system: |
175 | <itemizedlist> | 175 | <itemizedlist> |
176 | <listitem>What pieces of the system have changed and what pieces have not changed?</listitem> | 176 | <listitem>What pieces of the system have changed and what pieces have not changed?</listitem> |
177 | <listitem>How are changed pieces of software removed and replaced?</listitem> | 177 | <listitem>How are changed pieces of software removed and replaced?</listitem> |
@@ -485,7 +485,7 @@ | |||
485 | <title>Tips and Tricks</title> | 485 | <title>Tips and Tricks</title> |
486 | 486 | ||
487 | <para> | 487 | <para> |
488 | The code in the Yocto Project that supports incremental builds is not | 488 | The code in the build system that supports incremental builds is not |
489 | simple code. | 489 | simple code. |
490 | This section presents some tips and tricks that help you work around | 490 | This section presents some tips and tricks that help you work around |
491 | issues related to shared state code. | 491 | issues related to shared state code. |
@@ -691,10 +691,10 @@ | |||
691 | <title>Tracking License Changes</title> | 691 | <title>Tracking License Changes</title> |
692 | 692 | ||
693 | <para> | 693 | <para> |
694 | The license of an upstream project might change in the future. In order to prevent these changes | 694 | The license of an upstream project might change in the future. |
695 | going unnoticed, the Yocto Project provides a | 695 | In order to prevent these changes going unnoticed, the |
696 | <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename> | 696 | <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename> |
697 | variable to track changes to the license text. The checksums are validated at the end of the | 697 | variable tracks changes to the license text. The checksums are validated at the end of the |
698 | configure step, and if the checksums do not match, the build will fail. | 698 | configure step, and if the checksums do not match, the build will fail. |
699 | </para> | 699 | </para> |
700 | 700 | ||
@@ -714,7 +714,7 @@ | |||
714 | </para> | 714 | </para> |
715 | 715 | ||
716 | <para> | 716 | <para> |
717 | The Yocto Project uses the | 717 | The build system uses the |
718 | <filename><link linkend='var-S'>S</link></filename> variable as the | 718 | <filename><link linkend='var-S'>S</link></filename> variable as the |
719 | default directory used when searching files listed in | 719 | default directory used when searching files listed in |
720 | <filename>LIC_FILES_CHKSUM</filename>. | 720 | <filename>LIC_FILES_CHKSUM</filename>. |