Expect `pending_msg_events` to be in random peer order in tests

[rust-lightning] / Cargo.toml

diff --git a/Cargo.toml b/Cargo.toml
index 8290e28efe1b71be73e055e02b707092ea2fa69d..89b92a8c6e4ba4e6a7bbd230d0e721230a552e6f 100644 (file)
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,21 +1,34 @@
-[package]
-name = "lightning"
-version = "0.0.1"
-authors = ["Matt Corallo"]
-license = "AGPL-3.0"
-repository = "https://github.com/TheBlueMatt/rust-lightning/"
-description = """
-A Bitcoin Lightning implementation in Rust.
-Still super-early code-dump quality and is missing large chunks. See README in git repo for suggested projects if you want to contribute. Don't have to bother telling you not to use this for anything serious, because you'd have to finish building it to even try.
-"""
+[workspace]
 
-[features]
-# Supports tracking channels with a non-bitcoin chain hashes. Currently enables all kinds of fun DoS attacks.
-non_bitcoin_chain_hash_routing = []
+members = [
+    "lightning",
+    "lightning-block-sync",
+    "lightning-invoice",
+    "lightning-net-tokio",
+    "lightning-persister",
+    "lightning-background-processor",
+    "lightning-rapid-gossip-sync"
+]
 
-[dependencies]
-bitcoin = "0.10.7"
-rust-crypto = "0.2"
-rand = "0.3"
-secp256k1 = "0.8.1"
-num = "0.1"
+exclude = [
+    "no-std-check",
+]
+
+# Our tests do actual crypto 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