aboutsummaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-07-12 14:10:13 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-07-19 15:04:51 +0100
commit640181cce81663b0a2055592382d127eac5d63ba (patch)
tree213332d2d8a871a48ecf8e636ccf22b46d6dde56 /documentation
parent48336f5139a6d6ff43cb371f7831817cecec0ae9 (diff)
downloadopenembedded-core-contrib-640181cce81663b0a2055592382d127eac5d63ba.tar.gz
ref-manual: Added clarifying note to the BBCLASSEXTEND variable.
Fixes [YOCTO #9909] Added a note that talks about how the BBCLASSEXTEND mechanism adds recipe variants. (From yocto-docs rev: a05990ecb760519a685a1c5ddcf2ce3e048bfbf2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/ref-manual/ref-variables.xml21
1 files changed, 21 insertions, 0 deletions
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 3278ccc27e..b876bc3115 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -995,6 +995,27 @@
BBCLASSEXTEND =+ "native nativesdk"
BBCLASSEXTEND =+ "multilib:<replaceable>multilib_name</replaceable>"
</literallayout>
+ <note>
+ <para>
+ Internally, the <filename>BBCLASSEXTEND</filename>
+ mechanism generates recipe variants by rewriting
+ variable values and applying overrides such as
+ <filename>_class-native</filename>.
+ For example, to generate a native version of a recipe
+ named "foo", a
+ <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
+ on "foo" is rewritten to a <filename>DEPENDS</filename>
+ on "foo-native".
+ </para>
+
+ <para>
+ No reparsing, which adds some limitations, of the
+ recipe is done for each variant.
+ For example, it is not possible to "include" a
+ different file depending on the variant, since
+ "include's" are processed when the recipe is parsed.
+ </para>
+ </note>
</para>
</glossdef>
</glossentry>