@@ -45,22 +45,14 @@ Automatically refresh project info via `cargo metadata` on
45
45
--
46
46
Run build scripts (`build.rs` ) for more precise code analysis.
47
47
--
48
- [[rust-analyzer.cargo.buildScripts.invocationLocation]]rust-analyzer.cargo.buildScripts.invocationLocation (default: `"workspace"` )::
49
- +
50
- --
51
- Specifies the working directory for running build scripts.
52
- - "workspace": run build scripts for a workspace in the workspace's root directory.
53
- This is incompatible with `#rust-analyzer.cargo.buildScripts.invocationStrategy#` set to `once` .
54
- - "root": run build scripts in the project's root directory.
55
- This config only has an effect when `#rust-analyzer.cargo.buildScripts.overrideCommand#`
56
- is set.
57
- --
58
48
[[rust-analyzer.cargo.buildScripts.invocationStrategy]]rust-analyzer.cargo.buildScripts.invocationStrategy (default: `"per_workspace"` )::
59
49
+
60
50
--
61
51
Specifies the invocation strategy to use when running the build scripts command.
62
- If `per_workspace` is set, the command will be executed for each workspace.
63
- If `once` is set, the command will be executed once.
52
+ If `per_workspace` is set, the command will be executed for each Rust workspace with the
53
+ workspace as the working directory.
54
+ If `once` is set, the command will be executed once with the opened project as the
55
+ working directory.
64
56
This config only has an effect when `#rust-analyzer.cargo.buildScripts.overrideCommand#`
65
57
is set.
66
58
--
@@ -75,8 +67,7 @@ option.
75
67
If there are multiple linked projects/workspaces, this command is invoked for
76
68
each of them, with the working directory being the workspace root
77
69
(i.e., the folder containing the `Cargo.toml` ). This can be overwritten
78
- by changing `#rust-analyzer.cargo.buildScripts.invocationStrategy#` and
79
- `#rust-analyzer.cargo.buildScripts.invocationLocation#` .
70
+ by changing `#rust-analyzer.cargo.buildScripts.invocationStrategy#` .
80
71
81
72
By default, a cargo invocation will be constructed for the configured
82
73
targets and features, with the following base command line:
@@ -209,16 +200,6 @@ List of `cargo check` (or other command specified in `check.command`) diagnostic
209
200
210
201
For example for `cargo check` : `dead_code` , `unused_imports` , `unused_variables` ,...
211
202
--
212
- [[rust-analyzer.check.invocationLocation]]rust-analyzer.check.invocationLocation (default: `"workspace"` )::
213
- +
214
- --
215
- Specifies the working directory for running checks.
216
- - "workspace": run checks for workspaces in the corresponding workspaces' root directories.
217
- This falls back to "root" if `#rust-analyzer.check.invocationStrategy#` is set to `once` .
218
- - "root": run checks in the project's root directory.
219
- This config only has an effect when `#rust-analyzer.check.overrideCommand#`
220
- is set.
221
- --
222
203
[[rust-analyzer.check.invocationStrategy]]rust-analyzer.check.invocationStrategy (default: `"per_workspace"` )::
223
204
+
224
205
--
@@ -250,8 +231,7 @@ Cargo, you might also want to change
250
231
If there are multiple linked projects/workspaces, this command is invoked for
251
232
each of them, with the working directory being the workspace root
252
233
(i.e., the folder containing the `Cargo.toml` ). This can be overwritten
253
- by changing `#rust-analyzer.check.invocationStrategy#` and
254
- `#rust-analyzer.check.invocationLocation#` .
234
+ by changing `#rust-analyzer.check.invocationStrategy#` .
255
235
256
236
If `$saved_file` is part of the command, rust-analyzer will pass
257
237
the absolute path of the saved file to the provided command. This is
0 commit comments