| commit | cb47fdc0e18b771e669882c865c6db81e3bd6bb4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Feb 14 17:34:22 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 15 17:11:22 2024 +0000 |
| tree | 5dc997586d87c5e3f677d07201e5fb9df5d46c5e | |
| parent | a028a23fe5fe8390389b05d2740f0576908fe25d [diff] |
Switch to bindgen's static inline support This removes the need to hand-write rust_wrapper.c, because bindgen can generate it for us. bindgen 0.65 or later is needed. Earlier versions of this were buggy. I've also removed the claim that bssl-sys is somehow a solution for version skew. That was the original thinking from Android, but it hasn't worked out. The version skew solution is simply "use bindgen, don't handwrite bindings". Android are quite behind their originaly July timeline for adding the build half of this mechanism, but as this is now in the way of other work, we're going to proceed with using this now. There is now a unsupported_inline_wrappers cfg that Android can set to use the old mechanism. Update-Note: Rust support now requires your build correctly handle --wrap-static-fns. On Android, you will need to enable the unsupported_inline_wrappers cfg option until b/290347127 is fixed. Chromium doesn't actually use any of the inline functions yet, so we can handle --wrap-static-fns asynchronously, but I have a CL ready to enable that. Fixed: 596 Change-Id: I51fd1108a8c17a06f1bdd9171ebf352cea871723 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/58985 Auto-Submit: 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: