commit | 9f5b5c2268757aeb340d495772f133f95704aaea | [log] [tgz] |
---|---|---|
author | Joe Onorato <joeo@google.com> | Mon Apr 24 01:09:37 2023 -0700 |
committer | LaMont Jones <lamontjones@google.com> | Mon May 01 21:20:28 2023 +0000 |
tree | 173c055721fceeec0ac6aa7daf8157d98ffafba8 | |
parent | 2467b20cecfcf9d6fc5df7b4fbcfda0dd5f4540a [diff] |
Save approx 18GB of RAM by not having a bazillion copies of the same modules names Bug: 280108166 Bug: 278864904 Test: treehugger, m, manual inspection Merged-In: 2556850 Change-Id: Ib564b3edf4a0523fc8231b8e57a5ba9c42a73294
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.