-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
[Build] WSL2 #109
Comments
|
Makes sense. I think shutting down WSLg made it more complicated than I had thought. Works properly now. Alas, a bit slow and flickery. But so does the native Wayland compositor on my machine, too. EDIT: NVM. EDIT2: Was apparently an XAUTH issue. After manually setting |
Using these steps #108 (comment) I can run xterm & xeyes |
Thanks again. I got it working with those steps on my WSL2 Ubuntu 20.04 system, too. Namely, the XAuthority parts helped a lot. |
I've done some digging on how to run this smoothly on WSLg, and it seems WSLg uses a system distro image to run Weston with a custom build of MESA to get hardware acceleration. I expect Greenfield to run faster/smooth if a similar image is used. |
Wsl2 now supports gpu video encoding https://devblogs.microsoft.com/commandline/d3d12-gpu-video-acceleration-in-the-windows-subsystem-for-linux-now-available/ |
I'd like to use this issue to track my process in getting Greenfield to work under Windows 11/WSL2.
According to microsoft/WSL#938 (comment), this apparently worked before.
RN, after disabling WSLg with the following command (to be updated with a snippet that will automatically pull the Windows username. As soon as I've figured out how to properly get the Windows username from Powershell or cmd without additional characters), Greenfield proxy reports that no
dev/dri
interface can be found.The text was updated successfully, but these errors were encountered: