You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-3Lines changed: 13 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -232,9 +232,11 @@ Note that if `CARGO_TARGET_DIR` (see https://doc.rust-lang.org/cargo/reference/e
232
232
is specified in the environment, it takes precedence over `targetDirectory`, as cargo will output
233
233
all build artifacts to it, regardless of what is being built, or where it was invoked.
234
234
235
+
You may also override `CARGO_TARGET_DIR` variable by setting `rust.cargoTargetDir` in `local.properties`, however it seems very unlikely that this will be useful, as we don't pass this information to cargo itself. That said, it can be used to control where we search for the built library on a per-machine basis.
236
+
235
237
```groovy
236
238
cargo {
237
-
// Note: path is relative to the gradle project root.
239
+
// Note: path is relative to the gradle project's `projectDir`
0 commit comments