summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2015-01-19 14:14:19 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-02-17 15:16:51 +0000
commit4ab132a20d33e70cf6736737c59d2c0ce2f79298 (patch)
tree5525f7940beb4783d345feea1ec86ec049d0bae1 /documentation/yocto-project-qs
parent0a367c514b86998f302da4e6d98fedaa8b4e8aaf (diff)
downloadast2050-yocto-poky-4ab132a20d33e70cf6736737c59d2c0ce2f79298.zip
ast2050-yocto-poky-4ab132a20d33e70cf6736737c59d2c0ce2f79298.tar.gz
dev-manual, ref-manual, yocto-project-qs: Updates to parallelism variables
The way the old manual set had worded the use of the BB_NUMBER_THREADS, PARALLEL_MAKE, and BB_NUMBER_PARSE_THREADS had become depricated. It suggested a lot of user intervention to get these variables set to have the build system utilize optimal parallelism. The change a while back to the build system where the variables are set to the number of build host cores now makes the variables automatically be set to their best values. I have gone through the manual set and changed wordings appropriately to reflect this. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 3a27b1792c92a2f22173315e2732f672cdad2c78) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml30
1 files changed, 12 insertions, 18 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 8fe9b76..f21558e 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -509,15 +509,17 @@
</para>
<para>
- Another couple of variables of interest are the
- <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></ulink> and the
- <ulink url='&YOCTO_DOCS_REF_URL;#var-PARALLEL_MAKE'><filename>PARALLEL_MAKE</filename></ulink> variables.
- By default, these variables are set to the number of processor
- cores your build host uses.
- However, if your build host uses multiple processor cores,
- you should increase these settings to twice the number of
- cores used.
- Doing so can significantly shorten your build time.
+ Another three variables of interest are the
+ <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></ulink>,
+ <ulink url='&YOCTO_DOCS_REF_URL;#var-PARALLEL_MAKE'><filename>PARALLEL_MAKE</filename></ulink>,
+ and
+ <ulink url='&YOCTO_DOCS_BB_URL;#var-BB_NUMBER_PARSE_THREADS'><filename>BB_NUMBER_PARSE_THREADS</filename></ulink>
+ variables.
+ By default, these variables are optimally set based on the
+ number of processor cores your build host uses.
+ Although it is possible to override these variables, the
+ default values the OpenEmbedded build system derives provide you
+ with parallelism during the build.
</para>
<para>
@@ -898,18 +900,10 @@
<filename>conf/local.conf</filename> configuration file
in the Build Directory.
You need to manually edit this file to specify the machine you
- are building and to optimize your build time.
- Here are the minimal changes to make:
+ are building:
<literallayout class='monospaced'>
- BB_NUMBER_THREADS = "8"
- PARALLEL_MAKE = "-j 8"
MACHINE ?= "beaglebone"
</literallayout>
- Briefly, set
- <ulink url='&YOCTO_DOCS_REF_URL;#var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></ulink>
- and
- <ulink url='&YOCTO_DOCS_REF_URL;#var-PARALLEL_MAKE'><filename>PARALLEL_MAKE</filename></ulink> to
- twice your host processor's number of cores.
</para>
<para>
OpenPOWER on IntegriCloud