| commit | 41b588a75c7fea3febd39398f013e6eeca973bf0 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Sat May 02 01:57:15 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat May 02 01:57:15 2020 +0000 |
| tree | c497e28cd430de8d08e6ba482995748ac308747d | |
| parent | f17ccf2d4775c26f38c231a0774b038ba3490a65 [diff] | |
| parent | a4ce9b369e92d9a3831484d5a418bb55ae5df255 [diff] |
[automerger skipped] Merge changes from topic "sdk_version_variant" into rvc-dev am: a4ce9b369e -s ours am skip reason: Change-Id Ibdf18807a2ffe9bb352d74880a802ad55b57f154 with SHA-1 fca369e4e3 is in history Change-Id: I1627ee8940e6bbee63597788aa2c0b02a1ee8d37
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.