Closed kristoferfannar-ks closed 1 week ago
We rely on the cargo metadata
command in the build script and it looks like it doesn't accept nightly flags (we're not forwarding them right now, but if we would it still shouldn't work). Can you try this instead? https://github.com/rust-lang/rustfmt/issues/5332#issuecomment-1119990254
You're correct, that worked!
# .cargo/config.toml
[unstable]
bindeps = true
Is enough to build the tauri app with binary dependencies
Running cargo +nightly build -p tauri-app -Z bindeps
now builds, with the binary dependency built as well.
Of course, cargo +nightly tauri build -Z bindeps
still doesn't accept the -Z flag.
Thank you!
Of course, cargo +nightly tauri build -Z bindeps still doesn't accept the -Z flag.
Generally you can try cargo +nightly tauri build -- -Z bindeps
- This way tauri will forward the args to the cargo build
call but not to cargo metadata
. That said, with the config.toml setting the -Z bindeps flag shouldn't be required anymore iirc 🤔
Yes you're correct. -Z bindeps
is no longer required with these changes in the config.toml.
Describe the bug
It seems that using the nightly RFC-3028,
bindeps
, to add binaries as build-dependencies makes my tauri application unable to build.The specific command I'm using is:
Which results in this error:
Running
cargo +nightly tauri build -Z bindeps
directly results in this error:The error directly above makes me think that Tauri doesn't support nightly flags, but as I've found no documentation supporting that, I decided to write up this issue just in case.
Reproduction
Minimal reproduction can be found in this repository: https://github.com/kristoferfannar-ks/tauri-bin-example
Steps to reproduce are in README
Expected behavior
I'd except the tauri application to compile the binary crate while building and finish compilation successfully.
Full
tauri info
outputStack trace
Additional context
Maybe this shouldn't be classified as a bug, as it might simply just not be implemented. Anyways, thanks for the time and attention!