commit | aa0f7c10c6cabebcf5acad1d4ce870dbd246b193 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Thu Oct 08 01:29:20 2020 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Thu Oct 08 01:29:22 2020 +0000 |
tree | f32ccb287767c1374e60f3be29327f7f1d43b2c1 | |
parent | e4a4679b13f73f060d30219ac80d092f837144d1 [diff] |
Version bump to SP1A.201008.002 [core/build_id.mk] Change-Id: I9e62a7a6607d4bccc32c48b9664a08bd0d2f4e0f
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.