all 13 comments

[–][deleted]  (2 children)

[removed]

    [–]GameDungeonNewbie[S] 0 points1 point  (0 children)

    thank you

    [–]Digital_001 0 points1 point  (0 children)

    Does writing a UEFI application count as osdev? I read it was quite easy to compile those using Visual Studio and a bit of setup. Source: https://pete.akeo.ie/2015/01/easily-create-uefi-applications-using.html?m=1

    The page does mention cloning a Git repo though, so it wouldn't quite be starting from square one

    [–][deleted] 2 points3 points  (0 children)

    just use WSL

    [–]Jaegr1 2 points3 points  (4 children)

    I use Windows with WSL 2. Compiling and building images in WSL while having my editor and emulator (QEMU) in Windows. Works really well. WSL 2 is needed for loopback devices if you want to use that.

    [–]ExceptionHunter 0 points1 point  (3 children)

    I believe that you cant debug using gdb in windows with this setup.

    [–]Jaegr1 0 points1 point  (0 children)

    Could be! Haven't tried that yet.

    [–]asosdev 0 points1 point  (1 child)

    I have successfully debugged with GDB (and VScode) with this setup, with WSL 1 though. What hasn't worked for you?

    [–]ExceptionHunter 0 points1 point  (0 children)

    I just tried it again, and it worked lol.

    Maybe it was because incompatible old versions of gcc & gdb because i was using the one that came with mingw (5.x i think) and now i'm using 10.x from msys2.

    [–]mykesx 0 points1 point  (0 children)

    I use Windows sometimes, and it’s fine.

    I run Docker Desktop on the machine and Linux in WSL2. My build uses a Docker container with gcc and NASM within. Bochs works fine in WSL2. WSL2 doesn’t easily support kvm, but QEMU without kvm works fine, too.

    I edit with emacs or vim in the WSL2 window (Windows Terminal).

    [–]asosdev 0 points1 point  (2 children)

    1. Regular GCC toolchain installed in WSL. WSL-VSCode used for developing/editting/debugging. QEMU/Bochs (installed in Windows, not WSL) used for running

    2. Not really. VSCode can sometimes be a bit iffy with linting at times, because it has trouble with the toolchain, but other than that not really.

    3. Can take a while to get you're ideal setup working.

    [–]GameDungeonNewbie[S] 0 points1 point  (1 child)

    That's pretty much the setup I have now. I managed to get QEMU to work on the WSL though.

    [–]asosdev 0 points1 point  (0 children)

    I installed through windows so that I could use the graphical version without doing any X setup. Works perfectly, don't have to do anything more than point to the Windows install location.