Conflict extension of CMake Tool in nRF Connect SDK v2.0.2

RE: Conflict extension of CMake Tool in nRF Connect SDK v2.0.2

ErikLundh — Thu, 08 Sep 2022 19:52:18 GMT

I am happy if merely disabling CMake is good enough solution for you.

However disabling the CMake tool only works - as long as you are a 'one-trick pony', only using Visual Code on that one computer with Nrf Connect and nothing else.

If you need to use Visual Code on the same machine for any other purpose that involves CMake - a very popular tool in both "regular software" and several other embedded environments, you need to disable nrf Connect and enable Cmake - every time you switch.

By using settings profiles in Visual Code 1.71 you can have several set-ups of different toolchains with Visual Code on the same computer.

I myself work on some different Cmake based projects that are not for embedded targets, and use different CMake based embedded dev toool chain environments for development with e g Raspberry Pico and ESP32.

/Erik

RE: Conflict extension of CMake Tool in nRF Connect SDK v2.0.2

dejans — Thu, 08 Sep 2022 09:09:06 GMT

Hi,

I am glad that your issue has been resolved.

Best regards,
Dejan

RE: Conflict extension of CMake Tool in nRF Connect SDK v2.0.2

Jack Phan — Wed, 07 Sep 2022 15:47:51 GMT

Hi Erik & Dejan,

I disable CMake Tool (disable, not disable-workspace) and the warning doesn't show up any more.

Thanks a lot for your time,

Jack

RE: Conflict extension of CMake Tool in nRF Connect SDK v2.0.2

dejans — Mon, 05 Sep 2022 12:25:48 GMT

Hi,

This issue can be resolved with workaround which disables CMake extension for a specific workspace using extension sidebar menu.

Best regards,
Dejan

RE: Conflict extension of CMake Tool in nRF Connect SDK v2.0.2

ErikLundh — Sun, 04 Sep 2022 06:32:01 GMT

Hi Jack,
I have the same problem with conflicting extensions in VS Code
My hope is that the latest VS Code (ver 1.71) has "settings profiles"
My understanding is that this will support different sets of extension - and other settings. I read that you can have two instances of VS Code running at the same tinme - with different settings profiles. Great if you are working with both CMake-based projects and nrfConnect-based ones
The settings profiles feature has been in development for some time - and available to those to try "-Insiders" versions of VS Code.
However the last piece of the puzzle was missing. You could only switch settings profiles through menu choices in VS Code, after starting it up.
But now with VS Code 1.71 it seems like there is a way to specify which settings profile from the command line.
Chip vendor support packages usually invoke VS Code through some sort of script - making it easy to invoke different settings profiles for different tool chains and extension sets.

Erik