summaryrefslogtreecommitdiffstats
path: root/Config.in
diff options
context:
space:
mode:
authormb <mb@3c298f89-4303-0410-b956-a3cf2f4a3e73>2010-08-18 13:57:58 +0000
committermb <mb@3c298f89-4303-0410-b956-a3cf2f4a3e73>2010-08-18 13:57:58 +0000
commitc7ee63dd761a6cf7f863b00181aaa2002784f06b (patch)
tree2a58f3feae7536cc41649e7bd25f142bed291782 /Config.in
parent7a57b60ffa7dd01a69fd4dc14b08dddb8516130b (diff)
Support parallel build of certain packages
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22696 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'Config.in')
-rw-r--r--Config.in32
1 files changed, 32 insertions, 0 deletions
diff --git a/Config.in b/Config.in
index daecd171e..85d3adf9f 100644
--- a/Config.in
+++ b/Config.in
@@ -215,6 +215,38 @@ menu "Global build settings"
help
Enable IPV6 support in packages (passes --enable-ipv6 to configure scripts).
+ config PKG_BUILD_PARALLEL
+ bool
+ prompt "Compile certain packages parallelized"
+ default n
+ help
+ This adds a -jX option to certain packages that are known to
+ behave well for parallel build.
+
+ Note that this may overcommit CPU resources depending on the
+ -j level of the main make process, the number of package
+ submake jobs selected below and the number of actual CPUs present.
+ Example: If the main make is passed a -j4 and the submake -j
+ is also set to 4, we may end up with 16 parallel make processes
+ in the worst case.
+
+ You get maximum build performance, if you set the package build
+ jobs to the number of CPUs (cores) available and also start the main
+ make process with -jX, where X is the number of CPUs (cores).
+ However, make sure you have enough RAM available for
+ NR_CPUS to the power of two (NR_CPUS^2) make jobs.
+
+ If you are unsure, select N.
+
+ config PKG_BUILD_JOBS
+ int
+ prompt "Number of package submake jobs (2-512)"
+ range 2 512
+ default 2
+ depends on PKG_BUILD_PARALLEL
+ help
+ The number of jobs (-jX) to pass to packages submake.
+
comment "Stripping options"
choice