Cargo Features
bitcoind-json-rpc-regtest has no features set by default.
[dependencies]
bitcoind-json-rpc-regtest = { version = "0.3.0", features = ["download", "26_0", "25_2", "25_1", "25_0", "24_2", "24_1", "24_0_1", "23_2", "23_1", "23_0", "22_1", "22_0", "0_21_2", "0_20_2", "0_19_1", "0_18_1", "0_17_1", "doc"] }
Please note, in this crate the version features are mutally exclusive.
cargo test --all-features
is the same ascargo test --features=v26_0
cargo test --no-default-features
usesv26_0
also.
- download 0_17_1? 0_18_1? 0_19_1? 0_20_2? 0_21_2? 22_0? 22_1? 23_0? 23_1? 23_2? 24_0_1? 24_1? 24_2? 25_0? 25_1? 25_2? 26_0? = bitcoin_hashes, flate2, minreq, tar, zip
-
download is not supposed to be used directly only through selecting one of the version feature
Affects
bitcoind-json-rpc-regtest::downloaded_exe_path
… - 26_0 = 25_2, download
-
We support all minor releases (but only the latest patch release).
Affects
versions::VERSION
… - 25_2 26_0? = 25_1, download
-
Affects
versions::VERSION
… - 25_1 25_2? = 25_0, download
-
Affects
versions::VERSION
… - 25_0 25_1? = 24_2, download
-
Affects
versions::VERSION
… - 24_2 25_0? = 24_1, download
-
Affects
versions::VERSION
… - 24_1 24_2? = 24_0_1, download
-
Affects
versions::VERSION
… - 24_0_1 24_1? = 23_2, download
-
Affects
versions::VERSION
… - 23_2 24_0_1? = 23_1, download
-
Affects
versions::VERSION
… - 23_1 23_2? = 23_0, download
-
Affects
versions::VERSION
… - 23_0 23_1? = 22_1, download
-
Affects
versions::VERSION
… - 22_1 23_0? = 22_0, download
-
Affects
versions::VERSION
… - 22_0 22_1? = 0_21_2, download
-
Affects
versions::VERSION
… - 0_21_2 22_0? = 0_20_2, download
-
We only support the latest minor version for these.
Affects
versions::VERSION
… - 0_20_2 0_21_2? = 0_19_1, download
-
Affects
versions::VERSION
… - 0_19_1 0_20_2? = 0_18_1, download
-
Affects
versions::VERSION
… - 0_18_1 0_19_1? = 0_17_1, download
-
Affects
versions::VERSION
… - 0_17_1 0_18_1? = download
-
Affects
versions::VERSION
… - doc
-
used only for documentation building
Features from optional dependencies
In crates that don't use the dep:
syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality may be removed in the future.