| commit | a7a6cf63bdb2e5fe04daffc840fc84e82dc8193f | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Mon Feb 24 19:20:49 2025 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Mon Feb 24 19:25:09 2025 +0000 |
| tree | 87fa2832bfb6b985d7546c6bc5c137c3b83d1974 | |
| parent | 3e5812831b026f152cc75dcc17c1cff6e34c1782 [diff] |
Filter out framework and ext in uses library tag propagation in make Similar to https://r.android.com/3476311, this change ensures that "framework" and "ext" is not propagated to the reverse dependencies via uses library tags and the manifest check does not fail for Android.mk-defined modules. Test: CI Bug: 390048523 Change-Id: I47b1c9261de08e7dc817014ad49400d1650d3018
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.