| commit | 87ca28cbfaaba151dd2d3ee8fc35ec3d71530306 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 21 18:05:55 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 21 18:05:55 2020 +0000 |
| tree | 27c9b80f49631d8a9fd3b51a23a39c435c11ea7c | |
| parent | 0ea8dc1cb49a0a3247f50aa912ded7e86b376502 [diff] | |
| parent | de72054e03d00981e7e44d6e92dae85e94d39d56 [diff] |
Merge "Exclude holes from the block map." am: 9581181338 am: 4969b45d50 am: de72054e03 Change-Id: I46db3c1d99ab77d04171b7067e6303d91e626400
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.