| commit | 61d8c5a79912954891e8897e1bbe7553106e9b8d | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Mon Mar 04 20:01:44 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Mon Mar 04 21:12:43 2024 +0000 |
| tree | bd4caab888408ba75cf7a5b92bddc21652c32d56 | |
| parent | 279e018b0a32aa3510c87685a8de68edf9ac1cf3 [diff] |
aconfig: split aconfig_storage_file crate Current aconfig_storage_file crate contains two things: 1, aconfig storage file definition (which is used by aconfig crate for storage file creation) and 2, flag storage file read api. With this change, we are splitting 2 into its own crate aconfig_storage_read_api In the long run, there will be 3 crates for aconfig_storage 1, aconfig_storage_file It contains aconfig storage file definition, as well as a binary to help print/dump aconfig storage binary files into some readable format. 2, aconfig_storage_read_api This crate contains flag read apis. This crate depends on aconfig_storge_file crate. This crate will be used by codegen. 3, aconfig_storage_write_api This crate contains flag write apis. This crate depends on aconfig_storage_file crate. This crate will only be used by aconfig daemon to update flag values. Bug: b/321077378 Test: atest aconfig_storage_read_api.test; atest aconfig_storage_file.test; atest aconfig_storage_read_api.test.rust; atest aconfig_storage_read_api.test.cpp Change-Id: Ia6afdc40a45c7c59652fbfd123c2b77bf6666dd9
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.