commit | 808bf915a8827d67be6912caf9cc49013dd8ab90 | [log] [tgz] |
---|---|---|
author | Dennis Shen <dzshen@google.com> | Wed Mar 13 18:12:25 2024 +0000 |
committer | Dennis Shen <dzshen@google.com> | Wed Mar 13 20:29:13 2024 +0000 |
tree | 13b4936bf9e9ab93ae5ecc2bfe9e761c22d07ff1 | |
parent | 71f9303dc0131deed737d13d6fac1adb41b4ee71 [diff] |
aconfig: update aconfig_storage_read_api c++ lib Now the read api lib no longer owns the memory mapped file. The rust lib aconfig_storage_read_api api to get memory mapped file just returns an Mmap rust struct. However cxx does not support Mmap data type, so we cannot export the api to get memory mapped file from rust to c++. This means we have to implement c++ apis to get memory mapped files. This change is basically implementing c++ api to get memory mapped files, mirroring the rust implementation. In addition, the integration test is also updated to lock down the new c++ api implementation. Bug: b/321077378 Test: atest aconfig_storage_read_api.test.cpp Change-Id: I5e93a220cdd05cc0e5b0eb441284ac3e9dc34da7
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.