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

44 lines
968 B
TOML
Raw Normal View History

Embedded test via qemu
2021-05-15 15:12:27 +00:00
[package]
authors = ["Riccardo Casatta <riccardo@casatta.it>", "Dev Random <c1.devrandom@niftybox.net>"]
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
edition = "2021"
Embedded test via qemu
2021-05-15 15:12:27 +00:00
readme = "README.md"
name = "embedded"
version = "0.1.0"
Import bitcoin_hashes crate into hashes We would like to bring the `bitcoin_hashes` crate into the `rust-bitcoin` repository. Import `bitcoin_hashes` into `rust-bitocin/hashes`, doing so looses all the commit history from the original crate but if we archive the original repository then the history will be preserved. We maintain the same version number obviously and in the changelog we note the change of repository. Commit hash that was tip of `bitcoin_hashes` at time of import: commit 54c16249e06cc6b7870c7fc07d90f489d82647c7 Includes making `embedded` and `fuzzing` per-crate i.e., move them into `bitcoin` as hashes includes these also. NOTE: Does _not_ enable fuzzing for `hashes` in CI. Notes on CI: Attempts to merge in the github actions from the hashes crate however reduces coverage by not running hashes tests for beta toolchain. Some additional work could be done to improve the CI to increase efficiency without reducing coverage. Leaving for another day.
2022-09-16 01:52:57 +00:00
# Prevent this from interfering with workspaces
[workspace]
members = ["."]
Embedded test via qemu
2021-05-15 15:12:27 +00:00
[dependencies]
cortex-m = "0.6.0"
cortex-m-rt = "0.6.10"
cortex-m-semihosting = "0.3.3"
panic-halt = "0.2.0"
alloc-cortex-m = "0.4.1"
Remove no-std feature Currently `bitcoin` cannot be built with no features enabled, it must have either "no-std" or "std" enabled. This is an artifact from when we depended on `core2` for "no-std", now that we have our own `io` crate and we unconditionally depend on it we can remove the "no-std" feature.
2023-11-28 03:22:24 +00:00
bitcoin = { path="../", default-features = false, features = ["secp-lowmemory"] }
Embedded test via qemu
2021-05-15 15:12:27 +00:00
[[bin]]
name = "embedded"
test = false
bench = false
[profile.release]
codegen-units = 1 # better optimizations
debug = true # symbols are nice and they don't increase the size on Flash
lto = true # better optimizations
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
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
[patch.crates-io.base58check]
path = "../../base58"
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"
Add patch section to test crates In order to keep the embedded and schemacs test crates building when we update their local transient dependencies we need to use a `patch` section. - For `bitcoin/embedded` add `patch` section for `internals`, `hashes` already has an entry. - For `hashes/embedded` add `patch` section for `internals`. - For `hashes/extendend_tests/schemars` add `patch` section for `internals`. FTR for direct local dependencies we use a `path` field when specifying the dependency.
2023-06-27 23:25:21 +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"