| commit | c68e0336959e594e4efa3626521ffad6e48664e9 | [log] [tgz] |
|---|---|---|
| author | Jaewoong Jung <jungjw@google.com> | Thu Nov 21 15:30:17 2019 -0800 |
| committer | android-build-merger <android-build-merger@google.com> | Thu Nov 21 15:30:17 2019 -0800 |
| tree | abba744aa5dde1ed43e51dee05ce7725c9022157 | |
| parent | e7003e9f8dbc70c7ada5f5f2374615fde7118316 [diff] | |
| parent | 18b0a0a072291611b8fcd68d57557be0b2c7d58b [diff] |
Merge "Copy additional test apk outputs to suite dirs." am: 4a0832210c am: 18b0a0a072 Change-Id: Ic7ee4e41d29762471fc5b25dce6e757858fd1ea9
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.