| commit | ae2159dbcf9fe375ba5e6419383f2005ea72348e | [log] [tgz] |
|---|---|---|
| author | Dario Freni <dariofreni@google.com> | Tue Jun 09 10:27:46 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jun 09 10:27:46 2020 +0000 |
| tree | 55752617b7d457addfc2198d9b5eebe9f2c59841 | |
| parent | 0c5aef4d5bff5bff2cdc4aa95cf57f401d020351 [diff] | |
| parent | e93b598eb8f3a7654308659325dc44930064750c [diff] |
Merge "Use APK CtsShim prebuilts for flattened apex." into rvc-dev-plus-aosp am: f3c2823040 am: e93b598eb8 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/11789975 Change-Id: I0899451db34a4a24ed4c0c7c68ca7dc453645cf5
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.