|author||David Benjamin <firstname.lastname@example.org>||Mon Jan 13 18:14:07 2020 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Jan 13 23:50:48 2020 +0000|
Detect the NDK path from CMAKE_TOOLCHAIN_FILE. The NDK toolchain file uses either ANDROID_NDK or CMAKE_TOOLCHAIN_FILE, so look at both. In particular, our builders don't pass in ANDROID_NDK. Change-Id: Ic7fabdbd16adc3d38389d338b38839b67dde6523 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39544 Commit-Queue: David Benjamin <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> Reviewed-by: Adam Langley <email@example.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: