rust-lightning/Cargo.toml

[workspace]

members = [
    "lightning",
    "lightning-block-sync",
    "lightning-net-tokio",
    "lightning-persister",
]

# 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"
Use workspaces to separate crates 2019-11-15 02:44:30 +00:00			`[workspace]`
initial checkin 2017-12-25 01:05:27 -05:00
Use workspaces to separate crates 2019-11-15 02:44:30 +00:00			`members = [`
			`"lightning",`
Add lightning-block-sync package and library Defines an interface and related types for fetching block headers and data from a block source (e.g., Bitcoin Core). Used to keep lightning in sync with chain activity. 2021-01-11 10:50:54 -08:00			`"lightning-block-sync",`
Use workspaces to separate crates 2019-11-15 02:44:30 +00:00			`"lightning-net-tokio",`
Add a sample module FilesystemPersister. Intended to be a cross-platform implementation of the channelmonitor::Persist trait. This adds a new lightning-persister crate, that uses the newly exposed lightning crate's test utilities. Notably, this crate is pretty small right now. However, due to future plans to add more data persistence (e.g. persisting the ChannelManager, etc) and a desire to avoid pulling in filesystem usage into the core lightning package, it is best for it to be separated out. Note: Windows necessitates the use of OpenOptions with the `write` permission enabled to `sync_all` on a newly opened channel's data file. 2020-09-16 17:46:11 -04:00			`"lightning-persister",`
Use workspaces to separate crates 2019-11-15 02:44:30 +00:00			`]`
Move test profile to crate root, so it has effect again 2019-11-28 01:19:54 -05:00
Fix passing -O1 to build from `cargo test` In 9e03087d6acbc876a5ad1c9b9d8746bf18d5ca86 we started setting `opt-level` only on profile.test and not profile.dev. When that commit was authored I tested only that rustc was being called with opt-level set in its flags, not that the resulted run ran at the speed I expected. It seems profile.test isn't applied properly to dependencies or so, resulting in tests running much slower than they do at profile.dev.opt-level=1. 2020-10-05 12:47:08 -04:00			`# 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`
Specify panic = abort in profiles for lightning-c-bindings 2020-09-01 16:11:39 -04:00			`[profile.dev]`
Fix passing -O1 to build from `cargo test` In 9e03087d6acbc876a5ad1c9b9d8746bf18d5ca86 we started setting `opt-level` only on profile.test and not profile.dev. When that commit was authored I tested only that rustc was being called with opt-level set in its flags, not that the resulted run ran at the speed I expected. It seems profile.test isn't applied properly to dependencies or so, resulting in tests running much slower than they do at profile.dev.opt-level=1. 2020-10-05 12:47:08 -04:00			`opt-level = 1`
Specify panic = abort in profiles for lightning-c-bindings 2020-09-01 16:11:39 -04:00			`panic = "abort"`

LTO in release mode by default, which is really critical for C libs 2020-05-15 21:27:51 -04:00			`[profile.release]`
			`opt-level = 3`
			`lto = true`
Specify panic = abort in profiles for lightning-c-bindings 2020-09-01 16:11:39 -04:00			`panic = "abort"`