commit | 7e9e06a7393298c65a2a33e0cb3d13e957c06e4a | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Jul 17 13:50:56 2017 -0400 |
committer | Steven Valdez <svaldez@google.com> | Mon Jul 17 20:53:15 2017 +0000 |
tree | 2309bfa4db36a6049aeb363123daf558afdc2fc7 | |
parent | c5304e4f3b795a6a351b9500f8cae1e2c2ffb61c [diff] |
Use OPENSSL_UNUSED in OPENSSL_COMPILE_ASSERT. This would also have fixed the Windows clang issues. Those kicked in because Windows clang defines __clang__ and not __GNUC__, but OPENSSL_UNUSED accounts for this. It's also shorter. Change-Id: I75bc17bbb789c5b78a7a369c43194e146739f574 Reviewed-on: https://boringssl-review.googlesource.com/18004 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.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: