| commit | 89b87f6aa902c05fafbd657444d9f71886423678 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Thu Jun 01 10:23:05 2023 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Jun 01 17:28:25 2023 +0000 |
| tree | 32a34e87f8d0f2d918770143ddb63c4eb5acd9ba | |
| parent | cfc5f5e9fdf87ad281d383bc9b8eb32437ba5436 [diff] |
Open ab_partitions.txt with just read access We don't actually need write permission, so going with least privilege principle. We have observed some mysterious permission denied errors on server environments. Without detailed logs or access to the server it's hard to pinpoint what the root cause is. This is an attempt/hypothesis to fix the permission denied error. Test: th Bug: 283033491 Change-Id: I52dc360d593aab57c749109994bf3e1e3625d0ce
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.