microsoft / vscode-cmake-tools

CMake integration in Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=vector-of-bool.cmake-tools
MIT License
1.48k stars 456 forks source link

cmake: cache edit cache not found #3934

Closed frankieD3 closed 4 months ago

frankieD3 commented 4 months ago

Brief Issue Summary

I have been following a tutorial online and have an interesting tool in cmake-tools , cmake: edit: cmake cache. The problem is with Ctrl-Shift-P I am not finding it. Some of cmake-tools seems to be available. Here is the environment

1) wsl and UBuntu-24.04 2) Visual Studio Code 1.9.1 3) Cmake tools Extension 1.18.43

Additional observations

I'm sure that it is likely something in my environment. The problem is that I'm not sure how to debug this problem. From installng Jupyter notebook extensions I had to activate a Python extension that I perhaps had deactivated. Not entirely sure as I was shooting a bit in the dark.

I have toggled Developer Tools which pops up a window with interesting information that I'm not ready to parse.

Are there extensions that Cmake Tools depends on?

Thanks, Frank

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

No response

frankieD3 commented 4 months ago

Additional note In the Running Extensions tab I see under CMake 0.0.17 Cannot register 'cmake.cmakePath'. This property is already registered. well it was set to just cmake. When I set that variable to /usr/bin/cmake the extension loaded but I still do not see the edit cache selection.

frankieD3 commented 4 months ago

I found an old extension, just plain Cmake, and got rid of it. I select cmake: edit cmake cache (UI) and nothing pops up

v-frankwang commented 4 months ago

@frankieD3 When I use the wsl extension in vscode to connect to an Ubuntu machine, if I don't open a cmake project I can't find it by searching for CMake:Edit cmake cache in the command palette, when I open a cmake project I search for it in the command palette. CMake:Edit cmake cache is searchable, is this a reproduction of your problem?

ENV: CMake Tools :v1.18.43 Ubuntu: 18.04 C/C++:v1.21.2 vscode: v1.91.1

Don't open a cmake project: image Open a cmake project: image

frankieD3 commented 4 months ago

I got what was expected after removing the extension VsCode NeoVim and the old CMake(I didn't know it was old) in the WSL Ubuntu environment.

So the problem is solved.

However

From the point of view of a relative noob to the modern environment( I had serious build experience in the Unix environment of 25 years ago):

I had 2 extensions interfere with a good tutorial I have been take from up in Udemy. Granted I have taken advice from various web pages over the last year of what extensions to use. This is the 2nd time I have been bitten in the ... running tutorials and conflicting extensions.

I think I will post some questions elsewhere some questions about how extensions are managed with VS Code with the chief problem :

Why are some extensions not deprecated. CMake, last update 2017, is a good example. If not deprecated why is a warning not given?

Thanks for listening!! Frank