From fdd99bcb117f83c876f169965c34ae246901384d Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 13 Feb 2014 13:21:35 -0600 Subject: ref-manual: Added ICECC_PARALLEL_MAKE to glossary. Fixes [YOCTO #5801] First draft of this description. (From yocto-docs rev: 412d0cc7dbb74ece45940c40fbb617217ab88d2d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 40 ++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 8fe4c1a914..d8e0d2b666 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -2405,6 +2405,46 @@ + ICECC_PARALLEL_MAKE + + + Extra options passed to the make + command during the do_compile task + that specify parallel compilation. + This variable usually takes the form of + -j 4, where the number + represents the maximum number of parallel threads + make can run. + + The options passed affect builds on all enabled + machines on the network, which are machines running the + iceccd daemon. + + + + + If your enabled machines support multiple cores, + coming up with the maximum number of parallel threads + that gives you the best performance could take some + experimentation since machine speed, network lag, + available memory, and existing machine loads can all + affect build time. + Consequently, unlike the + PARALLEL_MAKE + variable, there is no rule-of-thumb for setting + ICECC_PARALLEL_MAKE to achieve + optimal performance. + + + + If you do not set ICECC_PARALLEL_MAKE, + the build system does not use it (i.e. the system does + not detect and assign the number of cores as is done with + PARALLEL_MAKE). + + + + ICECC_PATH -- cgit v1.2.3-54-g00ecf