Mirror of BoringSSL (grpc依赖) https://boringssl.googlesource.com/boringssl
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
David Benjamin 690dcdf5c9 Make the old sk_* functions into full functions 1 year ago
..
src Make the old sk_* functions into full functions 1 year ago
CMakeLists.txt Don't copy all of bssl-sys into the CMake build directory 2 years ago
Cargo.toml - remove dependency on hex-literal crate 2 years ago
README.md Don't copy all of bssl-sys into the CMake build directory 2 years ago
build.rs Don't copy all of bssl-sys into the CMake build directory 2 years ago
rust_wrapper.c initial setup for bssl crate with hmac and sha2 bindings 2 years ago
rust_wrapper.h initial setup for bssl crate with hmac and sha2 bindings 2 years ago
wrapper.h Spell includes in wrapper.h like the rest of the project 2 years ago

README.md

bssl-sys

A low-level binding crate for Rust that moves in lockstop with BoringSSL. BoringSSL explicitly does not have a stable ABI, bssl-sys is the solution for preventing subtle-memory corruption bugs due to version skew.

How it works

bssl-sys uses bindgen as part of the cmake build process to generate Rust compatibility shims for the targeted platform. It is important to generate it for the correct platform because bindgen uses LLVM information for alignment which varies depending on architecture.

To Use

Build boringssl with -DRUST_BINDINGS=<rust-triple> and ensure that you have bindgen installed. The rust-triple option should match the Rust target triple when building bssl-sys.

From there, the bssl-sys crate can be built. By default, it looks for bindgen output and BoringSSL static libraries in the build directory. This can be reconfigured with BORINGSSL_BUILD_DIR environment variable. Note the environment variable is evaluated relative to rust/bssl-sys/src, so using an absolute path may be more convenient.