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

Hello Group,

I’m using nRF Connect SDK v2.0.2 with Visual Studio Code (up-to-date). When I open “Open VS Code” from Toolchain Manager v1.1.3, it shows a warning of conflict extension of CMake Tool.

Do you have any idea to fix this?

Thanks a lot for your time,

Jack

ConflictingExtension

Click on Show Conflicting Extension, it shows

ConflictExtension_CMakeTool

Parents
  • 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

Reply
  • 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

Children
No Data
Related