Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Desired Rust & Cargo Upstream Features #7420

Open
ogoffart opened this issue Jan 21, 2025 · 0 comments
Open

Tracking Desired Rust & Cargo Upstream Features #7420

ogoffart opened this issue Jan 21, 2025 · 0 comments
Labels
upstream Needs a fix upstream

Comments

@ogoffart
Copy link
Member

This issue serves as a tracker for features and improvements we would like to see in Rust, Cargo, and related tools that would benefit Slint. It is meant to be updated and edited over time.

Features We Wish to See in Rust:

Features We Wish to See in Cargo:

  • Improved communication between runtime and code generation crates:

    • We'd like better mechanisms to communicate features from the "runtime" crate to code generation crates (e.g., slint-macro or slint-build).
    • This would allow us to surface relevant errors when required features are not enabled (e.g., detecting if Qt is available for backend-qt).
    • Currently, we rely on hacks like the SLINT_DEFAULT_STYLE.txt, which is unreliable.
  • Feature flags based on system dependencies:

    • build.rs currently cannot influence features. It would be useful to enable or disable features based on detected system dependencies (e.g., disabling the backend-winit crate if Qt is found on the system).
    • A configure.rs-like system would address this need.
  • Simpler disabling of individual default features Ability to disable individual default features rust-lang/cargo#3126:
    An easier mechanism to selectively disable default features would help as we have many default features and they need to be repeated in each depending crates.

In cargo-semver-check:

@ogoffart ogoffart added the upstream Needs a fix upstream label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Needs a fix upstream
Projects
None yet
Development

No branches or pull requests

1 participant