#Clion wsl movie
#Clion wsl serial
#Clion wsl drivers

I really like most of its key shortcuts, like Ctrl+D to duplicate a line (vs other IDEs which DELETE the line), Ctrl+Shift+в†‘/в†“ to move a line upwards/downwards, etc. Unfortunately, WSL2 does not have support for lsusb (or USB pass-thru in general), so I can't test my USB code very well, and occasionally have to go back to booting a Linux VM.ДЇor my 'IDE', I usually just use Notepad++ (another benefit of using WSL2).

#Clion wsl movie

It is nice to not have to reboot every time I want to play Windows-only Steam games though, or use Windows Movie Maker (still), or run Unity (because the Linux version is pretty glitchy). Also, it fails to change the mouse cursor or switch to free-look mode. For instance, it used to work without having to tick the 'Disable access control' box every time. I also run XLaunch (VcXsrv) so I can run graphical QEMU/Bochs, but it is a bit glitchy. I had to update to WSL2 because I needed to be able to mount loopback devices. It worked pretty well, so I use it as my main Linux for now. I used to use an Ubuntu dual-booted with Windows 7, but recently I got a laptop with Windows 10, so I decided to try out WSL (Ubuntu 20.04). Thou hast outraged, not insulted me, sir but for that I ask thee not to beware of Starbuck thou wouldst but laugh but let Ahab beware of Ahab beware of thyself, old man.

#Clion wsl drivers

So in the end, I would have to poach the drivers from elsewhere (like Linux), and then there's that legal stuff again.

#Clion wsl serial

So USB serial adapters usually use one of a handful of chips to do the translation, and each works completely differently, and in both cases, I have not seen data sheets detailing the use. The problem with USB serial adapters is that, ironically, USB has no standard for serial adapters, despite being called the Universal Serial Bus. But it does mean I can only debug it if the computer I use has a serial line (and it has to be an ISA COM port, none of that USB rubbish ), and I have a terminal handy.

Partially because I put all my debug messages on serial line instead of the main screen, so the screen is free for userspace to use (and so I don't need a font renderer in kernel space). I typically run my OS against bochs, but I periodically try QEMU as well. That's the nice thing about this setup: I haven't sunk so much time into a Makefile that switching to ninja is utterly unthinkable. I might improve the script to create a ninja file instead in future. With GCC, spitting out the dependencies can be done on the fly, but at work I have a compiler where generating dependencies requires a second pass over the file, and it takes about as long as actually compiling it. This (like everything else) has drawbacks and advantages. dependencies are not automatically updated). That stuff should be portable to anything POSIX, and even to Windows with nmake, but I don't want to make assumptions.Dependency tracking is done by the shell script (i.e. So why not just use sh? So I have a POSIX sh script that creates a POSIX make file. I eventually happened to land on that when I read someone describe that GNU Make essentially just tries to marry POSIX Make with POSIX sh. My build system: Shell script that creates a makefile.

I use it at work, and at home, I have used it for C, C++, C# (on Windows, with the csc command line compiler), shell scripting, config files, Java (when I was younger), everything.