@@ -94,12 +94,15 @@ for an example.
9494 * If `--spirv-builder-source` is set, then this is assumed to be a Git "commitsh", such
9595 as a Git commit hash or a Git tag, therefore anything that `git checkout` can resolve.
9696
97- --force-spirv-cli- rebuild
97+ --rebuild-codegen
9898 Force `rustc_codegen_spirv` to be rebuilt
9999
100100 --auto-install-rust-toolchain
101101 Assume "yes" to "Install Rust toolchain: [y/n]" prompt
102102
103+ --no-clear-target
104+ Clear target dir of `rustc_codegen_spirv` build after a successful build, saves about 200MiB of disk space
105+
103106 --force-overwrite-lockfiles-v4-to-v3
104107 There is a tricky situation where a shader crate that depends on workspace config can have
105108 a different `Cargo.lock` lockfile version from the the workspace's `Cargo.lock`. This can
@@ -148,12 +151,15 @@ for an example.
148151 * If `--spirv-builder-source` is set, then this is assumed to be a Git "commitsh", such
149152 as a Git commit hash or a Git tag, therefore anything that `git checkout` can resolve.
150153
151- --force-spirv-cli- rebuild
154+ --rebuild-codegen
152155 Force `rustc_codegen_spirv` to be rebuilt
153156
154157 --auto-install-rust-toolchain
155158 Assume "yes" to "Install Rust toolchain: [y/n]" prompt
156159
160+ --no-clear-target
161+ Clear target dir of `rustc_codegen_spirv` build after a successful build, saves about 200MiB of disk space
162+
157163 --force-overwrite-lockfiles-v4-to-v3
158164 There is a tricky situation where a shader crate that depends on workspace config can have
159165 a different `Cargo.lock` lockfile version from the the workspace's `Cargo.lock`. This can
0 commit comments