| commit | d088650481a69fc908c4f2bd438c591b08a86911 | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Tue Jan 09 16:49:53 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Thu Jan 11 15:30:10 2024 +0000 |
| tree | 203d60fe72ab7dda9cb79e780d421ca3f53b2199 | |
| parent | 3939d1ca5957571814933cc311655840a513677e [diff] |
aconfig: add flag type in flag table and remove info byte from value array 1, add flag type to the flag table. Before flag table only stores the mapping from (package id, flag name) to (flag id u32). The original intent is to do bitmasking on the top byte of flag id to indicate flag type. Now split the flag id u32 to two u16, the first represent flag type, the second represent flag id. So after the change, the flag table now shows the following mapping: (package id, flag name) -> (flag type as u16, flag id as u16) 2, originally we plan to store a info byte together with each flag value. The info byte is used by storage service damemon to mark up the flag status, such as if it is accepting server side flag push. After internal discussion, it is better to just create the info bytes as another file by storage service damemon. So that the value file is purely a flag value array. Bug: b/312243587 test: atest aconfig.test Change-Id: I7f953076b4269cf786bc23723078290e5ebe10bc
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.