4 releases (breaking)

0.4.0+fc44652 Sep 28, 2021
0.3.0+688fc5c May 21, 2021
0.2.0 Jan 21, 2021
0.1.0 Oct 23, 2020
Download history 1736/week @ 2021-07-03 2007/week @ 2021-07-10 1871/week @ 2021-07-17 1977/week @ 2021-07-24 1892/week @ 2021-07-31 1880/week @ 2021-08-07 2080/week @ 2021-08-14 1857/week @ 2021-08-21 2005/week @ 2021-08-28 1921/week @ 2021-09-04 2983/week @ 2021-09-11 2573/week @ 2021-09-18 2194/week @ 2021-09-25 1985/week @ 2021-10-02 2413/week @ 2021-10-09 2117/week @ 2021-10-16

8,790 downloads per month
Used in 12 crates (via grpcio-sys)

MIT/Apache

16MB
505K SLoC

GNU Style Assembly 194K SLoC // 0.0% comments C 76K SLoC // 0.2% comments C++ 66K SLoC // 0.1% comments Assembly 62K SLoC // 0.0% comments Perl 56K SLoC // 0.1% comments Go 50K SLoC // 0.1% comments Python 1K SLoC // 0.3% comments Rust 138 SLoC // 0.0% comments Shell 134 SLoC // 0.3% comments Prolog 42 SLoC

boringssl-src

A crate for building boringssl.

This crate is intended to integrate with other build script to build boringssl.

  1. To use the crate, just include it as build-dependency:
[build-dependencies]
boringssl-src = "0.2"
  1. And then build it in build script:
let artifact = boringssl_src::Build::new().build();
  1. If you just need to link it to your library, then let it setup directly:
artifacts.print_cargo_metadata();

If you want to make it available to existing build system, take CMake as an example, you can setup by using OPENSSL_ROOT_PATH:

let config = cmake::Config::new("native project");
config.define("OPENSSL_ROOT_DIR", format!("{}", boringssl_artifact.root_dir().display()));

Then cmake should be able to find the library by find_package(OpenSSL).

How and When is boringssl updated?

It's updated periodically. It for now serves as a build dependency for tikv/grpc-rs, so whenever grpc updates boringssl, this crate also updates the native dependency.

Dependencies