| commit | c37e64cba55256dff3ca4575dfcac1cfb2aa111e | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Thu May 30 16:13:39 2019 -0700 |
| committer | Adam Langley <agl@google.com> | Thu May 30 23:41:34 2019 +0000 |
| tree | 436cb6d2ab4065fa9b30a3115002dee3af13f0e9 | |
| parent | 326f12135b7e226af1fd1a5f24ee040d78a6aa2d [diff] |
Handle fips_shared_support.c getting built in other builds. Other build systems will just take a list of the files, including fips_shared_support.c, so better to make it a no-op in the non-shared+FIPS case. Also add it to the other cases so that the CMake build better matches other builds in that respect. Change-Id: I1bea4f6b8266da32340a5fc0fed5fc3680f3b18f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36264 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.
There are other files in this directory which might be helpful: