| commit | 18ffd5891ed9674f12929627fe18c43bed31e69c | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Wed Jul 31 10:31:20 2019 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Thu Aug 01 14:56:45 2019 -0700 |
| tree | 8ad119cf22d7c2b5a4ef4a33d3803f370fa3b2f4 | |
| parent | 8b8b9b6bf8291ba9eb1d6c92956e0ac3b912a058 [diff] |
Remove import_includes/export_includes Now that ONE_SHOT_MAKEFILE no longer exists, we don't have to rely on the filesystem to store this informtion. This removes ~16.7k files from our build graph (aosp-master/aosp_arm64-eng), though only about 600 of them were being used in a normal build. Test: treehugger Change-Id: I3ac12f5ea7f11d25064109a0599bc5be1976fba5
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.