Compatibility with WSL(2)?

[jpfeuffer]

Hi,

I have seen a lot of issues that were closed and people were referred to the "Remote: WSL" extension.
I tried that extension but I think the cmake-tools plugin is just not compatible at all.
Here are my problems:

1. It won't even install on the remote instance that spawns with code . unless you declare it as a UI plugin in your settings.
2. It does not find the compilers/kits on the WSL instance (I installed gcc/++ with apt), no matter what I do. Neither in the Windows instance nor on the Remote WSL instance.
3. Extended configuration is almost impossible, since Workspace configurations overwrite the Remote WSL configurations
4. Even if I move everything to User configuration and overwrite with the Remote WSL configuration, everything is full of [proc] The command: /usr/bin/cmake --version failed with error: Error: spawn /usr/bin/cmake ENOENT errors, while of course running /usr/bin/cmake --version from the terminal of the same Remote WSL instance works flawlessly.

TLDR: How to use this extension with WSL? All I want to do is to build the same project in the same folder once with MSVC and once with GCC WSL, preferably even without having two VS Code windows open. Is there any tutorial or documentation?

[elahehrashedi]

Question 1: There shouldn't be an issue installing the extension on WSL, regardless of how you open a WSL window:

Would you explain more about what kind of error you encounter when trying to install the extension?

Question 2: Can you run "gcc -v" and share the results with us?
I am not sure why the extension can not pick up the kit. Can you try and add the kit manually to the .vscode/cmake-kits.json file and see if you can get that to work, here is an example:

  {
    "name": "GCC 7.5.0 x86_64-linux-gnu",
    "compilers": {
      "C": "/usr/bin/gcc-7",
      "CXX": "/usr/bin/g++-7"
    }

[jpfeuffer]

[jpfeuffer]

And my Windows instance of the same workspace:

[jpfeuffer]

I don't even know, why it tries to use the Windows cmake.exe under WSL and everything. It just feels like this extension was not really designed with WSL2 in mind. Are there people actively working with a project where they are using cmake-tools to compile the same project under Windows and WSL2 parallelly?

[bobbrow]

Extensions don't generally need to be designed for WSL/WSL2 because the underlying system should be reporting to the extension that it is operating in a linux environment. It sounds like something is not configured correctly. I am running the extension in WSL2 and it picks /usr/bin/cmake for me. I tried both a workspace in the linux filesystem and something on /mnt/d.

Can you share what the value of Cmake: CMake Path is? I'm wondering if you overrode the setting at some point.