mirrors/rust-lightning
1
0
Fork 0
mirror of https://github.com/lightningdevkit/rust-lightning.git synced 2025-02-24 06:57:53 +01:00
Code Issues Projects Releases Packages Wiki Activity

Drop the no-std feature from BP and drop feature implications

Browse source 
Now that we don't have to have everything in our entire ecosystem
use the same `std`/`no-std` feature combinations we should start by
untangling our own features a bit.

This takes the first step by removing the `no-std` feature entirely
from the `lightning-background-processor` crate and removing most
feature implications on dependencies from the remaining `std`
feature.

It also addresses a CI oversight where we were not testing
`lightning-background-processor` without the `std` feature in CI at
all.
This commit is contained in:
Matt Corallo 2024-08-16 19:07:05 +00:00
parent 9ca38c59f4
commit 5e37074246
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
ci/ci-tests.sh
View file

@ -63,6 +63,7 @@ fi
echo -e "\n\nTest futures builds"
cargo test -p lightning-background-processor --verbose --color always --features futures
cargo test -p lightning-background-processor --verbose --color always --features futures --no-default-features
echo -e "\n\nTest Custom Message Macros"
cargo test -p lightning-custom-message --verbose --color always

3
lightning-background-processor/Cargo.toml
View file

@ -15,8 +15,7 @@ rustdoc-args = ["--cfg", "docsrs"]
[features]
futures = [ ]
std = ["bitcoin/std", "lightning/std", "lightning-rapid-gossip-sync/std"]
no-std = ["lightning/no-std", "lightning-rapid-gossip-sync/no-std"]
std = []
default = ["std"]