commit | a574568ca6af13a9b1de6a82ca069984306cc256 | [log] [tgz] |
---|---|---|
author | Wei Li <weiwli@google.com> | Tue Mar 04 16:29:32 2025 -0800 |
committer | Wei Li <weiwli@google.com> | Tue Mar 04 16:32:45 2025 -0800 |
tree | dc3b862366862f076d2ca5ddc66c0b28eebc16ae | |
parent | 3c7cefb37e701860b425630f158481ad9cb75371 [diff] |
If a file is from a soong module it doesn't need the is_platform_generated flag in compliance metadata In soong-only build most of these platform-generated files have been converted to soong modules so the flag is_platform_generated is not needed any more Bug: 324465531 Test: build/soong/tests/sbom_test.sh Change-Id: I7d1d79a73d4c55262c1d351d989b6cb7e768affb
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.