Commit graph

7 commits

Author SHA1 Message Date
Neeraj Upadhyay
24d5515b41 scripts: build_all: build sdm defconfigs
Add support for building new sdm defconfigs.

Change-Id: I7d1ae9fb0a3888a92ee4df850061afe3d2e378c6
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
2017-01-01 21:01:10 +05:30
Rohit Vaswani
f52a07bd52 scripts: build-all: Fix the check_kernel for MSM
Update the check in the check_kernel function for
newer kernel.

Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org>
2016-03-23 20:57:40 -07:00
David Brown
0bba5777ad scripts: Call out python2 explicitly
Many systems these days have both python2 and python3 installed.  The
unversioned executable `python` may point to either version.  Per
https://www.python.org/dev/peps/pep-0394/ , scripts that need Python 2
should explicitly call this out in the shebang line.

These build scripts are both specific to python 2, so call this out in
the shebang line.

Change-Id: I11f70c341e484254dc1679db65c2ed5ac61e510f
Signed-off-by: David Brown <davidb@codeaurora.org>
2016-03-23 20:51:59 -07:00
Abhimanyu Kapur
aa10e64c96 scripts: build_all: stop building mdm targets
Stop building mdm based defconfigs until all kernel
upgrade issues are resolved.

Change-Id: I988ea872c70d5c6645d52ae9d8abc1e1fcb4ec16
Signed-off-by: Abhimanyu Kapur <abhimany@codeaurora.org>
2016-03-23 20:51:58 -07:00
David Brown
ccd9bd0de7 scripts: Restore some of the parallism in "all" builds
The use of min/max should not have been switched, and instead of
forcing at least "-j2" for builds, it is enforcing no more than two
jobs in parallel.  This has drastically reduced the parallelism of the
builds.

Change this to use "max" as intended so that we do make use of
available CPUs, using at least two.

Change-Id: Ifad0c98ef0ce56fc6c2368321a6cfd763e81b370
Signed-off-by: David Brown <davidb@codeaurora.org>
2016-03-23 20:51:56 -07:00
David Brown
0a46b62c87 scripts: Reduce parallelism in "all" builds
Kernel builds are a bit asymmetrical in as far as CPU and memory
resources go.  Compilation itself tends to scale fairly linearly in
RAM usage per number of CPUs.  However, the link phase tends to use a
fairly constant large amount of RAM and generally only one CPU.

The existing attempt to build more in parallel has mostly resulted in
too many link steps running, which ends up swapping.

Instead of dividing the CPUs by the number of targets, just divide it
by two, and assume this will at least get us some compilation
happening during the link phase of one target build.

Change-Id: I0f8cac2d73600700d8ad6cb2a1b98e9529bb53a8
Signed-off-by: David Brown <davidb@codeaurora.org>
2016-03-23 20:51:54 -07:00
David Brown
fb89f1cbee scripts: Add build-all.py kernel building utility
A small script to make it easier to build and test all target
configurations.  Assumes the cross compiler is in the path, and
builds all defconfigs matching certain patterns.

Change-Id: Iffe265f417a32101cfc3b054eaf3c6d6a5784ca9
Signed-off-by: David Brown <davidb@codeaurora.org>
2016-03-23 20:51:52 -07:00