|author||David Benjamin <email@example.com>||Wed Feb 27 12:01:15 2019 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Wed Feb 27 17:18:02 2019 +0000|
Add a reference for Linux ARM ABI. The Android NDK docs link to a ARM GNU/Linux Application Binary Interface Supplement document. Also fix a type in trampoline-armv4.pl. The generic ARM document is usually shortened AAPCS, not APCS. I couldn't find a corresponding link for aarch64. Change-Id: I6e5543f5c9e26955cd3945e9e7a5dcff27c2bd78 Reviewed-on: https://boringssl-review.googlesource.com/c/35064 Commit-Queue: David Benjamin <firstname.lastname@example.org> Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: