Closed hYdos closed 1 year ago
This might just be a cargo quirk, can't this be changed via the .cargo/config.toml file? Does this happen without gradle-rust? I don't see any issue in your screenshot unfortunately.
it doesnt happen without gradle-rust and i have the .cargo/config.toml
To be honest I don't really see what could've caused this, the plugin basically just wraps the command execution in a pretty bundle, so the only thing I could think off is you having different defaults that somehow aren't passed through?
I haven't touched rustc in a hot minute, is there a way to debug log (both with and without gradle-rust) which linker (exact path) rustc is trying to use? (logs or screenshots at your convenience)
Also could you please show the error that you're getting when compiling with gradle-rust?
Hey :wave:, any update on this issue?
give me 2 seconds to setup a project to test this again
Will reopen if updated :3
So i've been modifying the example to build win64, linux64, mac64, and macArm64 and for some reason cargo is trying to link with cc which I dont have installed on my machine. I've never had the issue with cargo and was wondering if there is anything i can do in my buildscript to fix it
My native subproject buildscript: