| commit | 074bfc1264619edada05f5002794c627c1bd0533 | [log] [tgz] |
|---|---|---|
| author | Treehugger Robot <treehugger-gerrit@google.com> | Fri Apr 14 21:23:29 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Apr 14 21:23:29 2023 +0000 |
| tree | d9ecc3b5f6429ef5a4ce6b6221e0ee1687c6039d | |
| parent | 1b07bfec46450d6a500a06a48c40ef24477839e0 [diff] | |
| parent | 28fc5a97a76bd857baf1ce6e6058bb802f442d3b [diff] |
Merge "Create separate python libraries for the following logic and refactor SBOM generation script accordingly." am: ebf41e9a91 am: 28fc5a97a7 Original change: https://android-review.googlesource.com/c/platform/build/+/2525827 Change-Id: I1e65b41eedd122d3258270a78168ef2ec83e60c9 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.