Describe the problem
Right now, one has to name their binary the same as the crate name in order for Tauri's default tooling to work with it
Describe the solution you'd like
I'd like to set the binary name in tauri.conf.json and use that appropriately (--binary {val} for Cargo commands and {name}[.ext] for the output).
Alternatives considered
No response
Additional context
Reason I have multiple binaries is because we have multiple deployment/install strategies, one backed by Axum the other by Tauri, each a thin wrapper around the library. It's awkward to have "Project" vs "Project Web" vs "Project API" when we want to treat the first two as equal.
Describe the problem
Right now, one has to name their binary the same as the crate name in order for Tauri's default tooling to work with it
Describe the solution you'd like
I'd like to set the binary name in
tauri.conf.jsonand use that appropriately (--binary {val}for Cargo commands and{name}[.ext]for the output).Alternatives considered
No response
Additional context
Reason I have multiple binaries is because we have multiple deployment/install strategies, one backed by Axum the other by Tauri, each a thin wrapper around the library. It's awkward to have "Project" vs "Project Web" vs "Project API" when we want to treat the first two as equal.