6 releases (breaking)

0.5.1+b9232f9 Mar 2, 2022
0.5.0+b9232f9 Feb 25, 2022
0.4.0+fc44652 Sep 28, 2021
0.3.0+688fc5c May 21, 2021
0.1.0 Oct 23, 2020

#109 in Build Utils

Download history 1929/week @ 2022-03-09 1820/week @ 2022-03-16 1485/week @ 2022-03-23 2204/week @ 2022-03-30 2167/week @ 2022-04-06 1207/week @ 2022-04-13 2098/week @ 2022-04-20 1802/week @ 2022-04-27 1831/week @ 2022-05-04 1951/week @ 2022-05-11 1517/week @ 2022-05-18 1071/week @ 2022-05-25 1686/week @ 2022-06-01 2528/week @ 2022-06-08 3040/week @ 2022-06-15 2307/week @ 2022-06-22

9,691 downloads per month
Used in 11 crates (via grpcio-sys)

MIT/Apache

15MB
474K SLoC

GNU Style Assembly 195K SLoC // 0.0% comments C 76K SLoC // 0.2% comments C++ 63K SLoC // 0.1% comments Assembly 62K SLoC // 0.0% comments Perl 56K SLoC // 0.1% comments Go 20K SLoC // 0.1% comments Python 1K SLoC // 0.3% comments Rust 140 SLoC // 0.0% comments Shell 134 SLoC // 0.3% comments Prolog 46 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