| commit | 31f1466a613774369053a94eabbae38fb9cbb7f9 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Jan 29 15:17:38 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 01 20:07:18 2023 +0000 |
| tree | 1604725c59318a99ce62a7417a16d3767ddbce42 | |
| parent | a1c79226137e8f60ed572dabdd2435f1f942be0f [diff] |
Move OpenSSLConfig.cmake into the cmake/ directory We've already put perlasm.cmake in there. I figure CMake helper files can go in there. It also seems to match what other projects too. Change-Id: Ief6b10cf4e80b8d4b52ca53b90aa425b32037e52 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56566 Auto-Submit: David Benjamin <davidben@google.com> 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: