commit | 9fcaec6435a42cda37f3e8d4c5b8eed480c0e917 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Jun 06 19:30:32 2023 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 20 18:41:34 2023 +0000 |
tree | d9fc53a35a5f621508379ed84793eefe3acd9362 | |
parent | 50ee09552cde1c2019bef24520848d041920cfd4 [diff] |
Start recognizing the OPENSSL_NANOLIBC define nanolibc is an embedded platform with no threads. To start unforking that build, generalize some of the OPENSSL_TRUSTY defines. OpenSSL has OPENSSL_NO_SOCK if you don't have sockets and OPENSSL_NO_POSIX_IO if you don't have file descriptors. Those names are fine enough, so I've borrowed them here too. There's more to be done here, but this will clear out some of it. Change-Id: Iaba1fafdebb46ebb8f68b7956535dd0ccaaa832f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/60890 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@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: