| commit | 7e274918c0ebd963f33d922c82d5669d6a3a9a9f | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Thu Aug 22 05:22:44 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Thu Aug 22 05:22:44 2019 -0700 |
| tree | 42cc0ba0947afec2352b2fb10ee639bba308928c | |
| parent | 1ce08094d35676be7f3e5288ea0016b6b27d2926 [diff] | |
| parent | ffdeeae450d98c837b42bbc6ec112cc9a2af36d4 [diff] |
[automerger skipped] Merge "Remove stale artifact whitelist entries" am: ffdeeae450 -s ours am skip reason: change_id Ia495ed7b883fd100fdb75206c13cedb6fa62b0b2 with SHA1 5f7c08fbb3 is in history Change-Id: I9c8554dabeffb02849b781e8efde6624a55b9e2d
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.