-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[feat] Tauri on Embedded Linux + WPE WebKit? #4784
Comments
Unfortunately this is not something we plan on implementing, it would require a massive overhaul for a feature that most of the community won't use. You could try implementing it directly in the wry repo or if you want to use Tauri, you'd need to implement a custom tauri Runtime. |
If Tauri can incorporate Servo in the future, you may be able to target embedded Linux. |
Unfortunately Servo still requires X11 so I don't think it'd work just yet. |
Indeed, I think WPE may be a good option. But then in that case there's probably no much benefit to port a Tauri runtime on WPE because there's no window/system tray/clipboard. I'd rather just run my frontend app on WPE and connect a local backend server for low-level stuff. |
Describe the problem
I'm trying to build a full-screen display app for a kiosk machine in our factory for internal production testing. I'm thinking is it possible to get Tauri working with WPE WebKit and render stuff to Linux DRM directly? This is quite useful as I can re-use some native Rust bindings I've implemented earlier, while I also don't need to rely on GTK and window managers so that the overhead on RAM and storage.
Describe the solution you'd like
Not sure... Maybe I need to implement the IPC stuff specifically for WPE: https://github.com/tauri-apps/tao/tree/dev/src/platform_impl/linux
Also, I would like to know is there any alternative way to modify the current code and get it working without GTK and X11/Wayland?
Alternatives considered
Another similar thing is MiniGBM for Chromium, but I'd prefer not to use Chromium for low-RAM platforms.
Additional context
No response
The text was updated successfully, but these errors were encountered: