summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-10-22 16:59:12 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-22 23:03:16 (GMT)
commitb1c27ead60765c5ae66257e34ed3f80b8c68e9ed (patch)
treedd7d93518ecc4c8f1578d14b710ff7fec2e214c3
parent504c22b9c917b28110c7db23f400c7bafe1815c9 (diff)
downloadpoky-b1c27ead60765c5ae66257e34ed3f80b8c68e9ed.tar.gz
documentation: dev-manual - fixed capitalization on Source Directory.
(From yocto-docs rev: 8cfbd4eb519b2b966626c9a1ffd8515c198c2abd) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml28
1 files changed, 14 insertions, 14 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 2f73e28..20742ad 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -46,10 +46,10 @@
46 <title>Layers</title> 46 <title>Layers</title>
47 47
48 <para> 48 <para>
49 The source directory contains several layers right out of the box. 49 The Source Directory contains several layers right out of the box.
50 You can easily identify a layer in the source directory by its folder name. 50 You can easily identify a layer in the Source Directory by its folder name.
51 Folders that are layers begin with the string <filename>meta</filename>. 51 Folders that are layers begin with the string <filename>meta</filename>.
52 For example, when you set up the <link linkend='source-directory'>source directory</link> 52 For example, when you set up the <link linkend='source-directory'>Source Directory</link>
53 structure, you will see several layers: <filename>meta</filename>, 53 structure, you will see several layers: <filename>meta</filename>,
54 <filename>meta-hob</filename>, <filename>meta-skeleton</filename>, 54 <filename>meta-hob</filename>, <filename>meta-skeleton</filename>,
55 <filename>meta-yocto</filename>, and <filename>meta-yocto-bsp</filename>. 55 <filename>meta-yocto</filename>, and <filename>meta-yocto-bsp</filename>.
@@ -174,14 +174,14 @@
174 If this is the case, you need to address that deficiency instead of overlaying 174 If this is the case, you need to address that deficiency instead of overlaying
175 the include file. 175 the include file.
176 For example, consider how Qt 4 database support plug-ins are configured. 176 For example, consider how Qt 4 database support plug-ins are configured.
177 The source directory does not have 177 The Source Directory does not have
178 MySQL or PostgreSQL, however OpenEmbedded's 178 MySQL or PostgreSQL, however OpenEmbedded's
179 layer <filename>meta-oe</filename> does. 179 layer <filename>meta-oe</filename> does.
180 Consequently, <filename>meta-oe</filename> uses <filename>.bbappend</filename> 180 Consequently, <filename>meta-oe</filename> uses <filename>.bbappend</filename>
181 files to modify the <filename>QT_SQL_DRIVER_FLAGS</filename> variable to enable 181 files to modify the <filename>QT_SQL_DRIVER_FLAGS</filename> variable to enable
182 the appropriate plugins. 182 the appropriate plugins.
183 This variable was added to the <filename>qt4.inc</filename> include file in 183 This variable was added to the <filename>qt4.inc</filename> include file in
184 the source directory specifically to allow the <filename>meta-oe</filename> layer 184 the Source Directory specifically to allow the <filename>meta-oe</filename> layer
185 to be able to control which plugins are built.</para></listitem> 185 to be able to control which plugins are built.</para></listitem>
186 </itemizedlist> 186 </itemizedlist>
187 </para> 187 </para>
@@ -193,9 +193,9 @@
193 <filename>meta-&lt;layer_name&gt;</filename> format.</para></listitem> 193 <filename>meta-&lt;layer_name&gt;</filename> format.</para></listitem>
194 <listitem><para>Clone the repository alongside other <filename>meta</filename> 194 <listitem><para>Clone the repository alongside other <filename>meta</filename>
195 directories in the 195 directories in the
196 <link linkend='source-directory'>source directory</link>.</para></listitem> 196 <link linkend='source-directory'>Source Directory</link>.</para></listitem>
197 </itemizedlist> 197 </itemizedlist>
198 Following these recommendations keeps your source directory and 198 Following these recommendations keeps your Source Directory and
199 its configuration entirely inside the Yocto Project's core base. 199 its configuration entirely inside the Yocto Project's core base.
200 </para> 200 </para>
201 </section> 201 </section>
@@ -283,7 +283,7 @@
283 <para> 283 <para>
284 As an example, consider the main formfactor recipe and a corresponding formfactor 284 As an example, consider the main formfactor recipe and a corresponding formfactor
285 append file both from the 285 append file both from the
286 <link linkend='source-directory'>source directory</link>. 286 <link linkend='source-directory'>Source Directory</link>.
287 Here is the main formfactor recipe, which is named <filename>formfactor_0.0.bb</filename> and 287 Here is the main formfactor recipe, which is named <filename>formfactor_0.0.bb</filename> and
288 located in the meta layer at <filename>meta/recipes-bsp/formfactor</filename>: 288 located in the meta layer at <filename>meta/recipes-bsp/formfactor</filename>:
289 <literallayout class='monospaced'> 289 <literallayout class='monospaced'>
@@ -580,7 +580,7 @@
580 with specialized image <filename>.bb</filename> files. 580 with specialized image <filename>.bb</filename> files.
581 You can also add more features by configuring the 581 You can also add more features by configuring the
582 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-EXTRA_IMAGE_FEATURES'>EXTRA_IMAGE_FEATURES</ulink></filename> 582 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-EXTRA_IMAGE_FEATURES'>EXTRA_IMAGE_FEATURES</ulink></filename>
583 variable in the <filename>local.conf</filename> file found in the source directory 583 variable in the <filename>local.conf</filename> file found in the Source Directory
584 located in the build directory. 584 located in the build directory.
585 </para> 585 </para>
586 586
@@ -1083,7 +1083,7 @@
1083 You need to either create a new kernel recipe for this machine, or extend an 1083 You need to either create a new kernel recipe for this machine, or extend an
1084 existing recipe. 1084 existing recipe.
1085 You can find several kernel examples in the 1085 You can find several kernel examples in the
1086 source directory at <filename>meta/recipes-kernel/linux</filename> 1086 Source Directory at <filename>meta/recipes-kernel/linux</filename>
1087 that you can use as references. 1087 that you can use as references.
1088 </para> 1088 </para>
1089 1089
@@ -1206,7 +1206,7 @@
1206 extended to support multiple libraries. 1206 extended to support multiple libraries.
1207 Many standard recipes are already extended and support multiple libraries. 1207 Many standard recipes are already extended and support multiple libraries.
1208 You can check in the <filename>meta/conf/multilib.conf</filename> 1208 You can check in the <filename>meta/conf/multilib.conf</filename>
1209 configuration file in the source directory to see how this is 1209 configuration file in the Source Directory to see how this is
1210 done using the 1210 done using the
1211 <ulink url='&YOCTO_DOCS_REF_URL;#var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></ulink> 1211 <ulink url='&YOCTO_DOCS_REF_URL;#var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></ulink>
1212 variable. 1212 variable.
@@ -1365,7 +1365,7 @@
1365 script found in the 1365 script found in the
1366 <link linkend='build-directory'>Build Directory</link>. 1366 <link linkend='build-directory'>Build Directory</link>.
1367 The following commands build and invoke <filename>menuconfig</filename> assuming the 1367 The following commands build and invoke <filename>menuconfig</filename> assuming the
1368 source directory top-level folder is <filename>~/poky</filename>: 1368 Source Directory top-level folder is <filename>~/poky</filename>:
1369 <literallayout class='monospaced'> 1369 <literallayout class='monospaced'>
1370 $ cd ~/poky 1370 $ cd ~/poky
1371 $ source oe-init-build-env 1371 $ source oe-init-build-env
@@ -2013,7 +2013,7 @@
2013 $ bitbake world -f -c distro_check 2013 $ bitbake world -f -c distro_check
2014 </literallayout> 2014 </literallayout>
2015 The results are stored in the <filename>build/tmp/log/distro_check-${DATETIME}.results</filename> 2015 The results are stored in the <filename>build/tmp/log/distro_check-${DATETIME}.results</filename>
2016 file found in the source directory. 2016 file found in the Source Directory.
2017 </para> 2017 </para>
2018 </section> 2018 </section>
2019 2019
@@ -2029,7 +2029,7 @@
2029 2029
2030 <para> 2030 <para>
2031 Situations exist where you might want to build software from source files that are external to 2031 Situations exist where you might want to build software from source files that are external to
2032 and thus outside of the <link linkend='source-directory'>source directory</link>. 2032 and thus outside of the <link linkend='source-directory'>Source Directory</link>.
2033 For example, suppose you have a project that includes a new BSP with a heavily customized 2033 For example, suppose you have a project that includes a new BSP with a heavily customized
2034 kernel, a very minimal image, and some new user-space recipes. 2034 kernel, a very minimal image, and some new user-space recipes.
2035 And, you want to minimize exposing the build system to the 2035 And, you want to minimize exposing the build system to the