milksad
/
rust-bitcoin-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity
rust-bitcoin-unsafe-fast/Cargo.toml

22 lines
389 B
TOML
Raw Normal View History

Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[workspace]
Add a new base58 crate Add a new `base58` crate to the workspace and move the `bitcoin::base58` module to it. Done as part of crate smashing, specifically so that we can make `bip32` into a separate crate.
2024-02-15 03:35:29 +00:00
members = ["bitcoin", "hashes", "internals", "fuzz", "io", "units", "base58"]
Update to edition 2021 We just bumped the MSRV to Rust 1.56.1 which includes edition 2021. Update all crates in this repo to use edition 2021 and build/lint warnings.
2023-11-14 22:14:56 +00:00
resolver = "2"
move bitcoin/fuzz into repo root; add to workspace This allows testing the fuzztests and making sure that they compile and tests pass, etc., just using `cargo test --all` in the root.
2023-03-22 02:15:30 +00:00
base58: Re-name crate to base58ck The current name `base58check` is taken, as is `base58`. Use `base58ck` instead. Add a brief section to the readme about the crate naming.
2024-02-25 21:43:46 +00:00
[patch.crates-io.base58ck]
Add a new base58 crate Add a new `base58` crate to the workspace and move the `bitcoin::base58` module to it. Done as part of crate smashing, specifically so that we can make `bip32` into a separate crate.
2024-02-15 03:35:29 +00:00
path = "base58"
move bitcoin/fuzz into repo root; add to workspace This allows testing the fuzztests and making sure that they compile and tests pass, etc., just using `cargo test --all` in the root.
2023-03-22 02:15:30 +00:00
[patch.crates-io.bitcoin]
path = "bitcoin"
Patch hashes and update the code This patches `bitcoin_hashes` to use the version in the repository and fixes the code after removal of `Deref`. This also turns off `AS_DEPENDENCY` check with the intention to refactor it later.
2022-12-15 19:52:07 +00:00
[patch.crates-io.bitcoin_hashes]
path = "hashes"
Remove path field from internals dependency We use two different methods for specifying local dependencies, `patch` and also `path`. There does not seem to be a reason why we use both, lets be uniform. Elect to use `patch` for all local crates.
2023-06-27 22:57:25 +00:00
[patch.crates-io.bitcoin-internals]
path = "internals"
Add a `bitcoin_io` crate In order to support standard (de)serialization of structs, the `rust-bitcoin` ecosystem uses the standard `std::io::{Read,Write}` traits. This works great for environments with `std`, however sadly the `std::io` module has not yet been added to the `core` crate. Thus, in `no-std`, the `rust-bitcoin` ecosystem has historically used the `core2` crate to provide copies of the `std::io` module without any major dependencies. Sadly, its one dependency, `memchr`, recently broke our MSRV. Worse, because we didn't want to take on any excess dependencies for `std` builds, `rust-bitcoin` has had to have mutually-exclusive `std` and `no-std` builds. This breaks general assumptions about how features work in Rust, causing substantial pain for applications far downstream of `rust-bitcoin` crates. Here, we add a new `bitcoin_io` crate, making it an unconditional dependency and using its `io` module in the in-repository crates in place of `std::io` and `core2::io`. As it is not substantial additional code, the `hashes` io implementations are no longer feature-gated. This doesn't actually accomplish anything on its own, only adding the new crate which still depends on `core2`.
2023-10-04 05:51:26 +00:00
[patch.crates-io.bitcoin-io]
path = "io"
Add bitcoin-units crate Add a new crate `bitcoin-units`, move the `amount` module over to it and re-export all types from `bitcoin::amount` so this as not a breaking change.
2023-08-08 08:47:05 +00:00
[patch.crates-io.bitcoin-units]
path = "units"