diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-10-03 06:14:08 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-10-04 14:08:16 +0100 |
commit | 81ce4a9015d5f06c23f807860c3a95dbf9448d69 (patch) | |
tree | e3e5d2a5b0506c7b154e67f2ff747aced07ba282 /documentation/bsp-guide/bsp.xml | |
parent | 1eb01b66614912aa8fad63349953c3a7da6da4cc (diff) | |
download | openembedded-core-contrib-81ce4a9015d5f06c23f807860c3a95dbf9448d69.tar.gz |
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>
Diffstat (limited to 'documentation/bsp-guide/bsp.xml')
-rw-r--r-- | documentation/bsp-guide/bsp.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 91b1be0640..3cb65c21e7 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -388,7 +388,7 @@ <para> Tuning files are found in the <filename>meta/conf/machine/include</filename> 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. For example, the <filename>ia32-base.inc</filename> file resides in the <filename>meta-intel</filename> BSP Layer in <filename>conf/machine/include</filename>. @@ -440,7 +440,7 @@ formfactor recipe <filename>meta/recipes-bsp/formfactor/formfactor_0.0.bb</filename>, 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> </section> @@ -485,7 +485,7 @@ </para> <para> 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>. 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. @@ -557,7 +557,7 @@ to ensure the build process uses the <filename>standard/default/crownbay</filename> kernel branch. 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 exact kernel needed to build the Crown Bay BSP. </para> @@ -706,7 +706,7 @@ <filename>recipe-*</filename> subdirectory. You can find <filename>recipes.txt</filename> in 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 (<filename>openembedded-core</filename>) found at <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 should match what is found in the OpenEmbedded Core 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 related <filename>recipes-*</filename> subdirectories specific to the recipe's function, or within a subdirectory containing a set of closely-related @@ -1017,8 +1017,8 @@ <para> 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> - tools. + as provides details for the + <filename>yocto-bsp</filename> and <filename>yocto-kernel</filename> tools. </para> <section id='common-features'> @@ -1037,7 +1037,7 @@ <para> 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 environment just as you would when invoking a build: <literallayout class='monospaced'> |