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

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>
This commit is contained in:
Scott Rifenbark 2012-10-22 09:59:12 -07:00 committed by Richard Purdie
parent 9137117b3f
commit 3374926849
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -46,10 +46,10 @@
<title>Layers</title> <title>Layers</title>
<para> <para>
The source directory contains several layers right out of the box. The Source Directory contains several layers right out of the box.
You can easily identify a layer in the source directory by its folder name. You can easily identify a layer in the Source Directory by its folder name.
Folders that are layers begin with the string <filename>meta</filename>. Folders that are layers begin with the string <filename>meta</filename>.
For example, when you set up the <link linkend='source-directory'>source directory</link> For example, when you set up the <link linkend='source-directory'>Source Directory</link>
structure, you will see several layers: <filename>meta</filename>, structure, you will see several layers: <filename>meta</filename>,
<filename>meta-hob</filename>, <filename>meta-skeleton</filename>, <filename>meta-hob</filename>, <filename>meta-skeleton</filename>,
<filename>meta-yocto</filename>, and <filename>meta-yocto-bsp</filename>. <filename>meta-yocto</filename>, and <filename>meta-yocto-bsp</filename>.
@ -174,14 +174,14 @@
If this is the case, you need to address that deficiency instead of overlaying If this is the case, you need to address that deficiency instead of overlaying
the include file. the include file.
For example, consider how Qt 4 database support plug-ins are configured. For example, consider how Qt 4 database support plug-ins are configured.
The source directory does not have The Source Directory does not have
MySQL or PostgreSQL, however OpenEmbedded's MySQL or PostgreSQL, however OpenEmbedded's
layer <filename>meta-oe</filename> does. layer <filename>meta-oe</filename> does.
Consequently, <filename>meta-oe</filename> uses <filename>.bbappend</filename> Consequently, <filename>meta-oe</filename> uses <filename>.bbappend</filename>
files to modify the <filename>QT_SQL_DRIVER_FLAGS</filename> variable to enable files to modify the <filename>QT_SQL_DRIVER_FLAGS</filename> variable to enable
the appropriate plugins. the appropriate plugins.
This variable was added to the <filename>qt4.inc</filename> include file in This variable was added to the <filename>qt4.inc</filename> include file in
the source directory specifically to allow the <filename>meta-oe</filename> layer the Source Directory specifically to allow the <filename>meta-oe</filename> layer
to be able to control which plugins are built.</para></listitem> to be able to control which plugins are built.</para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>
@ -193,9 +193,9 @@
<filename>meta-&lt;layer_name&gt;</filename> format.</para></listitem> <filename>meta-&lt;layer_name&gt;</filename> format.</para></listitem>
<listitem><para>Clone the repository alongside other <filename>meta</filename> <listitem><para>Clone the repository alongside other <filename>meta</filename>
directories in the directories in the
<link linkend='source-directory'>source directory</link>.</para></listitem> <link linkend='source-directory'>Source Directory</link>.</para></listitem>
</itemizedlist> </itemizedlist>
Following these recommendations keeps your source directory and Following these recommendations keeps your Source Directory and
its configuration entirely inside the Yocto Project's core base. its configuration entirely inside the Yocto Project's core base.
</para> </para>
</section> </section>
@ -283,7 +283,7 @@
<para> <para>
As an example, consider the main formfactor recipe and a corresponding formfactor As an example, consider the main formfactor recipe and a corresponding formfactor
append file both from the append file both from the
<link linkend='source-directory'>source directory</link>. <link linkend='source-directory'>Source Directory</link>.
Here is the main formfactor recipe, which is named <filename>formfactor_0.0.bb</filename> and Here is the main formfactor recipe, which is named <filename>formfactor_0.0.bb</filename> and
located in the meta layer at <filename>meta/recipes-bsp/formfactor</filename>: located in the meta layer at <filename>meta/recipes-bsp/formfactor</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
@ -580,7 +580,7 @@
with specialized image <filename>.bb</filename> files. with specialized image <filename>.bb</filename> files.
You can also add more features by configuring the You can also add more features by configuring the
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-EXTRA_IMAGE_FEATURES'>EXTRA_IMAGE_FEATURES</ulink></filename> <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-EXTRA_IMAGE_FEATURES'>EXTRA_IMAGE_FEATURES</ulink></filename>
variable in the <filename>local.conf</filename> file found in the source directory variable in the <filename>local.conf</filename> file found in the Source Directory
located in the build directory. located in the build directory.
</para> </para>
@ -1083,7 +1083,7 @@
You need to either create a new kernel recipe for this machine, or extend an You need to either create a new kernel recipe for this machine, or extend an
existing recipe. existing recipe.
You can find several kernel examples in the You can find several kernel examples in the
source directory at <filename>meta/recipes-kernel/linux</filename> Source Directory at <filename>meta/recipes-kernel/linux</filename>
that you can use as references. that you can use as references.
</para> </para>
@ -1206,7 +1206,7 @@
extended to support multiple libraries. extended to support multiple libraries.
Many standard recipes are already extended and support multiple libraries. Many standard recipes are already extended and support multiple libraries.
You can check in the <filename>meta/conf/multilib.conf</filename> You can check in the <filename>meta/conf/multilib.conf</filename>
configuration file in the source directory to see how this is configuration file in the Source Directory to see how this is
done using the done using the
<ulink url='&YOCTO_DOCS_REF_URL;#var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></ulink>
variable. variable.
@ -1365,7 +1365,7 @@
script found in the script found in the
<link linkend='build-directory'>Build Directory</link>. <link linkend='build-directory'>Build Directory</link>.
The following commands build and invoke <filename>menuconfig</filename> assuming the The following commands build and invoke <filename>menuconfig</filename> assuming the
source directory top-level folder is <filename>~/poky</filename>: Source Directory top-level folder is <filename>~/poky</filename>:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ cd ~/poky $ cd ~/poky
$ source oe-init-build-env $ source oe-init-build-env
@ -2013,7 +2013,7 @@
$ bitbake world -f -c distro_check $ bitbake world -f -c distro_check
</literallayout> </literallayout>
The results are stored in the <filename>build/tmp/log/distro_check-${DATETIME}.results</filename> The results are stored in the <filename>build/tmp/log/distro_check-${DATETIME}.results</filename>
file found in the source directory. file found in the Source Directory.
</para> </para>
</section> </section>
@ -2029,7 +2029,7 @@
<para> <para>
Situations exist where you might want to build software from source files that are external to Situations exist where you might want to build software from source files that are external to
and thus outside of the <link linkend='source-directory'>source directory</link>. and thus outside of the <link linkend='source-directory'>Source Directory</link>.
For example, suppose you have a project that includes a new BSP with a heavily customized For example, suppose you have a project that includes a new BSP with a heavily customized
kernel, a very minimal image, and some new user-space recipes. kernel, a very minimal image, and some new user-space recipes.
And, you want to minimize exposing the build system to the And, you want to minimize exposing the build system to the