e23ae981cc
These files are difficult to support in the Starlark product configuration. They also aren't really a good representation of products even with Makefiles, because they only display information from products that have been imported with import-nodes, but generate empty files for the other products that are included from the imported ones. For example, lunching aosp_arm64 then running `m out/products/build/make/target/product/core_64_bit.mk.txt` would generate a file full of empty variable assignments. Bug: 221312856 Test: Presubmits Change-Id: I18613a628968acc25b57b44e229de7df1b2476ef
Android Make Build System
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.