| commit | e28c732521a7beb668e742e85634a201d8ce1223 | [log] [tgz] |
|---|---|---|
| author | Pete Bentley <prb@google.com> | Thu Sep 26 15:59:41 2019 +0100 |
| committer | Pete Bentley <prb@google.com> | Mon Sep 30 20:38:05 2019 +0100 |
| tree | a58760be73ca0b98a231dcef08a57f258f4a1e2b | |
| parent | 1f9387ae01ac5941a3158c1c9cfaa1e6201339a5 [diff] |
Install BoringSSL self test binaries to vendor image. Required in order to run test self test for the vendor copy of libcrypto.so which may differ from the one in /system and so will use differently name flag files in order to avoid running the BoringSSL Known Answer Tests on every process startup, impacting system health. Bug: 141150335 Test: TH Change-Id: I1db922379a59fa66fc65b6d92d370f33a2c65799 Merged-In: I1db922379a59fa66fc65b6d92d370f33a2c65799 (cherry picked from commit e3ab8eab257f170d52368cc796e7b4e54b60d695)
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.