Cargo: only depend on criterion when building benchmarks

This is a bit of a hack as it requires setting `--features bench` when invoking `cargo bench`, but it allows us to avoid pulling in criterion when building tests and examples, which reduces the number of dependencies for those build in half.
cloudflare · Feb 10, 2020 · 4100cec · 4100cec
1 parent 464d8e7
commit 4100cec
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/Cargo.toml b/Cargo.toml
@@ -46,6 +46,10 @@ fuzzing = []
 # For building with Android NDK < 18 and GCC.
 ndk-old-gcc = []
 
+# Build benchmarks. This is intended to make benchmark-specific dependencies
+# optional, so we don't have to build them for other targets.
+bench = ["criterion"]
+
 [package.metadata.docs.rs]
 default-features = false
 
@@ -56,6 +60,7 @@ cmake = "0.1"
 log = { version = "0.4", features = ["std"] }
 libc = "0.2"
 ring = "0.16"
+criterion = { version = "0.3", optional = true }
 lazy_static = "1"
 
 [target."cfg(windows)".dependencies]
@@ -65,7 +70,6 @@ winapi = { version = "0.3", features = ["wincrypt"] }
 mio = "0.6"
 url = "1"
 docopt = "1"
-criterion = "0.3"
 env_logger = "0.6"
 
 [profile.bench]
@@ -80,3 +84,4 @@ crate-type = ["lib", "staticlib", "cdylib"]
 [[bench]]
 name = "benches"
 harness = false
+required-features = ["bench"]