[oe-commits] [bitbake] 05/13: bitbake-user-manual: Added clarifying note to BBCLASSEXTEND variable.

[git at git.openembedded.org]

rpurdie pushed a commit to branch master
in repository bitbake.

commit 185c9c5fc205fe9c9daf5238f11b92bd0954f5c6
Author: Scott Rifenbark <srifenbark at gmail.com>
AuthorDate: Tue Jul 12 14:08:32 2016 -0700

    bitbake-user-manual: Added clarifying note to BBCLASSEXTEND variable.
    
    Fixes [YOCTO #9909]
    
    Added a note that talks about how the BBCLASSEXTEND mechanism
    adds recipe variants.
    
    Signed-off-by: Scott Rifenbark <srifenbark at gmail.com>
---
 .../bitbake-user-manual-ref-variables.xml           | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
index 4d06ff9..e26422a 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
@@ -986,6 +986,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>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.