commit | 5ba8a8b77507f93aa48cc61c5ba3f31a4d0cbf37 | [log] [tgz] |
---|---|---|
author | Dennis Shen <dzshen@google.com> | Mon Sep 23 17:06:44 2024 +0000 |
committer | Dennis Shen <dzshen@google.com> | Mon Sep 23 23:31:44 2024 +0000 |
tree | 0c75912655bfca3509ebf327c394a62bcff79969 | |
parent | eda61c1a851f2967c5757c6eb5ff90b33e7a7efd [diff] |
aconfig: create flag info file at build time Previously flag info file is created at run time rather than at build time due to two reasons: 1, it saves some storage space on each container 2, initially the flag info file does not container any flag non run time info, so creating this file at run time on device is more efficient. However, flag info file is fairly compact, 1 byte per flag. So the storage footprint increase is minimal. Also, now flag info file contains flag information known at the build time such as if the flag is read write. To help create flag info file at run time, we actually have to keep additional information on flag map file. Then use this information to create flag info file at run time. Now it is more efficient to just create flag info file at build time. In addition, to create flag info file at run time, we need to maintain an additional write api create_flag_info_file. Each time flag file version changes, we have to keep the old version of this API as well. If we create flag info file at build time, then we don't have to maintain this API. Overall the benefits outweight the 1 byte per flag storage overhead. Therefore making this change to create flag info file at build time. Bug: b/301491148 Test: m Change-Id: I33993a438bbaf8697214655288ced30817b9592e
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.