aboutsummaryrefslogtreecommitdiff
path: root/Cargo.example.toml
diff options
context:
space:
mode:
authorhuntc <[email protected]>2021-12-09 10:40:03 +1100
committerhuntc <[email protected]>2021-12-09 10:40:03 +1100
commit990d2330dbcec71bf72bdc116c390181f8d995cc (patch)
treea5bbc83c1f7a9cbcc61ff5fdce21c4ebaada194c /Cargo.example.toml
parent4eb9f0f3aebfa7b1d72830da2241b2a8b7ca139f (diff)
Rust Analyzer documentation
Intends to clarify how to make Embassy usable from within Visual Studio Code by assuming the presence of the Rust Analyzer. Note that IntelliJ does not support the Rust Analyzer, so an open question remains as to the whether this is a good move. If it turns out not to be a good move then we should still look at clarifying the use of a workspace file.
Diffstat (limited to 'Cargo.example.toml')
-rw-r--r--Cargo.example.toml93
1 files changed, 0 insertions, 93 deletions
diff --git a/Cargo.example.toml b/Cargo.example.toml
deleted file mode 100644
index 3fa8a32e9..000000000
--- a/Cargo.example.toml
+++ /dev/null
@@ -1,93 +0,0 @@
1# This file is a template for a Cargo workspace for developer convenience.
2#
3# Since Cargo resolves all features for all crates in the workspace together,
4# it is not possible to have a workspace with all the crates together, since they
5# enable incompatible features. For example, nrf crates enable embassy-macros/nrf
6# and stm32 crates enable embassy-macros/stm32. embassy-macros doesn't support having
7# both of these features on at the same time, because it makes no sense.
8#
9# Instead, we provide this template so you can enable only the crates you're going to
10# work on. This makes eg rust-analyzer check-on-save and autocomplete work, but only
11# in these crates, without any feature conflict.
12#
13# Copy this file to `Cargo.toml` and uncomment one group of crates below.
14#
15# `/Cargo.toml` is already in .gitignore, so you don't commit it accidentally.
16
17[workspace]
18resolver = "2"
19
20members = [
21 "embassy",
22 "embassy-traits",
23 "embassy-macros",
24 "embassy-hal-common",
25 "embassy-net",
26
27 # Uncomment ONLY ONE of the groups below.
28
29 # nRF
30 #"embassy-nrf",
31 #"examples/nrf",
32
33 # stm32
34 #"embassy-stm32",
35 #"stm32-metapac",
36 # uncomment ONLY ONE example crate.
37 #"examples/stm32f0",
38 #"examples/stm32f1",
39 #"examples/stm32f4",
40 #"examples/stm32f7",
41 #"examples/stm32g0",
42 #"examples/stm32h7",
43 #"examples/stm32l0",
44 #"examples/stm32l1",
45 #"examples/stm32l4",
46 #"examples/stm32wb55",
47 #"examples/stm32wl55",
48
49 # rp2040
50 #"embassy-rp",
51 #"examples/rp",
52
53 # std
54 #"examples/std",
55]
56
57exclude = [
58 # This is only built as a build-dependency, for the host. It shouldn't
59 # get built for the target.
60 "stm32-metapac-gen"
61]
62
63[profile.dev]
64codegen-units = 1
65debug = 2
66debug-assertions = true
67incremental = false
68opt-level = 3
69overflow-checks = true
70
71[profile.release]
72codegen-units = 1
73debug = 2
74debug-assertions = false
75incremental = false
76lto = "fat"
77opt-level = 's'
78overflow-checks = false
79
80# do not optimize proc-macro crates = faster builds from scratch
81[profile.dev.build-override]
82codegen-units = 8
83debug = false
84debug-assertions = false
85opt-level = 0
86overflow-checks = false
87
88[profile.release.build-override]
89codegen-units = 8
90debug = false
91debug-assertions = false
92opt-level = 0
93overflow-checks = false