[wyvernbw]

currently cargo-gpu-install (and by extension cargo-gpu) fail if you use a custom target directory (for example i use a shared target dir across all my projects, set in ~/.cargo/config.toml). this pr makes it so the install falls back to the target directory that's given by cargo-metadata if the target/release/{dylib_filename} file is missing.

[Firestar99]

I don't quite understand the purpose of this patch. If you're compiling the codegen backend crate rustc_codegen_spirv, you're doing so with a specific rustc version. Switching rustc versions always requires a clean build, so your global build cache aint't doing anything if you don't have other projects fixed to the same rustc version. And it won't share with the spirv target either, since every target is getting it's own subdirectory.

[wyvernbw]

i think you misunderstood, the compilation automatically puts artifacts in the shared target directory and cargo-gpu-install fails to find them at all because it only looks in the hardcoded, relative target/release path. You'd have to temporarily disable the global cargo config to get around it. The purpose isn't to share a build cache between targets. And you're right that I messed up when the check happens

EDIT: I think a much better solution would actually be to use cargo's --target-dir arg to force it to use the right path

[wyvernbw]

I changed the install code to pass --target-dir to cargo, which makes it ignore the global target dir config, so it works properly and the artifacts are in the same place for everyone. I think this a way cleaner approach