| commit | a90b6070c7369c9cf401b5c391f9fbf20d2d5d6f | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Jul 25 10:12:48 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Wed Jul 25 14:30:05 2018 -0700 |
| tree | b56911fc4ae9e9f0e30021ceedbbc797e6aad330 | |
| parent | ae08b5189125c348201f6c90310663674e05ed34 [diff] |
Move manifest fixing to a separate rule Manifest fixing is getting complicated, move it to a separate rule so that it doesn't have to be a function in definitions.mk. Bug: 111347801 Test: m checkbuild Change-Id: Ibc60ad79c9c4f4a63a0e1c8f7779534954fb6585
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.