| commit | b64277de4c194d8b6931f8637534c5d9611a1105 | [log] [tgz] |
|---|---|---|
| author | Max Bires <jbires@google.com> | Wed Mar 28 15:48:13 2018 -0700 |
| committer | Hung-ying Tyan <tyanh@google.com> | Thu Jul 26 14:35:32 2018 +0800 |
| tree | be0e8ff2bbd1e54468e0e2aee00cbe72578aaa48 | |
| parent | 6ac13c77c7dfdfa6542eb0d88f98f82fe439b069 [diff] |
Adding VENDOR_SECURITY_PATCH to vendor partition build.prop This will add ro.vendor.build.security_patch to /vendor/build.prop on device Bug: 76428542 Test: ro.vendor.build.security_patch entry shows up under /vendor/build.prop Change-Id: I3d3ec2d0e76fc5e62cd283ed4bce3894423cabdd Merged-In: I4f783e996cb425a49c2b12ae4f364e12c6ca7784 (cherry picked from 56d444b98fab77ffb990c3e67776e5adc203c419)
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.