dev-manual: Reword for when to use BBMASK.
Changed the wording on when a user would consider using the BBMASK variable. It is more suited for excluding things that cause problems rather than for speeding up build time. Reporte-by: Paul Eggleton <paul.eggleton@linux.com> (From yocto-docs rev: 993d7c953a37747297238cd9af53a1f00e737df9) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
9114dfcbe8
commit
33f2c1a0ae
|
@ -3004,9 +3004,11 @@
|
|||
<para>
|
||||
You might find that there are groups of recipes or append files
|
||||
that you want to filter out of the build process.
|
||||
For example, recipes you know you will never use or want should not
|
||||
be part of the build.
|
||||
Removing these files from parsing speeds up parts of the build.
|
||||
Usually, this is not necessary.
|
||||
However, on rare occasions where you might want to use a
|
||||
layer but exclude parts that are causing problems, such
|
||||
as introducing a different version of a recipe, you can
|
||||
use <filename>BBMASK</filename> to exclude the recipe.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
Loading…
Reference in New Issue