commit | 3b89c6532a2fa93301b74be8fbb8c128779efe1c | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Mon Nov 06 13:54:39 2023 -0800 |
committer | Colin Cross <ccross@android.com> | Tue Jan 02 17:21:22 2024 -0800 |
tree | db48665c3cd308b19163cea1f5fade010bc91a92 | |
parent | b2063049f878fdb37025b7f96df5adfb4585af28 [diff] |
Support Soong-generated module-info.json entries Allow Soong modules to generate their own module-info.json entries by merging Soong's module-info.json file into the one generated in Make. Skip collecting unnecessary ALL_MODULES.$(my_register_name).* that are only used for module-info.json if the module was already handled by Soong via the LOCAL_SOONG_MODULE_INFO_JSON property. Bug: 309006256 Test: Compare module-info.json Change-Id: I2c9db3c7c7bae7bd6cb889d7ebc2e383c278c82d
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.