milksad
/
rust-secp256k1-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity

move the note to the main readme

This commit is contained in:
Andronik Ordian 2020-03-16 11:45:09 +01:00
parent 420eb38034
commit 37b9e2dfe9
No known key found for this signature in database
GPG Key ID: C66F3C680DE0E6ED
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -21,3 +21,9 @@ Contributions to this library are welcome. A few guidelines:
* No new dependencies, please. * No new dependencies, please.
* No crypto should be implemented in Rust, with the possible exception of hash functions. Cryptographic contributions should be directed upstream to libsecp256k1. * No crypto should be implemented in Rust, with the possible exception of hash functions. Cryptographic contributions should be directed upstream to libsecp256k1.
* This library should always compile with any combination of features on **Rust 1.22**. * This library should always compile with any combination of features on **Rust 1.22**.
## A note on Rust 1.22 support
The build dependency `cc` might require a more recent version of the Rust compiler.
To ensure compilation with Rust 1.22.0, pin its version in your `Cargo.lock`
with `cargo update -p cc --precise 1.0.41`.

6
secp256k1-sys/README.md
View File

@ -26,12 +26,6 @@ $ ./vendor-libsecp.sh depend <version-code> <rev>
- Where `<version-code>` is the secp256k1-sys version number underscored: `0_1_2`. - Where `<version-code>` is the secp256k1-sys version number underscored: `0_1_2`.
- Where `<rev>` is the git revision of libsecp256k1 to checkout. - Where `<rev>` is the git revision of libsecp256k1 to checkout.
## Note
The build dependency `cc` might require a recent version of the rust compiler.
If you want to compile it with rust 1.22.0, pin its version in your `Cargo.lock`
with `cargo update -p cc --precise 1.0.41`.
## Linking to external symbols ## Linking to external symbols
For the more exotic use cases, this crate can be used with existing libsecp256k1 For the more exotic use cases, this crate can be used with existing libsecp256k1