| commit | cbfe4f5a8e3cc26dc679b5058c7b18f2e1d6eba4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Oct 18 13:45:16 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Oct 18 19:01:20 2018 +0000 |
| tree | 88f2f6f40272883c82e9c21bba4e2d78f140199a | |
| parent | dd412c428ad7c2a60ae4709dfbad6301e499dcb8 [diff] |
Remove support for GCC 4.7. This reverts https://boringssl-review.googlesource.com/24924. As noted there, GCC 4.7 support ends 2018-03-23, which has passed. GCC 4.8.0 was released 2013-03-22, so we are now past the five year mark, matching Abseil's guidelines. Abseil also now explicitly lists supported compilers and explicitly requires GCC 4.8+. https://abseil.io/docs/cpp/platforms/platforms gRPC also now requires 4.8 per https://github.com/grpc/grpc/issues/10036#issuecomment-290248204 Update-Note: On the off chance someone was using GCC 4.7, which only started working in January, that'll no longer work. Change-Id: Ie017822e903f98293e7b5e9bda10f104f17be7b3 Reviewed-on: https://boringssl-review.googlesource.com/c/32564 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@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: