VSCODE记得已删除文件夹的选定CMAKE套件
因此，如果我制作了一个全新的文件夹，请在Vscode中打开它，然后首次运行“ Cmake Configure” - CMake Extension要求我选择一个套件。请注意，仅在第一次运行“ CMake Configure”时才发生这种情况。
这是奇怪的： 如果我关闭VSCODE，请删除该文件夹（以及所有内容），重新创建此文件夹，用VSCODE重新打开它，然后再次运行“ Cmake Configure” - 这次我不要求为CMAKE选择一个套件。
我希望与该新目录的工作区相关的任何内容都将存储在该目录中，因此当我删除文件夹时 - Vscode使用的任何隐藏文件都应删除诸如所选套件之类的内容。 显然不是这样...那么Vscode如何记住某些工作空间所选的CMake套件之类的内容？
So if I make a completely new folder, open it in vscode, and run 'cmake configure' for the first time - the cmake extension asks me to select a kit. Note how this happens only on the first time 'cmake configure' is run.
Here is what's weird:
If I close vscode, delete the folder (and all of it's content), re-create this folder, re-open it with vscode and run 'cmake configure' again - this time I am not asked to select a kit for cmake.
I would expect that anything related to the workspace of this new directory will be stored within that directory, so when I delete the folder - any hidden files used by vscode to remember things like selected kits should be deleted.
This is obviously not the case... So how does vscode remember things like selected cmake kits for certain workspaces?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我也有类似的问题。 VSCODE存储全局设置和信息：
在此“代码”目录中，我为目录名称做了一个递归的GREP，我对EG有问题：
对我来说，此GREP返回了几个 .json 文件和几个 state.vscdb 二进制文件。我检查了JSON文件，并纠正了其中的一些路径问题。但是，这并没有解决我的问题。 GREP返回的二进制文件似乎是一些VSCODE数据库文件。关闭VSCODE后，我删除了（更改临时名称）state.vscdb and state.vscdb.backup文件，在GREP返回的所有目录中，然后重新启动了VSCODE。
VSCODE促使我进行了干净的CMAKE配置，该配置确实有效，并为我的陷入困境目录提供了干净的构建。诚然，这是非常野蛮的力量，但对我有用。我只有几个我必须重建的项目。重建后，我确实注意到了一些状态。VSCDB文件已重新创建，但不是全部。
如果在Vscode本身中可以使用这种“深清洁”构建，那将是很好的，但是我在任何地方都找不到任何信息。
I had a similar issue. Vscode stores global settings and information in:
From this 'code' directory, I did a recursive grep for the directory name that I was having issues with e.g.:
For me, this grep returned a couple of .json files and several state.vscdb binary files. I inspected the json files and corrected some pathing issues within them. This did not fix my issue however. The binary files returned by grep appear to be some vscode database files. With vscode closed, I removed (temp name changed) the state.vscdb and state.vscdb.backup files in all directories that were returned by the grep, then relaunched vscode.
Vscode prompted me to do a clean cmake configure, which did work and gave me a clean build of my troubled directory. This admittedly is very brute-force, but worked for me. I only had a couple of projects that I had to rebuild. After rebuilding I did notice that some of the state.vscdb files had been re-created, but not all.
It would be nice if this type of "deep clean" build were possible within vscode itself, but I couldn't find any info on this anywhere.