commit | 2f3cb44b289ab5aba0ff524580f4d9f803b892a3 | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Jan 09 09:38:56 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Jan 09 09:38:56 2020 +0000 |
tree | e1689e149eae01b484aecee54a6266e0c30a2021 | |
parent | bf4f7acb17591d352d2f18034f200810ba077820 [diff] | |
parent | 4b482e337e81bdc5105bc8125a5ac99b01461e4b [diff] |
[automerger skipped] Merge "Update references to sdkext" am: b9e912dc9d am: 2bba9827af am: 4b482e337e -s ours am skip reason: Change-Id I628fc555b82e9bd931c8f0cce2222b02efad6036 with SHA-1 37e998ac31 is in history Change-Id: I2c6ef03037c238e24eb0329f120f0a52343f39c4
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.