| commit | 11590358b5f570d231c78e739a1b059ed6bbe572 | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Mon Dec 16 14:44:16 2024 -0800 |
| committer | Joe Onorato <joeo@google.com> | Mon Jan 06 15:22:15 2025 -0800 |
| tree | 744010d9b4959fedd72dfddd10cc1c602c064d88 | |
| parent | 928fa2298030d47ea30c29586e7bba913c9eb23d [diff] |
Add metadata to module info about whether the module came from soong or make And a tool to print out the soong modules with their module info still coming from make, because we need to eliminate those. Test: build/make/tools/missing_soong_module_info.py Bug: 384569435 Change-Id: I093148451a0353fb82da9503b6c0c722ebc06336
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.