ref-manual: Rewrite of the CLASSOVERRIDE variable in the glossary
Fixes [YOCTO #10174] I applied a more descriptive explanation of this varialbe. (From yocto-docs rev: 7c6c2645b7e74e1c7de0d43b35307c8917648959) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
43b9962cdd
commit
44b0b07a6f
|
@ -1992,22 +1992,35 @@
|
||||||
An internal variable specifying the special class override
|
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).
|
"class-native", and so forth).
|
||||||
The classes that use this variable set it to
|
The classes that use this variable (e.g.
|
||||||
appropriate values.
|
<link linkend='ref-classes-native'><filename>native</filename></link>,
|
||||||
|
<link linkend='ref-classes-nativesdk'><filename>nativesdk</filename></link>,
|
||||||
|
and so forth) set the variable to appropriate values.
|
||||||
|
<note>
|
||||||
|
<filename>CLASSOVERRIDE</filename> gets its default
|
||||||
|
"class-target" value from the
|
||||||
|
<filename>bitbake.conf</filename> file.
|
||||||
|
</note>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
You do not normally directly interact with this variable.
|
As an example, the following override allows you to install
|
||||||
The value for the <filename>CLASSOVERRIDE</filename>
|
extra files, but only when building for the target:
|
||||||
variable goes into
|
<literallayout class='monospaced'>
|
||||||
<link linkend='var-OVERRIDES'><filename>OVERRIDES</filename></link>
|
do_install_append_class-target() {
|
||||||
and then can be used as an override.
|
install my-extra-file ${D}${sysconfdir}
|
||||||
|
}
|
||||||
|
</literallayout>
|
||||||
Here is an example where "python-native" is added to
|
Here is an example where "python-native" is added to
|
||||||
<link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
|
<link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>,
|
||||||
only when building for the <filename>-native</filename> case:
|
but only when building for the build host:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
DEPENDS_append_class-native = " python-native"
|
DEPENDS_append_class-native = " python-native"
|
||||||
</literallayout>
|
</literallayout>
|
||||||
|
The underlying mechanism behind
|
||||||
|
<filename>CLASSOVERRIDE</filename> is simply that it is
|
||||||
|
included in the default value of
|
||||||
|
<link linkend='var-OVERRIDES'><filename>OVERRIDES</filename></link>.
|
||||||
</para>
|
</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
</glossentry>
|
</glossentry>
|
||||||
|
|
Loading…
Reference in New Issue