How do I make Tauri work on projects with multiple bins?

[m4heshd]

My project has multiple bins. One of them is the Tauri client. But how do I tell Tauri which bin to worry about?

Here's what I have so far. This is how I do it on all the other Rust projects.

Directory structure:

.
└── src-tauri/
    └── src/
        ├── bin/
        │   ├── client/
        │   │   └── main.rs
        │   └── pack/
        │       └── main.rs
        ├── lib.rs
        ├── module_one.rs
        └── module_two.rs

Cargo.toml:

[[bin]]
name = "Client"
path = "src/bin/client/main.rs"

[[bin]]
name = "Pack"
path = "src/bin/pack/main.rs"

package.json:

"scripts": {
    "dev": "vite",
    "build": "vite build",
    "preview": "vite preview",
    "tauri-dev": "tauri dev -- --bin Client",
    "tauri-build": "tauri build -- --bin Client"
  }

This works fine when using npm run tauri-dev but npm run tauri-build fails with the following error.

Error failed to bundle project: Failed to get main binary

How do I make Tauri treat the Client bin as its main binary?

[m4heshd]

Error failed to bundle project: Failed to get main binary

Managed to get rid of this error by using default-run = "Client" in Cargo.toml, but the packaging process still looks for other binaries. I know I can use a custom nsi template and stuff but it would be great to simply exclude a specific list of binaries in the Tauri config.

[KevinT3Hu]

Have you found a solution on this? Furthermore my other bin is not being built while runningpnpm tauri dev so I can't use it properly.

[m4heshd]

@KevinT3Hu It's been a long time, and I can't remember exactly what workaround I ended up using. I'll update here if I manage to dig it up.

[echelon]

@KevinT3Hu, we run a Rust/Nx monorepo with several frontend projects and 30+ Rust crates in a single Cargo workspace, including 2 Tauri apps. There are some levers for this, but we hope the Tauri team adds more:

export TAURI_FRONTEND_PATH="path/to/your/frontend"
export TAURI_APP_PATH="path/to/your/crate"

cargo tauri dev --config "path/to/your/config/override.toml"

Note (1): You can't use TOML files in CI as the Github action is written using the Javascript flavor CLI instead of the Rust one, and it doesn't understand TOML.

Note (2): If you're using Cargo workspaces, the path to your crate is not the workspace root, but the crate root.

Note (3): Switching Javascript build directives must be done from the config file as there's no environment variable override.

These configurations are cumbersome and make building, testing in dev mode, bundling, etc. a little error prone and nasty. I hope the team adds a nice way to configure and maintain multiple sets of build configurations.

I'm currently looking for a way to stop using the CLI tool and run our development and production build steps manually.

[FabianLars]

Note (1): You can't use TOML files in CI as the Github action is written using the Javascript flavor CLI instead of the Rust one, and it doesn't understand TOML.

This is not true or at least isn't supposed to be true. Both the js and rust clis are literally the same and should both support the same stuff (assuming they're on the same version). The action itself also tries to interpret the config arg as toml, json5, and json.

I hope the team adds a nice way to configure and maintain multiple sets of build configurations.

Can you be more specific? I'm not a nx user nor did i work on really large repos containing multiple apps whatever so i'm not sure what exactly would help you.