boringssl-src-rs's Introduction

boringssl-src

A crate for building boringssl.

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

To use the crate, just include it as build-dependency:

[build-dependencies]
boringssl-src = "0.6"

And then build it in build script:

let artifact = boringssl_src::Build::new().build();

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.

boringssl-src-rs's People

Contributors

Stargazers

Watchers

boringssl-src-rs's Issues

Source code does not match crates.io release

Hello 👋!

I had a weird bug in my code:

   Compiling boringssl-src v0.3.0+688fc5c
error[E0599]: no method named `get_profile` found for struct `Config` in the current scope
  --> /home/hugdev01/.cargo/registry/src/github.com-1ecc6299db9ec823/boringssl-src-0.3.0+688fc5c/src/lib.rs:99:31
   |
99 |             let profile = cfg.get_profile();
   |                               ^^^^^^^^^^^ method not found in `Config`

error: aborting due to previous error

I am not yet sure why this is happening but it went away with a lot of cargo clean and cargo update.
However I realised two things while working on it:

the source code in this repo does not seem to watch the release 0.3.0+688fc5c on crates.io
the code calls the method get_profile() on Config which has only been available since cmake version 0.1.45 so I think the cmake version field in Cargo.toml should be 0.1.45 insted of 0.1. I am thinking the error above is because a wrong version of cmake was chosen in my dependency tree but not 100% sure.