| commit | ef5dc401aea911f3217ef96dc55c056ca18febeb | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Fri Sep 11 06:20:25 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Sep 11 06:20:25 2020 +0000 |
| tree | de2656b4a588aae609992d6c88e49efe715f19ee | |
| parent | 6fa28a9ef6c744348dbebcdf2cd119f9ae79e818 [diff] | |
| parent | 55c090ebe0ccca10eee3b7205025d1d8e55ae9df [diff] |
Merge changes I4a43604b,I7200f5f9,If3402a0a am: 55c090ebe0 Original change: https://android-review.googlesource.com/c/platform/build/+/1413820 Change-Id: Ia65262f3e8a337e8164b02417bc0635f33e5f18b
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.