80b97c8318
The logic is stolen from cmake-rs, and it is important to follow it as we will need to look for CMAKE_TOOLCHAIN_FILE the same way cmake-rs does. When checking for env variable BORING_BSSL_PATH during a cross build for target x86_64-unknown-linux-gnu, boring-sys build script will attempt to read: BORING_BSSL_PATH_x86_64-unknown-linux-gnu BORING_BSSL_PATH_x86_64_unknown_linux_gnu TARGET_BORING_BSSL_PATH BORING_BSSL_PATH |
||
|---|---|---|
| .github/workflows | ||
| boring | ||
| boring-sys | ||
| hyper-boring | ||
| scripts | ||
| tokio-boring | ||
| .gitignore | ||
| .gitmodules | ||
| .rusty-hook.toml | ||
| Cargo.toml | ||
| README.md | ||
| RELEASE_NOTES | ||
| THIRD_PARTY | ||
| cliff.toml | ||
README.md
boring
BoringSSL bindings for the Rust programming language and TLS adapters for tokio and hyper built on top of it.
Documentation
- Boring API: https://docs.rs/boring
- tokio TLS adapters: https://docs.rs/tokio-boring
- hyper HTTPS connector: https://docs.rs/hyper-boring
- FFI bindings: https://docs.rs/boring-sys
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed under the terms of both the Apache License, Version 2.0 and the MIT license without any additional terms or conditions.
Accolades
The project is based on a fork of rust-openssl.