commit | e8484f2160f3e7265a5de2c38cf91a2e76288d41 | [log] [tgz] |
---|---|---|
author | Janis Danisevskis <jdanis@google.com> | Thu Jan 23 16:57:31 2020 -0800 |
committer | Janis Danisevskis <jdanis@google.com> | Fri Jan 24 14:44:36 2020 -0800 |
tree | 4a2761fbbc05cfd62653d01b628f52c36f546071 | |
parent | cb0e97750a1fc244e9f035f1a555ff00f2ddeaf8 [diff] |
Remove keymaster libraries from VNDK These keymaster libraries constitute a service to vendors who want/need to implement a keymaster trusted app, or want to wrap an older keymaster HAL when updating an older device to a newer Android version. It is not necessary to implement or link against these libraries to be Android or Treble compliant. Many vendors have completely independent implementations of keymaster. Vendors should be able to provide there own versions of these libraries or ship without them entirely. /system does not depend on /vendor to have a compatible version of these libraries. Test: N/A Bug: 139955894 Merged-In: I9286b36d26f09e26763df17758f9bec9e2b60ec8 Change-Id: I9286b36d26f09e26763df17758f9bec9e2b60ec8
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.