| commit | 36e85b6a05fe185f6b3a1b7e609e8b775c9b5a81 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Mar 18 13:58:15 2024 +1000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 22 04:15:32 2024 +0000 |
| tree | ab56b49364a5b770827d42a62140bc508ae4e166 | |
| parent | 821fe3380cce646fa3557b882d91fba318981b9b [diff] |
Flatten crypto/fipsmodule/CMakeLists.txt up a layer This is one step towards flattening the libcrypto build into the top-level CMakeLists.txt file. (This is to align the CMake build with our other builds, and also make it easier to consume a CRYPTO_SOURCES variable without having to prepend "../" in front of each value.) This also avoids a rather annoying corner of CMake: files generated in a different directory don't work well, which is why we had all this mess with EXTERNAL_OBJECT, GENERATED, and bcm_o_target. Globbing it into one file is a bit unwieldy, but avoids this. (CMake is incredibly bad at custom rules.) Bug: 542 Change-Id: Ia5038511af339a0eae2af56875a42581eb1ed15b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/67287 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@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: