| commit | 235ee97b469ca6761e5096ea829f4da032c591fe | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 01 10:39:44 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 01 17:26:06 2023 +0000 |
| tree | fed99f1e5659b01de329513838328f7319d00fd8 | |
| parent | 5a3eb9ea7e787b7a787b7a6529d181d7e1fdb54e [diff] |
Reland "Build with C11 on MSVC in the standalone Bazel build" This reverts 1e2f1696636088626cb223aa5a10f64e07b62ffd. Bazel 6.3 has since been released, which includes a fix for https://github.com/bazelbuild/bazel/issues/15073. Envoy and gRPC have both since updated to this Bazel version. The policies in https://opensource.google/documentation/policies/cplusplus-support#build_systems also imply a minimum Bazel version of 6.3.2. I'm thinking we let this bake for a little while, to catch any unexpected issues, and then, if it sticks, we try to go ahead and require C11 across the board. Update-Note: If using Bazel with MSVC, and the build fails with something like "Command line error D8016 : '/std:c++20' and '/std:c11' command-line options are incompatible", you are likely running into the above Bazel bug. Update to Bazel 6.3 or later. Bug: 623, 624 Change-Id: I8baa99392ca47bc7580bc2930e7f4b16beced91e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62905 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: