commit | abb183978473daf4ac4124e8f0fa561d3c1e2c59 | [log] [tgz] |
---|---|---|
author | Oriol Prieto Gascó <opg@google.com> | Fri Nov 15 20:11:57 2024 +0000 |
committer | Oriol Prieto Gascó <opg@google.com> | Fri Nov 15 20:11:57 2024 +0000 |
tree | 350b13606186ef0bcfa577c9131a67b6fa6e6a04 | |
parent | 6a1f24a24bed6eeb53bcc74c7e4ebeff14e85d6c [diff] |
Add --allow-read-write flag to aconfig This flag allows the user to specify whether or not to allow flags with READ_WRITE permission to be parsed. By default, the flag is set to true, which means that flags with READ_WRITE permission will be parsed. If the flag is set to false, then it is an error if flags with READ_WRITE permission are provided to the create-cache command. Bug: 377294922 Test: cargo test Change-Id: I48583a35e04d392fa7954d69e18884f2a7d46f35
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.