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
| Clean only `release`, `debug` or `docs`| no (not yet) | yes |
76
76
| Real `cargo clean` command under the hood | no | yes |
77
+
| Keep executables in an extra directory | yes | no |
77
78
78
79
Note that `cargo-clean-recursive` uses the actual `cargo clean` command under the hood instead of
79
80
simply deleting the target directories. This gies makes the cleaning work exactly as intended by
@@ -98,7 +99,9 @@ Options:
98
99
-t, --threads <THREADS> The number of threads to use for directory scaning. 0 automatically selects the number of threads [default: 0]
99
100
-v, --verbose Show access errors that occur while scanning. By default those errors are hidden
100
101
-i, --interactive Use the interactive project selection. This will show a selection of all cleanable projects with the possibility to manually select or deselect
101
-
--ignore <IGNORE> Directories that should be ignored by default, including subdirectories. This will still detect the projects in those directories, but mark them to not be cleaned
102
+
--ignore <IGNORE> Directories that should be ignored by default, including subdirectories. This will still detect the projects in those directories, but mark them to not be cleaned. To actually skip scanning directories, use --skip instead. The directories can be specified as absolute paths or relative to the workdir
103
+
-e, --keep-executable Keeping compiled executables in release, debug and cross-compilation directories. Moves the executable to a new folder outside of target
104
+
--skip <SKIP> Directories that should be fully skipped during scanning, including subdirectories. This will speed up the scanning time by not doing any reads for the specified directories. The directories can be specified as absolute paths or relative to the workdir
0 commit comments