| commit | 1a8281ccc22d0351a35cf9735061c11d27398beb | [log] [tgz] |
|---|---|---|
| author | Zhi Dou <zhidou@google.com> | Wed Dec 20 21:04:10 2023 +0000 |
| committer | Zhi Dou <zhidou@google.com> | Wed Jan 03 15:53:01 2024 +0000 |
| tree | ddf5835d1a112936ebd929cb5e94fa8232673a9b | |
| parent | 2e137a99636b16f8295312ec074f14fc26a716d0 [diff] |
aconfig: add new codegen mode force_read_only The "force_read_only" mode is designed for libraries shared among multiple containers for the following two scenarios where: 1. The library must be built with read_only flags or 2. Different containers requires different values for the same flags. In this mode, the library includes only non-exported flags, adhering to the concept that exported flags should maintain consistent values across containers. Additionally, regardless of their original permissions, all flags within this mode will be set to read_only. Bug: 316357759 Test: atest aconfig.test Change-Id: I65df39416c96404d84044a46bbcfe1bc8ce9ba8f
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.