remove target dir after successful rustc_codegen_spirv build, saves 200MiB

Author: Firestar99

crates/cargo-gpu/src/args.rs

@@ -71,6 +71,11 @@ pub struct InstallArgs {
     #[clap(long, action)]
     pub auto_install_rust_toolchain: bool,
 
+    /// Clear target dir of `rustc_codegen_spirv` build after a successful build, saves about
+    /// 200MiB of disk space.
+    #[clap(long = "no-clear-target", default_value = "true", action = clap::ArgAction::SetFalse)]
+    pub clear_target: bool,
+
     /// There is a tricky situation where a shader crate that depends on workspace config can have
     /// a different `Cargo.lock` lockfile version from the the workspace's `Cargo.lock`. This can
     /// prevent builds when an old Rust toolchain doesn't recognise the newer lockfile version.

crates/cargo-gpu/src/install.rs

@@ -188,15 +188,18 @@ package = "rustc_codegen_spirv"
                 })
                 .context("running build command")?;
 
-            let dylib_path = checkout
-                .join("target")
-                .join("release")
-                .join(&dylib_filename);
+            let target = checkout.join("target");
+            let dylib_path = target.join("release").join(&dylib_filename);
             if dylib_path.is_file() {
                 log::info!("successfully built {}", dylib_path.display());
                 if !source_is_path {
                     std::fs::rename(&dylib_path, &dest_dylib_path)
                         .context("renaming dylib path")?;
+
+                    if self.spirv_install.clear_target {
+                        log::warn!("clearing target dir {}", target.display());
+                        std::fs::remove_dir_all(&target).context("clearing target dir")?;
+                    }
                 }
             } else {
                 log::error!("could not find {}", dylib_path.display());