commit | 0c3e6a037ccc2c30c11470c2a9343358fd0c94cb | [log] [tgz] |
---|---|---|
author | Duy Truong <duytruong@google.com> | Thu Sep 22 04:03:12 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Sep 22 04:03:12 2022 +0000 |
tree | 92146c3a903eed16e7ee49bde334d875dca5a61a | |
parent | eaf21cca171669d12b65bafc16c03c530f1cf3c9 [diff] | |
parent | 495f4c07764db78c922d32d79e07f1c522671c77 [diff] |
Merge "Initial STS sdk" into sc-dev am: e0438b6f1b am: 214aa1d785 am: a0b3f427ca am: 495f4c0776 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/19776213 Change-Id: Id17d606881fa3d339c8a14e85ba3893911714dec Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.