| commit | 28e4a1b838b2ffbf9e2151ae5fcfffe5ab0ffac0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jun 23 15:29:16 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 27 16:58:21 2023 +0000 |
| tree | a467d12ee3f1d2ccbcb6e2d7ba29f91a719cfae8 | |
| parent | 286ea215ec6669152feb71a28075ae69b957f4bf [diff] |
Build with C11 on MSVC in the standalone Bazel build We require MSVC 2019 now, which has a /std:c11 flag. Enable it to match the CMake build and remove a blocker for requiring C11 unconditionally. (This select branch is also used by clang-cl. I had meant to figure out the @bazel_tools business as part of this, but it turns out clang-cl works better with the MSVC flags than the GCC ones anyway. -Wall in clang-cl is like MSVC's /Wall and actually means all warnings. Ideally we'd still condition this on the compiler, in case anyone uses MinGW, but we can figure that out later.) Tested with bazelisk build :all and bazelisk build --compiler=clang-cl :all on Windows. Change-Id: I4559789a221071eef39f9d34929f0e9c5994119e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61127 Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: 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: