diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-10-01 12:09:23 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-10-02 17:41:34 +0100 |
commit | e6ed2118fcde44d9a018c7df0f73ffa839f64a51 (patch) | |
tree | db86e1de7ff5fabf513eab77f3c2e314c39ce668 /documentation/dev-manual/dev-manual-bsp-appendix.xml | |
parent | 5fd5ef78c4a0a2ebebb94cc3e325d511c80da413 (diff) | |
download | poky-e6ed2118fcde44d9a018c7df0f73ffa839f64a51.tar.gz |
documentation: dev-manual - Fixed capitalization for term.
The term "Source Directory" should be capitalized.
(From yocto-docs rev: 143213545358dd5b6c28c71202bea2e40dbb2522)
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/dev-manual-bsp-appendix.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-bsp-appendix.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml index 815414b192..0962768713 100644 --- a/documentation/dev-manual/dev-manual-bsp-appendix.xml +++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml | |||
@@ -26,7 +26,7 @@ | |||
26 | <title>Getting Local Source Files and BSP Files</title> | 26 | <title>Getting Local Source Files and BSP Files</title> |
27 | 27 | ||
28 | <para> | 28 | <para> |
29 | You need to have the <link linkend='source-directory'>source directory</link> | 29 | You need to have the <link linkend='source-directory'>Source Directory</link> |
30 | available on your host system. | 30 | available on your host system. |
31 | You can set up this directory through tarball extraction or by cloning the | 31 | You can set up this directory through tarball extraction or by cloning the |
32 | <filename>poky</filename> Git repository. | 32 | <filename>poky</filename> Git repository. |
@@ -36,7 +36,7 @@ | |||
36 | </para> | 36 | </para> |
37 | 37 | ||
38 | <para> | 38 | <para> |
39 | As mentioned, one way to set up the source directory is to use Git to clone the | 39 | As mentioned, one way to set up the Source Directory is to use Git to clone the |
40 | <filename>poky</filename> repository. | 40 | <filename>poky</filename> repository. |
41 | These commands create a local copy of the Git repository. | 41 | These commands create a local copy of the Git repository. |
42 | By default, the top-level directory of the repository is named <filename>poky</filename>: | 42 | By default, the top-level directory of the repository is named <filename>poky</filename>: |
@@ -45,8 +45,8 @@ | |||
45 | $ cd poky | 45 | $ cd poky |
46 | </literallayout> | 46 | </literallayout> |
47 | Alternatively, you can start with the downloaded Poky "&DISTRO_NAME;" tarball. | 47 | Alternatively, you can start with the downloaded Poky "&DISTRO_NAME;" tarball. |
48 | These commands unpack the tarball into a source directory structure. | 48 | These commands unpack the tarball into a Source Directory structure. |
49 | By default, the top-level directory of the source directory is named | 49 | By default, the top-level directory of the Source Directory is named |
50 | <filename>&YOCTO_POKY;</filename>: | 50 | <filename>&YOCTO_POKY;</filename>: |
51 | <literallayout class='monospaced'> | 51 | <literallayout class='monospaced'> |
52 | $ tar xfj &YOCTO_POKY_TARBALL; | 52 | $ tar xfj &YOCTO_POKY_TARBALL; |
@@ -133,12 +133,12 @@ | |||
133 | 133 | ||
134 | <para> | 134 | <para> |
135 | You need to have the base BSP layer on your development system. | 135 | You need to have the base BSP layer on your development system. |
136 | Similar to the local <link linkend='source-directory'>source directory</link>, | 136 | Similar to the local <link linkend='source-directory'>Source Directory</link>, |
137 | you can get the BSP | 137 | you can get the BSP |
138 | layer in a couple of different ways: | 138 | layer in a couple of different ways: |
139 | download the BSP tarball and extract it, or set up a local Git repository that | 139 | download the BSP tarball and extract it, or set up a local Git repository that |
140 | has the BSP layers. | 140 | has the BSP layers. |
141 | You should use the same method that you used to set up the source directory earlier. | 141 | You should use the same method that you used to set up the Source Directory earlier. |
142 | See "<link linkend='getting-setup'>Getting Setup</link>" for information on how to get | 142 | See "<link linkend='getting-setup'>Getting Setup</link>" for information on how to get |
143 | the BSP files. | 143 | the BSP files. |
144 | </para> | 144 | </para> |
@@ -196,7 +196,7 @@ | |||
196 | <title>Making a Copy of the Base BSP to Create Your New BSP Layer</title> | 196 | <title>Making a Copy of the Base BSP to Create Your New BSP Layer</title> |
197 | 197 | ||
198 | <para> | 198 | <para> |
199 | Now that you have set up the source directory and included the base BSP files, you need to | 199 | Now that you have set up the Source Directory and included the base BSP files, you need to |
200 | create a new layer for your BSP. | 200 | create a new layer for your BSP. |
201 | To create your BSP layer, you simply copy the <filename>meta-crownbay</filename> | 201 | To create your BSP layer, you simply copy the <filename>meta-crownbay</filename> |
202 | layer to a new layer. | 202 | layer to a new layer. |
@@ -207,7 +207,7 @@ | |||
207 | The name should follow the BSP layer naming convention, which is | 207 | The name should follow the BSP layer naming convention, which is |
208 | <filename>meta-<name></filename>. | 208 | <filename>meta-<name></filename>. |
209 | The following assumes your working directory is <filename>meta-intel</filename> | 209 | The following assumes your working directory is <filename>meta-intel</filename> |
210 | inside your source directory. | 210 | inside your Source Directory. |
211 | To start your new layer, just copy the new layer alongside the existing | 211 | To start your new layer, just copy the new layer alongside the existing |
212 | BSP layers in the <filename>meta-intel</filename> directory: | 212 | BSP layers in the <filename>meta-intel</filename> directory: |
213 | <literallayout class='monospaced'> | 213 | <literallayout class='monospaced'> |
@@ -366,7 +366,7 @@ | |||
366 | Recall that the BSP uses the <filename>linux-yocto</filename> kernel as determined | 366 | Recall that the BSP uses the <filename>linux-yocto</filename> kernel as determined |
367 | earlier in the <filename>mymachine.conf</filename>. | 367 | earlier in the <filename>mymachine.conf</filename>. |
368 | The recipe for that kernel is not located in the | 368 | The recipe for that kernel is not located in the |
369 | BSP layer but rather in the source directory at | 369 | BSP layer but rather in the Source Directory at |
370 | <filename>meta/recipes-kernel/linux</filename> and is | 370 | <filename>meta/recipes-kernel/linux</filename> and is |
371 | named <filename>linux-yocto_3.2.bb</filename>. | 371 | named <filename>linux-yocto_3.2.bb</filename>. |
372 | The <filename>SRCREV_machine</filename> and <filename>SRCREV_meta</filename> | 372 | The <filename>SRCREV_machine</filename> and <filename>SRCREV_meta</filename> |
@@ -549,7 +549,7 @@ | |||
549 | <orderedlist> | 549 | <orderedlist> |
550 | <listitem><para>Get the environment ready for the build by sourcing the environment | 550 | <listitem><para>Get the environment ready for the build by sourcing the environment |
551 | script. | 551 | script. |
552 | The environment script is in the top-level of the source directory. | 552 | The environment script is in the top-level of the Source Directory. |
553 | The script has the string | 553 | The script has the string |
554 | <filename>init-build-env</filename> in the file’s name. | 554 | <filename>init-build-env</filename> in the file’s name. |
555 | For this example, the following command gets the build environment ready: | 555 | For this example, the following command gets the build environment ready: |