3dea629a9e
This change add cache in generated jave code to improve the performance. The cache is a DeviceConfig.Properties. One Properties contains all flag values from the given namesapce. The Properties for a given namespace is initialized as null, and the first call for any flags in that Properties will trigger the call to fetch all the values. After the first call, the flag values are stored in the Properties, so the following calls will directly get the value from the Properties instead from the backup storage. Test: atest aconfig.test.java Bug: 307511846 Change-Id: Ic43626101c28099199b6faa419cf1945bd53b15d |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
banchanHelp.sh | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
cogsetup.sh | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
METADATA | ||
navbar.md | ||
OWNERS | ||
PREUPLOAD.cfg | ||
rbesetup.sh | ||
README.md | ||
shell_utils.sh | ||
tapasHelp.sh | ||
Usage.txt |
Android Make Build System
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.