Respect required-features field from Cargo.toml #14379
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cargo.tomlallows binary target definition to containrequired-featuresfield (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.tomlregardless of the presence of therequired-featuresfield 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:Example build with
cargo-tauri:The above will exclude
defguard-servicefrom the final package, while this:will include all binaries.