commit | bd17fab26048d9469fd6d857517d77a81e9b1d74 | [log] [tgz] |
---|---|---|
author | Hridya Valsaraju <hridya@google.com> | Wed Dec 12 18:03:41 2018 -0800 |
committer | Hridya Valsaraju <hridya@google.com> | Fri Dec 14 14:13:24 2018 -0800 |
tree | 567b5c51f421d12f65c8c8c3681fed61e40319f9 | |
parent | e7e33bc7f5dd7f81f59c858ed8307b1e6452aa38 [diff] |
Relax inode usage estimation slack for DAP right sizing The current increase of 4 % is insufficient for some targets. Test: mmm Bug: 119115481 Change-Id: Idcba8025b913da9b70794bfc7464d15b4d99ad34 (cherry picked from commit 3e02e34090d9a81a7eae64e8f094c7b5971778f3)
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.