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

Windows debugging WSL #6

Open
sivanmu opened this issue Mar 10, 2022 · 3 comments
Open

Windows debugging WSL #6

sivanmu opened this issue Mar 10, 2022 · 3 comments

Comments

@sivanmu
Copy link

sivanmu commented Mar 10, 2022

Hey James,

I was testing it out on Windows and I cannot make it work. Tried with 1.2.0 so far but this issue might be version independent:

image

It looks as if WSL cannot interact with Chrome running outside of WSL, which sort of makes sense, for a subsystem that is but a command line.

I documented the steps that got me here, just so we can add them to the Readme once we get it running (should we, using this approach):

  • install Windows Subsystem for Linux (WSL)
    • open a command prompt with administrator rights and type "wsl --install"
    • after it completes the download and install automatically in a few minutes, restart your machine
    • After the restart it will automatically launch WSL for the first time, taking a few minutes to complete the installation.
    • When it is done installing, it will ask you for a username and password. Remember those
    • (To launch into WSL in the future when this existing terminal gets lost, either type WSL into the windows search or type WSL into a command prompt and hit enter)
  • Into this WSL prompt enter "sudo apt update" followed by "sudo apt install openjdk-17-jre" which installs the java runtime environment (when asked for elevation/permissions, enter username and password from earlier)

Thanks for your help,
sivanmu

@sivanmu sivanmu changed the title Windows: "Input line is too long" Windows debugging WSL Mar 10, 2022
@megger-cgfx
Copy link
Contributor

Just did some reading on this. This might be a solution, have to try it first though after my local WSL install gets un-stuck on mysterious errors.
https://github.com/microsoft/wslg
(https://www.youtube.com/watch?v=KcIdAunRSSc)

@megger-cgfx
Copy link
Contributor

megger-cgfx commented Mar 11, 2022

Alright, spent quite some time on this yesterday/today on three different devices, ran into different errors left and right, but at least managed to get wsl to run on two, one just refused. Still, the WSLg variant (with graphical processing, able to launch GUI apps like chrome for us) doesn't work on any. I have a feeling it works semi-natively on Windows 11 though, at least they say so, that it's easier to access, but I really don't want to upgrade.

Also, it really blows up the instruction scope and exception handling list, and I fear this would make it flat out inaccessible to your average joe with Windows. Do you think there's any way to make it run on Windows natively?

@megger-cgfx
Copy link
Contributor

megger-cgfx commented Mar 12, 2022

With the weekend here, I've decided to bite the bullet and upgrade to Windows 11 in hopes of getting this to run on the new WSLg (which should have run on Win10 in some capacity already but refused in more ways than one.)

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

No branches or pull requests

2 participants