| commit | e06e97464c1fcaaa72fb5e5f1152be48d0ce0924 | [log] [tgz] |
|---|---|---|
| author | Hridya Valsaraju <hridya@google.com> | Thu Aug 16 10:45:05 2018 -0700 |
| committer | Hridya Valsaraju <hridya@google.com> | Fri Aug 17 11:40:06 2018 -0700 |
| tree | 793db840ddeb83b0c10e4ca917906f1f60a20eaf | |
| parent | 1fa790cb53ee8cf84aae23fb2857670c92e1c151 [diff] |
Correct PRODUCT_USE_FASTBOOTD USAGE Remove all usage of flag PRODUCT_USE_FASTBOOTD as it will not be set when these files are processed by the build system. Bug: 78793464 Test: make bootimage and check for fastbootd binary in recovery Change-Id: I371a6d2beddeb54a88281934b54b8c61ead12d4f Merged-In: I371a6d2beddeb54a88281934b54b8c61ead12d4f (cherry picked from commit b9d535356b25dd638428c2b4d71e7031752c67db)
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.