commit | fd95f097fe20679c8da2c9928026d4b6e5d95aaf | [log] [tgz] |
---|---|---|
author | Peter Collingbourne <pcc@google.com> | Fri Mar 24 11:34:24 2023 -0700 |
committer | Peter Collingbourne <pcc@google.com> | Fri Mar 24 16:39:17 2023 -0700 |
tree | 056e3d7187b196effa04637348ce39b0cdf76ee3 | |
parent | 1c117c5faba9dc1a7e23ec1a5e6b3b742e478782 [diff] |
Make kernel prebuilts writable after copying them. Images created by Bazel are read-only, which leads to build failures when later commands attempt to modify them, as the cp command will also copy the file permissions. Fix it by using chmod to make the images writable after copying them. Change-Id: I8aaa7c4395d38b674f76a7f0ebfa95e1f2da0af0
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.