| commit | c3d408e3c180327bfbc88e9147e25bb793071bf6 | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Mon Oct 29 13:16:09 2018 -0700 |
| committer | Mark Salyzyn <salyzyn@google.com> | Mon Oct 29 13:37:04 2018 -0700 |
| tree | 1d331d3414a9976ce958ad972c6594e329e997e6 | |
| parent | 89fe71180b829916b09d76a8f76e217b34ab3ce1 [diff] |
build_image tune right-size image To more quickly settle on a no free space result, recognize that there is roughly 1/58.5 overhead managing the free space pool as determined experimentally. This algorithm carries with it some risk of being sensitive to any alterations in ext4. This also addresses the issue of a much larger apparent free space available calculated on the sample pass when deploying ext4 dedupe, and resolves the poorer estimation that happens without accounting for the overhead. The alternative of adding a second pass works to a similar, and likely more comforting algorithm and result. But doing so adds a minute to the typical incremental build time, or +50% to the time it takes to determine ext4 right sized images. Test: manual Bug: 111302946 Change-Id: Id5ae6645b9aa2d036e6fefe2fb17672e8f8ef6f0
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.