#secp256k1 #libsecp256k1 #ffi

sys cashweb-secp256k1-sys

FFI for Pieter Wuille’s libsecp256k1 library

2 unstable releases

Uses old Rust 2015

0.3.1 Dec 31, 2020
0.1.2 Jul 1, 2020

#6 in #libsecp256k1

Download history 19/week @ 2022-10-11 14/week @ 2022-10-18 39/week @ 2022-10-25 47/week @ 2022-11-01 44/week @ 2022-11-08 39/week @ 2022-11-15 21/week @ 2022-11-22 17/week @ 2022-11-29 44/week @ 2022-12-06 20/week @ 2022-12-13 36/week @ 2022-12-20 27/week @ 2022-12-27 4/week @ 2023-01-03 25/week @ 2023-01-10 22/week @ 2023-01-17 51/week @ 2023-01-24

110 downloads per month
Used in 8 crates (via cashweb-secp256k1)

CC0 license

455KB
9K SLoC

C 7K SLoC // 0.1% comments Rust 1K SLoC // 0.1% comments GNU Style Assembly 742 SLoC // 0.1% comments Automake 143 SLoC Shell 111 SLoC // 0.1% comments

cashweb-secp256k1-sys

This crate provides Rust definitions for the FFI structures and methods.

Vendoring

The default build process is to build using the vendored libsecp256k1 sources in the depend folder. These sources are prefixed with a special cashweb-secp256k1-sys-specific prefix rustsecp256k1_v1_2_3_.

This prefix ensures that no symbol collision can happen:

  • when a Rust project has two different versions of cashweb-secp256k1 in its depepdency tree, or
  • when cashweb-secp256k1 is used for building a static library in a context where existing libsecp256k1 symbols are already linked.

To update the vendored sources, use the vendor-libsecp.sh script:

$ ./vendor-libsecp.sh depend <version-code> <rev>
  • Where <version-code> is the cashweb-secp256k1-sys version number underscored: 0_1_2.
  • Where <rev> is the git revision of libsecp256k1 to checkout.

Linking to external symbols

If you want to compile this library without using the bundled symbols (which may be required for integration into other build systems), you can do so by adding --cfg=rust_secp_no_symbol_renaming' to your RUSTFLAGS variable.

Dependencies