commit | be1b86480dfac5d1dfb8e0bdd58855ea029fe914 | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Mon Oct 07 06:14:20 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Mon Oct 07 06:14:20 2019 -0700 |
tree | c04947b674f433a555bf598aba068d1c81b41b9e | |
parent | 42127e02136abf0c96ba71d706d23303f229e554 [diff] | |
parent | 2c5def62dc843c4ca79ef9ad66f59b58b2fd6f7f [diff] |
[automerger skipped] Disable vendor path check for mainline variants am: 2c5def62dc -s ours am skip reason: change_id I607781ce7c6299cbc98c54c683d04db3b65c2e21 with SHA1 42127e0213 is in history Change-Id: I76d70443a8acf96a19fc8b7f276bd3896e93b2c3
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.