sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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>
This commit is contained in:
Scott Rifenbark 2012-10-01 12:09:23 -07:00 committed by Richard Purdie
parent 5fd5ef78c4
commit e6ed2118fc
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
documentation/dev-manual/dev-manual-bsp-appendix.xml
View File

@ -26,7 +26,7 @@
<title>Getting Local Source Files and BSP Files</title>
<para>
You need to have the <link linkend='source-directory'>source directory</link>
You need to have the <link linkend='source-directory'>Source Directory</link>
available on your host system.
You can set up this directory through tarball extraction or by cloning the
<filename>poky</filename> Git repository.
@ -36,7 +36,7 @@
</para>
<para>
As mentioned, one way to set up the source directory is to use Git to clone the
As mentioned, one way to set up the Source Directory is to use Git to clone the
<filename>poky</filename> repository.
These commands create a local copy of the Git repository.
By default, the top-level directory of the repository is named <filename>poky</filename>:
@ -45,8 +45,8 @@
$ cd poky
</literallayout>
Alternatively, you can start with the downloaded Poky "&DISTRO_NAME;" tarball.
These commands unpack the tarball into a source directory structure.
By default, the top-level directory of the source directory is named
These commands unpack the tarball into a Source Directory structure.
By default, the top-level directory of the Source Directory is named
<filename>&YOCTO_POKY;</filename>:
<literallayout class='monospaced'>
$ tar xfj &YOCTO_POKY_TARBALL;
@ -133,12 +133,12 @@
<para>
You need to have the base BSP layer on your development system.
Similar to the local <link linkend='source-directory'>source directory</link>,
Similar to the local <link linkend='source-directory'>Source Directory</link>,
you can get the BSP
layer in a couple of different ways:
download the BSP tarball and extract it, or set up a local Git repository that
has the BSP layers.
You should use the same method that you used to set up the source directory earlier.
You should use the same method that you used to set up the Source Directory earlier.
See "<link linkend='getting-setup'>Getting Setup</link>" for information on how to get
the BSP files.
</para>
@ -196,7 +196,7 @@
<title>Making a Copy of the Base BSP to Create Your New BSP Layer</title>
<para>
Now that you have set up the source directory and included the base BSP files, you need to
Now that you have set up the Source Directory and included the base BSP files, you need to
create a new layer for your BSP.
To create your BSP layer, you simply copy the <filename>meta-crownbay</filename>
layer to a new layer.
@ -207,7 +207,7 @@
The name should follow the BSP layer naming convention, which is
<filename>meta-&lt;name&gt;</filename>.
The following assumes your working directory is <filename>meta-intel</filename>
inside your source directory.
inside your Source Directory.
To start your new layer, just copy the new layer alongside the existing
BSP layers in the <filename>meta-intel</filename> directory:
<literallayout class='monospaced'>
@ -366,7 +366,7 @@
Recall that the BSP uses the <filename>linux-yocto</filename> kernel as determined
earlier in the <filename>mymachine.conf</filename>.
The recipe for that kernel is not located in the
BSP layer but rather in the source directory at
BSP layer but rather in the Source Directory at
<filename>meta/recipes-kernel/linux</filename> and is
named <filename>linux-yocto_3.2.bb</filename>.
The <filename>SRCREV_machine</filename> and <filename>SRCREV_meta</filename>
@ -549,7 +549,7 @@
<orderedlist>
<listitem><para>Get the environment ready for the build by sourcing the environment
script.
The environment script is in the top-level of the source directory.
The environment script is in the top-level of the Source Directory.
The script has the string
<filename>init-build-env</filename> in the file’s name.
For this example, the following command gets the build environment ready: