| commit | 0df0f6bbf13a52006b1cabf7d7afd973019b4e3c | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Tue Jul 30 12:56:59 2019 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Jul 31 18:09:22 2019 -0700 |
| tree | 274f20e2b157286bbbc4ce4b6427f80a6aed0092 | |
| parent | 5c3fc2a7924988710e89901e46a2b16258032727 [diff] |
Remove [jni_]link_type files Now that mm/ONE_SHOT_MAKEFILE have been removed, we can expect to know about all of our dependencies at the end of the build. This removes 19k nodes from our build graph (aosp-master aosp_arm64-eng), though in a default build, only 3k of those are used. Test: ALLOW_MISSING_DEPENDENCIES=true, then trigger a missing dependency Test: treehugger Test: create link_type files, then apply CleanSpec.mk, ensure they're removed Change-Id: I9506331e4a9911d2f26e59a2f72a97aef1644073
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.