| commit | 702408ecbb5d40c08d3850658e8ec0c78ff0cb30 | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Mon Apr 08 17:59:13 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Wed Apr 10 16:36:46 2024 +0000 |
| tree | 5d7ac2921162e0474f1ac4c5af46db71d509508a | |
| parent | ba67028405cdd4c02da7e0682fe528ec97210de0 [diff] |
aconfig: update storage file to store flag index instead of file byte offset Previously, in package.map, we store the byte offset of the first flag in a flag package in a flag value file. In flag.map, we store the within package flag byte offset. Once we know the total offset, we can locate the flag in the flag value file. However, this offset may not work for flag info file. Currently we only have boolean flags. Each boolean flag value and info takes up 1 byte in flag value and flag info file. So the byte offsets are the same. But in the future, when we add a new flag value type, or add more contents to flag info file. Then the byte offset for flag value file and flag info file may not be same. Instead, we should store index rather than offset. The package map should store the index of the first flag in this package. The flag map stores the within package index. Then flag value read api and flag info read api can then infer the byte offset independently. Bug: b/321077378 Test: atest -c Change-Id: Iad89776d5369715ba2d8faaea18261ac3271f13b
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.