| commit | e5dd91bca7d6cca4cd6d642df775be5d8cc79b34 | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Tue May 28 17:04:02 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Thu May 30 00:32:42 2024 +0000 |
| tree | 8fb3a192cbc3bda6cba98d08826d290a1020a801 | |
| parent | 8a402d7e30e0b92931b3cd93f6d1f87b4e9018b5 [diff] |
aconfig: create first implementation of aconfig storage java read api 1, See AconfigStorageReadAPI.java to see java APIs to map storage files and read flag values. It is using fast native annotation, in theory it should be faster than regular JNI without much of the overhead. 2, The java api calls into Rust wrapper in srcs/lib.rs, note that MappedByteBuffer is not copied during JNI. In the rust side implementation we get the underlying raw pointer and buffer size and reconstruct a rust slice. However, at current implmentation, the string input such as package name and flag name are most likely copied. They are converted from JStirng to JavaStr first without copy, then the into() call to convert it to Rust string. We could potentially optimize it to without copy. 3, Add an android_test target to lock down the API behaviors. Bug: b/321077378 Test: atest -c Change-Id: I8915fe70e8eb341be563c70f85e19e644e8aa6be
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.