commit | 82447e9aa48a9a63df37bf76b01a1fb5695e3899 | [log] [tgz] |
---|---|---|
author | Steve Berbary <sberbary@google.com> | Wed Oct 05 02:27:58 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Oct 05 02:27:58 2022 +0000 |
tree | ad06122f47f43a0e69378178d43cdffaa5e864b0 | |
parent | 0c3e6a037ccc2c30c11470c2a9343358fd0c94cb [diff] | |
parent | eef4b24433d447d5e0e04287dae62e1b2da22947 [diff] |
Update Security String to 2022-12-01 am: eef4b24433 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/20112473 Change-Id: If0f5b8f90c28f287d541853c84aee3b935a014ee 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.