bitbake: bitbake-user-manual: Added review changes to BBCLASSEXTEND description

Fixes [YOCTO #9909]

Added some technical clarifications to the existing note to be clear
about what is causing the limitations in this case.  Applied some
formatting fixed to for the use of the include word.

(Bitbake rev: e9ad2e0f6d2681dd793cc39c468eb86e57fd6f48)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-07-14 12:52:30 -07:00 committed by Richard Purdie
parent 4bc1ee5de4
commit 9a9577ed49
1 changed files with 9 additions and 7 deletions

View File

@ -992,19 +992,21 @@
mechanism generates recipe variants by rewriting mechanism generates recipe variants by rewriting
variable values and applying overrides such as variable values and applying overrides such as
<filename>_class-native</filename>. <filename>_class-native</filename>.
For example, to generate a native version of a recipe For example, to generate a native version of a recipe,
named "foo", a a
<link linkend='var-DEPENDS'><filename>DEPENDS</filename></link> <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
on "foo" is rewritten to a <filename>DEPENDS</filename> on "foo" is rewritten to a <filename>DEPENDS</filename>
on "foo-native". on "foo-native".
</para> </para>
<para> <para>
No reparsing, which adds some limitations, of the Even when using <filename>BBCLASSEXTEND</filename>, the
recipe is done for each variant. recipe is only parsed once.
For example, it is not possible to "include" a Parsing once adds some limitations.
different file depending on the variant, since For example, it is not possible to
"include's" are processed when the recipe is parsed. include a different file depending on the variant,
since <filename>include</filename> statements are
processed when the recipe is parsed.
</para> </para>
</note> </note>
</para> </para>