| commit | becb3ffccdecff83047285ebea20e5b85b2d65b1 | [log] [tgz] |
|---|---|---|
| author | Tom Hughes <tomhughes@chromium.org> | Tue Jan 09 16:21:53 2024 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 23 21:55:49 2024 +0000 |
| tree | 99785ccfa00b9583f09e29cc1c98c60f27825317 | |
| parent | 81138bc861023edda4816e1a89398f32c3b68e23 [diff] |
Fix threads detection for CROS_EC/CROS_ZEPHYR The CROS_EC and CROS_ZEPHYR platforms currently have threads disabled, so we should not attempt to search for (or link) a threads library. BUG=b/273639386 Change-Id: I094a989680160f9ecefbdb4cb3e94c4825a651e3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65568 Reviewed-by: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: