| commit | 436f1368cd53353d9f54a9f1495300340b0d46df | [log] [tgz] |
|---|---|---|
| author | Zhi Dou <zhidou@google.com> | Mon Jun 24 21:14:15 2024 +0000 |
| committer | Zhi Dou <zhidou@google.com> | Mon Jun 24 21:14:52 2024 +0000 |
| tree | e7315fcbe6a21814952695ddfcb0ae8b087e3ba8 | |
| parent | 4c47a8925eb20848dca5c075c44761669553575c [diff] |
flush mmap file to disk after updating The change was applied in the file in memory. Without explicitly calling msync, there is no guarantee that the changes are written back to disk. Thus the flag value may not be changed. Bug: b/348693143 Test: atest aconfig_storage_write_api.test.cpp aconfig_storage_write_api.test.rust Change-Id: I8b1e0cbbb90bcb3c2e5bbf418a6a1a9cd047c81b
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.