| commit | 76a5d103dbe6f7862622d6a062051dd3bad61925 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 22 01:05:58 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 22 01:05:58 2020 +0000 |
| tree | d990c7313d3151ac8a61ea7b83d74302807405dc | |
| parent | cff44aa9931445e912ddc6a535533c7e32d6dfbd [diff] | |
| parent | 43d32fb1385172d10ba0b8c7b5a92fe91cf8418f [diff] |
Merge "Turn on PRODUCT_ENFORCE_PRODUCT_PARTITION_INTERFACE if PRODUCT_SHIPPING_API_LEVEL > 29" am: 02b1498d5a am: a7f1ee1ac8 am: 43d32fb138 Change-Id: Ia39dc6fcd3a0db4ceec74767d4bf98203834cc5c
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.