'Failing to use VSCode and WSL to compile windows programs with mingw-w64 (WSL)
I, per a friend's recommendation, installed WSL Debian. With Msys2 it was mostly plug and play. Yes I have the WSL Remote extension and started "code ." from WSL. The VSCode C++ plugin can't identify the header files in \\wsl$\Debian\usr\x86_64-w64-mingw32\include even when I set the include path in settings. Should I use \\wsl$\Debian\usr\share\mingw-w64\include instead?
How would VSCode know to use the WSL terminal when I press f5? Should I have the sources files on Windows or Debian? I should be able to have them in either place cause I have \mnt\c as well as \\wsl$. Also if I make a program and want to debug it with gdb, wouldn't I need gdb running on the same system (Windows)? So I'll still need something like Msys2. Does this just not work? I thought this is the point, or is it just to be able to make Linux software on Windows not the other way around?
I also gave up on using CMake since I don't know it well enough to use it with anything it can't automatically identify.
All I see are lines and lines of messages I don't know how to interpret and I can't find any answers. I'm afraid of stackoverflow though.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|