Cross-platform WebView rendering library in Rust that supports all major desktop platforms like Windows, macOS, and Linux.
Overview
WRY connects the web engine on each platform and provides easy to use and unified interface to render WebView. It also re-exports TAO as a module for event loop and window creation.
Usage
The minimum example to create a Window and browse a website looks like following:
There are also more samples under examples
, you can enter commands like the following to try them:
cargo run --example multi_window
For more information, please read the documentation below.
Documentation
Platform-specific notes
All platforms use TAO to build the window, and wry re-exports it as an application module. Here is the underlying web engine each platform uses, and some dependencies you might need to install.
Linux
Tao uses gtk-rs and its related libraries for window creation and wry also needs WebKitGTK for WebView. So please make sure the following packages are installed:
Arch Linux / Manjaro:
The libayatana-indicator
package can be installed from the Arch User Repository (AUR).
Debian / Ubuntu:
# For tray feature, choose one of following package
Fedora
# For tray feature
Fedora does not have the Ayatana package yet, so you need to use the GTK one, see the feature flags documentation.
macOS
WebKit is native on macOS so everything should be fine.
If you are cross-compiling for macOS using osxcross and encounter a runtime panic like Class with name WKWebViewConfiguration could not be found
it's possible that WebKit.framework
has not been linked correctly, to fix this set the RUSTFLAGS
environment variable:
RUSTFLAGS="-l framework=WebKit" cargo build --target=x86_64-apple-darwin --release
Windows
WebView2 provided by Microsoft Edge Chromium is used. So wry supports Windows 7, 8, and 10.
Android / iOS
We have experimental support of mobile ends. If you are interested in playing or hacking it, please follow this note.
When building for Android, WRY generates kotlin files that are needed to run WRY on Android and you have to set the following environment variables:
WRY_ANDROID_REVERSED_DOMAIN
WRY_ANDROID_APP_NAME_SNAKE_CASE
WRY_ANDROID_KOTLIN_FILES_OUT_DIR
You can skip setting these environment variables if you are using the WRY template from our cargo-mobile
fork.
License
Apache-2.0/MIT