| commit | faf9b0128c2c6b82926cb37f0521d74338baa271 | [log] [tgz] |
|---|---|---|
| author | Hugo Drumond Jacob <hugojacob@google.com> | Mon May 20 18:32:50 2024 +0200 |
| committer | Hugo Drumond Jacob <hugojacob@google.com> | Mon May 20 18:35:24 2024 +0200 |
| tree | 4a2fedde85eab7e60cc7387744a8acc0372e2cf3 | |
| parent | 7963591826de284b0b6f7b7fdaca30869ea3587d [diff] |
Dump the required modules into module-info.json Certain applications, like tracking the dependency chain of modules, knowing the "required" dependencies is required. In this context, "required" here means the `required` field in Android.bp files. Bug: 339193439 Test: Inspect module-info.json for the `required` field Change-Id: I09977bf71a0a0ae46ea9268ce1faa5c90673bb7a
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.