pre-built binaries: Update readme and fix clippy
This commit is contained in:
parent
2e8ad14f59
commit
c5010de2af
15
README.md
15
README.md
|
|
@ -9,9 +9,20 @@ and [hyper](https://github.com/hyperium/hyper) built on top of it.
|
|||
|
||||
## Release Support
|
||||
|
||||
The crate statically links with the latest BoringSSL master branch.
|
||||
By default, the crate statically links with the latest BoringSSL master branch.
|
||||
|
||||
### Contribution
|
||||
## Support for pre-built binaries
|
||||
|
||||
While this crate can build BoringSSL on its own, you may want to provide pre-built binaries instead.
|
||||
To do so, specify the environment variable `BORING_BSSL_PATH` with the path to the binaries.
|
||||
|
||||
You can also provide specific headers by setting `BORING_BSSL_INCLUDE_PATH`.
|
||||
|
||||
_Notes_: The crate will look for headers in the `$BORING_BSSL_INCLUDE_PATH/openssl/` folder, make sure to place your headers there.
|
||||
|
||||
_Warning_: When providing a different version of BoringSSL make sure to use a compatible one, the crate relies on the presence of certain functions.
|
||||
|
||||
## Contribution
|
||||
|
||||
Unless you explicitly state otherwise, any contribution intentionally
|
||||
submitted for inclusion in the work by you, as defined in the Apache-2.0
|
||||
|
|
|
|||
|
|
@ -200,7 +200,7 @@ fn main() {
|
|||
|
||||
let include_path = PathBuf::from(
|
||||
std::env::var("BORING_BSSL_INCLUDE_PATH")
|
||||
.unwrap_or(String::from("deps/boringssl/src/include")),
|
||||
.unwrap_or_else(|_| String::from("deps/boringssl/src/include")),
|
||||
);
|
||||
|
||||
let mut builder = bindgen::Builder::default()
|
||||
|
|
|
|||
Loading…
Reference in New Issue