#custom cargo profile
14 messages · Page 1 of 1 (latest)
As far as I can tell that's not what it's complaining about
because it doesn't support so it cannot find the correct path of the cargo build output
the actual cargo build output:
Try restarting your computer, because if I remember correctly when this has happened to me in the past, it's related to a process locking the file from being renamed
I looked the source, it's not support custom profile
There's an open feature request somewhere
Ah right, we picked it up from discord straight into a PR now that you mention it
umm, but seems the fix is about conflict --release and custom --profile, rather than the target_dir
both dev and next:
https://github.com/tauri-apps/tauri/blob/next/tooling/cli/src/interface/rust.rs#L1004-L1018