7 releases (4 breaking)

0.5.2+6195bf8 Feb 16, 2023
0.5.1+b9232f9 Mar 2, 2022
0.5.0+b9232f9 Feb 25, 2022
0.4.0+fc44652 Sep 28, 2021
0.1.0 Oct 23, 2020

#45 in Build Utils

Download history 3650/week @ 2022-11-29 4068/week @ 2022-12-06 2398/week @ 2022-12-13 1425/week @ 2022-12-20 1377/week @ 2022-12-27 3709/week @ 2023-01-03 3956/week @ 2023-01-10 2447/week @ 2023-01-17 3296/week @ 2023-01-24 3861/week @ 2023-01-31 3055/week @ 2023-02-07 3503/week @ 2023-02-14 3854/week @ 2023-02-21 4050/week @ 2023-02-28 4170/week @ 2023-03-07 4655/week @ 2023-03-14

17,109 downloads per month
Used in 12 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.5"
  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