Respect required-features field from Cargo.toml

[moubctez]

Cargo.toml allows binary target definition to contain required-features field (see The Cargo Book). If defined, the binary is built only when a certain feature is activated.

Tauri pulls the list of binaries from Cargo.toml regardless of the presence of the required-features field and tries to add them to the final package. But the binaries may not be there.

This pull request addresses this problem.

Example excerpt from Cargo.toml:

[[bin]]
name = "defguard-client"

[[bin]]
name = "defguard-service"
required-features = ["service"]

Example build with cargo-tauri:

cargo tauri build

The above will exclude defguard-service from the final package, while this:

cargo tauri build --features service

will include all binaries.

[github-actions]

Package Changes Through 095d43d

There are 3 changes which include tauri-bundler with patch, tauri-cli with patch, @tauri-apps/cli with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
tauri-bundler	2.7.2	2.7.3
@tauri-apps/cli	2.9.2	2.9.3
tauri-cli	2.9.2	2.9.3

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[FabianLars]

thanks for the pr! would you mind adding a small changefile as well please?

[moubctez]

thanks for the pr! would you mind adding a small changefile as well please?

Done

[sftse]

Shouldn't this have the same code path if options.features == None vs options.features == Some(["a", "b"]) when req_features == Some(["c"])? The continue will be hit in the latter case, but not in the former.

Looking into this due to #14607