-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathCargo.toml
More file actions
171 lines (165 loc) · 6.93 KB
/
Copy pathCargo.toml
File metadata and controls
171 lines (165 loc) · 6.93 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
[workspace]
resolver = "2"
members = [
"crates/fbuild-core",
"crates/fbuild-config",
"crates/fbuild-paths",
"crates/fbuild-packages",
"crates/fbuild-packages-fetch",
"crates/fbuild-library",
"crates/fbuild-toolchain",
"crates/fbuild-serial",
"crates/fbuild-build",
"crates/fbuild-build-engine",
"crates/fbuild-build-esp",
"crates/fbuild-build-arm",
"crates/fbuild-build-mcu",
"crates/fbuild-deploy",
"crates/fbuild-daemon",
"crates/fbuild-cli",
"crates/fbuild-python",
"crates/fbuild-test-support",
"crates/fbuild-header-scan",
"crates/fbuild-library-select",
"bench/fastled-examples",
]
# Custom dylints have their own nightly toolchain pin (see
# `dylints/*/rust-toolchain.toml`) and must not be part of the
# stable workspace build — `cargo dylint --all` builds them with
# the pinned nightly via the discovery below. See #264.
exclude = [
"dylints/ban_raw_subprocess",
"dylints/ban_raw_path_prefix_compare",
"dylints/ban_std_pathbuf",
"dylints/ban_unrooted_tempdir",
"dylints/ban_direct_serialport",
"dylints/ban_file_based_locks",
"dylints/ban_deploy_tool_direct_invocation",
"dylints/ban_process_exit_outside_main",
"dylints/ban_unwrap_in_production",
"dylints/cli_no_build_deploy_direct_use",
"dylints/require_multi_thread_flavor_when_spawning",
"dylints/ban_std_sync_mutex_in_async",
# FastLED/fbuild#844 bridge sweep — 10 net-new lints landing
# together with the matching internal bridge APIs.
"dylints/ban_bare_reqwest",
"dylints/ban_std_fs_in_async",
"dylints/ban_tokio_fs_direct_import",
"dylints/ban_std_thread_sleep",
"dylints/ban_std_mpsc_in_async_reachable",
"dylints/ban_tokio_mpsc_direct_import",
"dylints/ban_std_fs_canonicalize",
"dylints/ban_runtime_new_outside_main",
"dylints/ban_poison_panic",
"dylints/ban_print_in_production",
# FastLED/fbuild#840 initializer-order sweep — convention-based
# checks for env-var mutation and OnceLock installation outside
# binary entry points. MIR-based dataflow check is a follow-up.
"dylints/ban_env_var_set_after_import",
"dylints/require_oncelock_install_before_use",
# FastLED/fbuild#911 — bans hand-rolled '.replace(\\, /)'
# backslash-to-slash rewrites on path-shaped strings, directing
# callers at fbuild_core::path::NormalizedPath::display_slash().
# Companion to ban_std_pathbuf. Filed after PRs #890 and #912 both
# had to patch the same anti-pattern at yet another call site.
"dylints/ban_manual_slash_normalize",
]
[workspace.metadata.dylint]
libraries = [{ path = "dylints/*" }]
[workspace.package]
version = "2.5.3"
edition = "2021"
rust-version = "1.94.1"
license = "MIT OR Apache-2.0"
repository = "https://github.com/fastled/fbuild"
[workspace.dependencies]
tokio = { version = "1", features = ["rt-multi-thread", "macros", "net", "sync", "time", "process", "io-util", "fs", "signal"] }
serde = { version = "1", features = ["derive"] }
serde_json = "1"
thiserror = "2"
tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
clap = { version = "4", features = ["derive"] }
axum = { version = "0.7", features = ["ws"] }
tower-http = { version = "0.5", features = ["cors", "trace"] }
hyper = { version = "1", features = ["full"] }
reqwest = { version = "0.12", default-features = false, features = ["json", "blocking", "stream", "rustls-tls"] }
semver = "1"
tokio-serial = "5"
# `usbportinfo-interface` exposes `UsbPortInfo.interface` (the composite
# `MI_xx` index), used by fbuild-serial's Windows enumerator to disambiguate
# multi-function devices (e.g. Teensy Serial vs Serial+MIDI). FastLED/fbuild#962.
serialport = { version = "4", default-features = false, features = ["usbportinfo-interface"] }
pyo3 = { version = "0.29", features = ["abi3-py310"] }
tempfile = "3"
filetime = "0.2"
sha2 = "0.10"
regex = "1"
walkdir = "2"
tree-sitter = "0.26.9"
tree-sitter-cpp = "0.23.4"
flate2 = "1"
tar = "0.4"
zip = { version = "2", default-features = false, features = ["deflate"] }
xz2 = "0.1"
bzip2 = "0.5"
zstd = "0.13"
bytes = "1"
uuid = { version = "1", features = ["v4"] }
base64 = "0.22"
futures = "0.3"
tokio-tungstenite = "0.24"
async-trait = "0.1"
dashmap = "6"
blake3 = "1"
criterion = { version = "0.5", default-features = false, features = ["html_reports"] }
mimalloc = "0.1"
object = { version = "0.36", default-features = false, features = ["read", "std", "elf", "write"] }
rusqlite = { version = "0.31", features = ["bundled"] }
shell-words = "1"
bincode = "1"
# USB identity data is fetched from FastLED/boards at runtime. Do not add a
# catalogue dependency here; dependency checks run through `soldr cargo`.
# prost: hand-derived `#[derive(prost::Message)]` payload structs for the
# fbuild v1 broker request/response lane (no .proto/build.rs needed). Pinned
# to the version running-process 4.3.0 re-exports so the wire types stay
# compatible. See crates/fbuild-daemon/src/broker.
prost = "0.14"
# fbuild-daemon binds the running-process backend endpoint directly so the
# broker can verify and route to versioned daemon processes.
interprocess = "2.4.2"
rayon = "1"
tracing-test = "0.2"
# Terminal coloring for `fbuild build --shrink` reporting (FastLED/fbuild#493).
# Auto-disables on non-tty and respects `NO_COLOR`, so the same code is safe
# to call from anywhere — no `--color` flag plumbing needed.
owo-colors = "4"
# Process containment: all subprocess spawns the daemon performs (compilers,
# esptool, qemu, simavr, node, npm, …) and any grandchildren they fork must
# die with the daemon. See FastLED/fbuild#32.
# Migrated from `running-process-core 3.4` to `running-process 4.x` after
# the upstream mono-crate consolidation.
#
# v1 broker adoption (zackees/running-process#437 / FastLED/fbuild#510):
# `fbuild-daemon`'s `broker` module adopts the frozen v1 broker session API
# (`#433`) for daemon discovery + version negotiation, so we now enable the
# `client-async` feature (fbuild-daemon is a tokio runtime —
# `AsyncBrokerSession::adopt`). The `core` feature stays on for process
# containment. `RUNNING_PROCESS_DISABLE=1` still selects the legacy direct
# loopback-HTTP path (see crates/fbuild-daemon/src/broker).
running-process = { version = "4.5.7", default-features = false, features = ["client-async"] }
[profile.dev]
debug = "line-tables-only"
# Cargo's dev defaults: opt-level = 0 for first-party (fast compile +
# fast link), incremental = true (cargo + linker keep state across
# builds), codegen-units = 256 (parallel compile units). We accept
# those for our own crates so `pip install`/`uv sync` rebuilds finish
# quickly when iterating.
# Optimize third-party deps even in dev so runtime perf doesn't tank
# just because we want a fast local-rebuild loop. Cargo compiles each
# upstream crate exactly once and caches it, so this only costs the
# first build — every subsequent rebuild of fbuild's source is still
# the fast dev-profile path.
[profile.dev.package."*"]
opt-level = 3
debug = false