| commit | d6b799a6271c0da185b1859446612703d49fb717 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 19 14:54:42 2020 -0400 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 19 16:12:23 2020 -0400 |
| tree | a3b9b933282011b8b8a89c17e46ff867b0bd5dc1 | |
| parent | 2e80113ad211e01055df06fd52b37c1fea10e18e [diff] |
Searches for debugfs_static in search path When signing APks on build server, there might not be an android repo. Usually deapexer.py will be run from otatools.zip after exctration. So we should look for debugfs_static in search path Bug: 165347497 Test: Sign using self-service Change-Id: I608870b0184bd8f5f07afa53355b39de47a97e1c
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.