commit | 45c0f56ae9d8a1009b5c85ee07a0849538c1ecc2 | [log] [tgz] |
---|---|---|
author | Xin Li <delphij@google.com> | Thu Oct 10 21:51:38 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Thu Oct 10 21:51:38 2019 -0700 |
tree | e9cfeb07ded83face9ada63fdb27f3520ab52203 | |
parent | 4a44a68a17f606bc81661c178bd68fd5b49f8cf1 [diff] | |
parent | d6d0eb2522057d41abf6b944ecb9c7a90dce485a [diff] |
[automerger skipped] DO NOT MERGE - Merge QP1A.191005.007 into master am: 66ec993fe5 -s ours am: 39124f2240 -s ours am: 656c9fcf1b -s ours am: d6d0eb2522 -s ours am skip reason: subject contains skip directive Change-Id: I49929c3f86b6e72f2045dc61a7cc784444607df5
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.