| commit | 2b191894c29284cf52633bd68126a0e0bffa00b5 | [log] [tgz] |
|---|---|---|
| author | Mark Salyzyn <salyzyn@google.com> | Mon Nov 05 08:31:29 2018 -0800 |
| committer | Mark Salyzyn <salyzyn@google.com> | Tue Nov 06 15:57:03 2018 -0800 |
| tree | d938f8123596a58a10b21d801f2f86baeb0a80a3 | |
| parent | d0b9758203d2ff66059fcd60fa5bf53078a773ef [diff] |
build_image still too aggressive with right sizing (part troix) Regression introduced by c3d408e3c180327bfbc88e9147e25bb793071bf6 Found a case where 1 + 1/60 reduction in size based on free space failed when right sizing an ext4 image. Reduced the math to 1 + 1/61. Test: compile Bug: 111302946 Change-Id: I0f32c75e80b5da4d47671055ac274ccc2b485992
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.