| commit | 741c153370f58dbf73c6680c8f37de656bc2cb3c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Jan 25 17:37:16 2023 -0500 |
| committer | Adam Langley <agl@google.com> | Tue Jan 31 18:53:52 2023 +0000 |
| tree | ddd28866743513cde40e8a9241846916550a9b8f | |
| parent | 8a69c0d4f8f412432f80dd36ee5987fb1675bfbc [diff] |
Align the generated CMake build with the main one. Having two of these is tedious and I hope, eventually, we can align them. But for now, sync them manually: - Bump the minimum CMake versions to match - Align the C/C++ version directives - Simplify architecture detection - Trim some Windows defines that date to our overly aggressive warnings - Use the Threads package - Only use _XOPEN_SOURCE on Linux because it's a glibc-specific problem. I've tested this manually, but we don't particularly test this build right now (I forget if anyone is even using it), so this is mostly relying on finding out from others if it breaks something. In the long term, we should merge the two CMake builds. Bug: 542 Change-Id: Icccc466464306967275d29a6982c0e9859fc972c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56445 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: 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: