| commit | ec55dc15d3a39e5f1a58bfd79148729f38f6acb4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Mar 05 02:24:32 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Mar 05 20:49:21 2018 +0000 |
| tree | 161f4bebc54d5715e11366e1cb7c29b6014d0a01 | |
| parent | 929a9d7d425ff219bc0480db5f877cbd99f69f91 [diff] |
Update tools. Also remove the -Wtautological-constant-compare logic. I believe Clang has since removed that problematic warning from -Wall and that check was causing problems when we were embedded as a subproject in a project that didn't set CMP0025. (In that case, by the time our build file ran, the compiler had already been detected and the damage done. This unfortunately means the next Clang version check will hit the same issue, but let's deal with that when we get there.) Change-Id: Iea5f262899b74c5b84f707f4cf4ac4b3540c4acb Reviewed-on: https://boringssl-review.googlesource.com/26375 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: