| commit | 66d8563227085a59bbe44ef32068aaec87cc8f6c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Mar 07 10:17:43 2022 -0500 |
| committer | Adam Langley <agl@google.com> | Tue Mar 08 13:55:00 2022 +0000 |
| tree | 91c7d24e6c9500f49413866298d0f51f56386901 | |
| parent | 6e25e54b1c0f20791f77b4ba9ba03be0e4618ff6 [diff] |
Limit the pthread_rwlock workaround to glibc. Most libcs seem to be reasonable. Bionic (Android) always makes pthread_rwlock_t. Reportedly, NetBSD does too. Default to assuming libcs are reasonable and treat glibc as the exception. Update-Note: If there are non-glibc libcs with similarly problematic headers, this may break the build. Let us know if it does. Fixed: 482 Change-Id: I63052cad7693d9e28d98775205fe7688e262d88c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/51685 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: