commit | 95799b056ed36ffff5382fe79613e40ab99a426b | [log] [tgz] |
---|---|---|
author | Janis Danisevskis <jdanis@google.com> | Fri Sep 11 09:47:45 2020 -0700 |
committer | Janis Danisevskis <jdanis@google.com> | Wed Oct 28 19:40:51 2020 -0700 |
tree | 1bd6eb284e3574fce2679bc45815c7c707877d06 | |
parent | b979b79bd95937a55b806fb1b6210babce2ca0d7 [diff] |
Add keystore2 to PLATFORM_PACKAGES Add keystore 2 to the PLATFORM_PACKAGES in anticipation for the Keystore 2.0 migration. This builds and installs keystore2 on the device, but it does not get started yet. Staring keystore2 is currently controlled with the platform property ro.android.security.keystore2.enable=true. Bug: 171305684 Test: keystore2 builds and is present on the device but does not start unconditionally. Change-Id: Id92cb2aa38022516067853d89d6c3210db1100a8
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.