ref-manual: Expanded CLASSOVERRIDE variable example description.

(From yocto-docs rev: f78cfbd4bd06f4dbf35522f2fd4b2012de889323)

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 2013-11-19 09:44:37 -08:00 committed by Richard Purdie
parent 3cd74158dd
commit 04ee674163
1 changed files with 9 additions and 7 deletions

View File

@ -320,8 +320,8 @@
<para>
You can change the default behavior by setting this
variable to "1", "yes", or "true"
in your <filename>local.conf</filename> file, which is
variable to "1", "yes", or "true"
in your <filename>local.conf</filename> file, which is
located in the
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
Here is an example:
@ -829,7 +829,7 @@
<glossentry id='var-BUGTRACKER'><glossterm>BUGTRACKER</glossterm>
<glossdef>
<para>
Specifies a URL for an upstream bug tracking website for
Specifies a URL for an upstream bug tracking website for
a recipe.
The OpenEmbedded build system does not use this variable.
Rather, the variable is a useful pointer in case a bug
@ -893,19 +893,21 @@
<glossdef>
<para>
An internal variable specifying the special class override
that should currently apply (e.g. "class-target",
that should currently apply (e.g. "class-target",
"class-native", and so forth).
The classes that use this variable set it to
The classes that use this variable set it to
appropriate values.
</para>
<para>
You do not normally directly interact with this variable.
The value for the <filename>CLASSOVERRIDE</filename>
variable goes into
variable goes into
<link linkend='var-OVERRIDES'><filename>OVERRIDES</filename></link>
and then can be used as an override.
Here is an example:
Here is an example where "python-native" is added to
<link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
only when building for the native case:
<literallayout class='monospaced'>
DEPENDS_append_class-native = " python-native"
</literallayout>