| commit | 997745dc13bd27eab4cc5bb4b7114aa15412f025 | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Thu Jan 25 18:10:31 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Fri Jan 26 18:02:07 2024 +0000 |
| tree | 99dd4ef192c0cf2186c8dbfd2d0575137d74752c | |
| parent | c7a1c76e28df3495dd5b3535a34013bae4b3eef3 [diff] |
aconfig: add aconfig_storage_metadata proto Introduce a new proto to capture storage file location for each container. This proto file will appeara as /metadata/aconfig/storage_file_location.pb. Storage service daemon is responsible for writing entires to it when a new storage file set is available. The flag read lib will use this file to find the corresponding storage file and mmap them. Bug: b/321077378 Test: atest aconfig_storage_file.test Change-Id: I226e76be895805dce52a075050dcd5b42d337be8
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.