commit | 707e6f5ac85ab02adc62a1168eb7ec90fdb88d25 | [log] [tgz] |
---|---|---|
author | David Anderson <dvander@google.com> | Tue Sep 21 22:24:43 2021 -0700 |
committer | David Anderson <dvander@google.com> | Wed Sep 22 14:14:44 2021 -0700 |
tree | 9aa909f37871d0c85768bbb3b4a17fe6715eda05 | |
parent | 3c63667abb5f69685b933025c1cea24c4fe61efa [diff] |
Refactor generate-image-prop-dictionary. It's really error prone to add new partitions or image flags given the amount of code duplication here. Since most images have (or should have) roughly the same flags, this factors the work out into a helper function. Bug: N/A Test: m, m otapackage Change-Id: If1a22b9d7b5cf028ba52608322c4383792dae6b9
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.