| commit | 9c8103317c53f1c3e17456017c24986a00415938 | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Fri Aug 10 15:15:56 2018 -0700 |
| committer | Steven Moreland <smoreland@google.com> | Fri Aug 10 15:15:56 2018 -0700 |
| tree | 42ede47ca96612176e52a9c0042662ec5f96bcaf | |
| parent | 35edeae74f0c0c2545997643faf11edad50ac1b4 [diff] |
Add additional OWNERS for entries to the VNDK. The target/product/vndk/current.txt file was added in order to have a global check on what is included in the VNDK. This for instance adds as an extra check to make sure that a device-specific module doesn't end up in this global set. However, because modifying the VNDK is relatively common, this puts undue burden on the build team to conduct reviews. For that reason, I'm opening it up with additional reviewers. Bug: N/A Test: N/A Change-Id: I9827260bde8ec757be363fc153b718d9c0b68f25
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.