commit | a82b2b5658208b817fe5ebad008cfc2aed07ff3e | [log] [tgz] |
---|---|---|
author | Zhenhuang Wang <zeek@google.com> | Mon Feb 20 09:05:06 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Feb 20 09:05:06 2023 +0000 |
tree | 53f223ae807f7d37677b055ab1912a7b78a50ed9 | |
parent | 208f01470b61865bb616c5a51564aa37473069b4 [diff] | |
parent | c14d68cebe080b3cba6f9f25a18fb46a20e75338 [diff] |
Merge "Enable `-sha256` feature to device-tests.zip" am: 195b5fc64c am: c14d68cebe Original change: https://android-review.googlesource.com/c/platform/build/+/2442621 Change-Id: I97d1c57c96a46bf973ea6e40f884b9cacaa7646d 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.