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

documentation: bsp-guide - Changed Source Directory capitalization. 

The term should be initially capitalized.

(From yocto-docs rev: 38a11d512bfe675319fb76da9d7618315af91c47)

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-03 06:14:08 -07:00 committed by Richard Purdie
parent 1eb01b6661
commit 81ce4a9015
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
documentation/bsp-guide/bsp.xml
View File

@ -388,7 +388,7 @@
<para> <para>
Tuning files are found in the <filename>meta/conf/machine/include</filename> Tuning files are found in the <filename>meta/conf/machine/include</filename>
directory within the directory within the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
Tuning files can also reside in the BSP Layer itself. Tuning files can also reside in the BSP Layer itself.
For example, the <filename>ia32-base.inc</filename> file resides in the For example, the <filename>ia32-base.inc</filename> file resides in the
<filename>meta-intel</filename> BSP Layer in <filename>conf/machine/include</filename>. <filename>meta-intel</filename> BSP Layer in <filename>conf/machine/include</filename>.
@ -440,7 +440,7 @@
formfactor recipe formfactor recipe
<filename>meta/recipes-bsp/formfactor/formfactor_0.0.bb</filename>, <filename>meta/recipes-bsp/formfactor/formfactor_0.0.bb</filename>,
which is found in the which is found in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
</para></note> </para></note>
</section> </section>
@ -485,7 +485,7 @@
</para> </para>
<para> <para>
For your BSP, you typically want to use an existing Yocto Project kernel recipe found in the For your BSP, you typically want to use an existing Yocto Project kernel recipe found in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink> <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
at <filename>meta/recipes-kernel/linux</filename>. at <filename>meta/recipes-kernel/linux</filename>.
You can append your specific changes to the kernel recipe by using a You can append your specific changes to the kernel recipe by using a
similarly named append file, which is located in the BSP Layer (e.g. similarly named append file, which is located in the BSP Layer (e.g.
@ -557,7 +557,7 @@
to ensure the build process uses the <filename>standard/default/crownbay</filename> to ensure the build process uses the <filename>standard/default/crownbay</filename>
kernel branch. kernel branch.
Finally, the append file points to the specific top commits in the Finally, the append file points to the specific top commits in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink> Git <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> Git
repository and the <filename>meta</filename> Git repository branches to identify the repository and the <filename>meta</filename> Git repository branches to identify the
exact kernel needed to build the Crown Bay BSP. exact kernel needed to build the Crown Bay BSP.
</para> </para>
@ -706,7 +706,7 @@
<filename>recipe-*</filename> subdirectory. <filename>recipe-*</filename> subdirectory.
You can find <filename>recipes.txt</filename> in the You can find <filename>recipes.txt</filename> in the
<filename>meta</filename> directory of the <filename>meta</filename> directory of the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>, <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
or in the OpenEmbedded Core Layer or in the OpenEmbedded Core Layer
(<filename>openembedded-core</filename>) found at (<filename>openembedded-core</filename>) found at
<ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>. <ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>.
@ -714,7 +714,7 @@
<para>Within any particular <filename>recipes-*</filename> category, the layout <para>Within any particular <filename>recipes-*</filename> category, the layout
should match what is found in the OpenEmbedded Core should match what is found in the OpenEmbedded Core
Git repository (<filename>openembedded-core</filename>) Git repository (<filename>openembedded-core</filename>)
or the source directory (<filename>poky</filename>). or the Source Directory (<filename>poky</filename>).
In other words, make sure you place related files in appropriately In other words, make sure you place related files in appropriately
related <filename>recipes-*</filename> subdirectories specific to the related <filename>recipes-*</filename> subdirectories specific to the
recipe's function, or within a subdirectory containing a set of closely-related recipe's function, or within a subdirectory containing a set of closely-related
@ -1017,8 +1017,8 @@
<para> <para>
The following sections describe the common location and help features as well The following sections describe the common location and help features as well
as details for the <filename>yocto-bsp</filename> and <filename>yocto-kernel</filename> as provides details for the
tools. <filename>yocto-bsp</filename> and <filename>yocto-kernel</filename> tools.
</para> </para>
<section id='common-features'> <section id='common-features'>
@ -1037,7 +1037,7 @@
<para> <para>
Both tools reside in the <filename>scripts/</filename> subdirectory Both tools reside in the <filename>scripts/</filename> subdirectory
of the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. of the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
Consequently, to use the scripts, you must <filename>source</filename> the Consequently, to use the scripts, you must <filename>source</filename> the
environment just as you would when invoking a build: environment just as you would when invoking a build:
<literallayout class='monospaced'> <literallayout class='monospaced'>