Build summary UX
martinrb at google.com
Fri Aug 22 19:04:43 UTC 2014
On Fri, Aug 22, 2014 at 3:10 AM, Erik Joelsson <erik.joelsson at oracle.com>
> On 2014-08-22 01:10, Martin Buchholz wrote:
> Serial execution is useful for both resource-constrained environments and
> for folks trying to profile the build itself. Serial build is also likely
> to be optimal if you are optimizing for total energy used rather than total
> wall clock time.
> If you are in a resource-constrained environment you can easily set
> either --with-jobs=1 to configure or JOBS=1 to make and get a serially
> executed build. Also, if configure doesn't find a lot of memory or cpu
> cores, the default number of jobs will get set to a small value, even 1 if
Increasingly I am living in a world where I have more than enough CPUs, but
not enough RAM. Chrome eats it all! Don't know what configure or make
could do about that problem - it's a tough one.
> There are tricks to profiling the build in place already. If you run with
> LOG=trace on a machine with gnu time installed, you will get a special log
> file containing the wall clock time for each command executed, both in
> recipes and $(shell). I use this frequently when trying things to optimize
> build performance.
Thanks. I see you have done an excellent job documenting "make help".
But fix the typo below: s/build/built/
. make bootcycle-images # Build images twice, second time with newly
More information about the build-dev