documentation/poky-ref-manual: Review edits on B and externalsrc.bbclass

I tried to implement some comments by Richard on the B glossary
entry and the externalsrc.bbclass section.  The comments were a bit
confusing to me but the gist of it was I mis-interpreted Richard's
comments on supporting separate directories for B and S.  I had
indicated that autotools-based recipes did this by default, which
was wrong.  What was confusing to me is where the comments should
be.  I ended up putting them in both areas of the reference manual.

(From yocto-docs rev: a2ddc17bd003b116e593f7df0f59d86cfa0e1cd9)

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 2012-03-01 11:08:50 -06:00 committed by Richard Purdie
parent e95d81a8bf
commit 7018654853
2 changed files with 6 additions and 2 deletions

View File

@ -567,6 +567,9 @@
<link linkend='var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></link> variable.
When you do, the <link linkend='var-B'><filename>B</filename></link> variable must support the
recipe's ability to build variants in different working directories.
Most autotools-based recipes support separating these directories.
The Yocto Project defaults to using separate directories for <filename>gcc</filename>
and some kernel recipes.
Alternatively, you can make sure that separate recipes exist that each
use the <filename>BBCLASSEXTEND</filename> variable to build each variant.
The separate recipes can inherit a single target recipe.

View File

@ -76,8 +76,9 @@
</literallayout>
You can separate the source directory (<filename>S</filename>) and the directory pointed to
by the <filename>B</filename> variable.
In general, <filename>autotools</filename>, recipes such as <filename>gcc</filename>,
and some kernel recipes separate these directories by default.
Most autotools-based recipes support separating these directories.
The Yocto Project defaults to using separate directories for <filename>gcc</filename>
and some kernel recipes.
</para>
</glossdef>
</glossentry>