Skip to content

fix: don't pull tauri default features (wry) unconditionally#7

Merged
eleboucher merged 1 commit into
mainfrom
fix/gate-tauri-wry
Jul 20, 2026
Merged

fix: don't pull tauri default features (wry) unconditionally#7
eleboucher merged 1 commit into
mainfrom
fix/gate-tauri-wry

Conversation

@eleboucher

@eleboucher eleboucher commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

tauri = "2" pulls tauri's default features, including wry, which forces tauri-runtime-wrywebkit2gtk into downstream CEF builds.

Switch to tauri = { version = "2", default-features = false }. The plugin is generic over R: Runtime and doesn't need wry to compile. iOS keeps wry via its existing target-cfg features = ["wry"].

The plugin is generic over R: Runtime and doesn't need tauri/wry to
compile. Enabling tauri defaults forced tauri/wry -> tauri-runtime-wry
-> webkit2gtk into downstream CEF builds that should only use the CEF
runtime.

The iOS target-cfg already adds features = ["wry"] explicitly, so iOS
keeps wry. Sable's own tauri dep sets dynamic-acl/compression, so no
shared features are lost.
@eleboucher eleboucher reopened this Jul 20, 2026
@eleboucher
eleboucher merged commit 4e1bcdc into main Jul 20, 2026
35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant