mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-02-24 15:02:20 +01:00
f041a64fca
To ensure no-std is honored across dependencies, add a crate depending on lightning crates supporting no-std. This should ensure any regressions are caught. Otherwise, cargo doesn't seem to catch some incompatibilities (e.g., f64::log10 unavailable in core) and seemingly across other dependencies as describe here: https://blog.dbrgn.ch/2019/12/24/testing-for-no-std-compatibility/
33 lines
741 B
TOML
33 lines
741 B
TOML
[workspace]
|
|
|
|
members = [
|
|
"lightning",
|
|
"lightning-block-sync",
|
|
"lightning-invoice",
|
|
"lightning-net-tokio",
|
|
"lightning-persister",
|
|
"lightning-background-processor",
|
|
]
|
|
|
|
exclude = [
|
|
"no-std-check",
|
|
]
|
|
|
|
# Our tests do actual crypo and lots of work, the tradeoff for -O1 is well worth it.
|
|
# Ideally we would only do this in profile.test, but profile.test only applies to
|
|
# the test binary, not dependencies, which means most of the critical code still
|
|
# gets compiled as -O0. See
|
|
# https://doc.rust-lang.org/cargo/reference/profiles.html#profile-selection
|
|
[profile.dev]
|
|
opt-level = 1
|
|
panic = "abort"
|
|
|
|
[profile.release]
|
|
opt-level = 3
|
|
lto = true
|
|
panic = "abort"
|
|
|
|
[profile.bench]
|
|
opt-level = 3
|
|
codegen-units = 1
|
|
lto = true
|