commit | 621b02ab22ad183b8c5e7b75aa17e816dc0f6194 | [log] [tgz] |
---|---|---|
author | Devin Moore <devinmoore@google.com> | Wed Jan 24 19:12:52 2024 +0000 |
committer | Devin Moore <devinmoore@google.com> | Wed Jan 24 19:28:21 2024 +0000 |
tree | 0351f6ceafea982a6f86fcfcda2d468c8c68a677 | |
parent | 45db966e90c5e2e81198957cc69acac9e76f2bd2 [diff] |
find_static_candidates.py: protect against missing keys in module Looks like modules can now be missing "shared_libs" and "static_libs". Use default values of empty sets where applicable, or check for the existence of the keys before looking for them. Test: python find_static_candidates.py --module audioserver Bug: 322190716 Change-Id: I8be9bd2c1562975db57ffbf89d57ff2767f0b1f1
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.