| commit | 233d5b97f84e3639d3c8c78bd93e2e5c2cbbd50c | [log] [tgz] |
|---|---|---|
| author | Wei Li <weiwli@google.com> | Fri May 05 10:49:28 2023 -0700 |
| committer | Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | Fri May 19 00:35:20 2023 +0000 |
| tree | 3d7ddb7d8dc3d4e6ff4ee21ae2b716215d89582a | |
| parent | d637b06d8f445f5aa433df413c5bfcb3943a0c6e [diff] |
Some changes to support SBOM generation for b build unbundled APEXs. 1) Use output file path of installed files in build system since there is no PRODUCT_OUT in Bazel 2) Use CONTAINS to describe the relationship between a APEX and files it contains 3) Generate SBOM of APEXs, which is similar to SBOM of products Bug: 275472038 Test: CIs (cherry picked from https://android-review.googlesource.com/q/commit:fd7e6517d345d3b8d4af12dae345434d968b83b9) Merged-In: I41622366e5e6ed9dc78cca7bc7bb69a1f8f9bd9f Change-Id: I41622366e5e6ed9dc78cca7bc7bb69a1f8f9bd9f
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.