ruki

> 是的，要手动设置link 那就比较蛋疼了，这样，即使走 cmake 能找到，也没法自动 links 上，还得手动配各种 link

> add_rules("plugin.compile_commands.autoupdate", {outputdir = "$(buildir)", lsp = "clangd"}) > xmake project -k compile_commands later, the compile_commands are put into the cwd. These two are completely independent and unrelated, don't mix...

The template configuration interface is not yet stable, so it is currently only an internal private interface. You cannot customize the template configuration. duplicate, https://github.com/xmake-io/xmake/issues/3539

这种自己搞个 task 插件生成下就行了。

This is very difficult to maintain and affects the configuration of all actions such as build, run, clean, and install. And it is only used for vsxmake. We should write...

In addition, this still cannot avoid starting multiple xmake processes. It might be better if we have a way to start only one xmake to build. Maybe we can then...

> A script like that would be a good way to handle it, I don't think it's only relevant for vsxmake but it would be my main usage of it....

> The real issue with vsxmake project is that currently "build solution" (or "clean solution") are badly handled as they run for every target (so they're doing a xmake config...

code 和 logs 就能不能加个 code block 么，乱成这样怎么看。 ```console xmake g -c ``` 先清下全局缓存重新检测下 ```console xmake f -c ``` 还是不行，就自己调下 https://github.com/xmake-io/xmake/blob/dev/xmake/modules/detect/sdks/find_vstudio.lua ```console xmake g -c xmake l detect.sdks.find_vstudio ```

> { "2022" = { vcvarsall_bat = "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvarsall.bat", vcvarsall = { }, version = "17.0" } } 没，你安装不完整，重装下。