| commit | f961de5c47ed265c3e758ec70dd15ece20809962 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Apr 18 17:39:00 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 20 17:53:00 2022 +0000 |
| tree | b1e0960c72ce67f7d52e016280dbfd5fb3fb4f4b | |
| parent | 493d5cbedda8690d17a323d3532acfb1fb1845ad [diff] |
Try to require C11 (in non-MSVC compilers). MSVC is a little behind, but otherwise we should be able to assume C11 support in all our compilers. The only C99 builds should just be stale build files. Such consumers are leaving performance on the table, by using the worse refcounting implementation. For now, don't require it in public headers. Android's build is still defaulting to C99, which means requiring C11 will be disruptive. We can try the public headers after that's fixed. Update-Note: If the build fails with an error about C11, remove -std=c99 or -std=gnu99 from your build. Refcounting will get faster. Change-Id: I2ec6f7d7acc026a451851d0c38f60c14bae6b00f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52247 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@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.
Project links:
There are other files in this directory which might be helpful: