Juan Carlos Arevalo Baeza

I didn't find an issue for this, but after sending a PR, I noticed by chance that there's a closed (not used) PR that attempted to solve this. #1 I...

Progress report: no dice. What I said doesn't work at all, because the compiler flags (CMAKE_CXX_FLAGS) are not copied to _any_ target properties. They are pre-pended in the generator when...

Ooohhh... I spotted an issue in CMake's own DB: https://gitlab.kitware.com/cmake/cmake/-/issues/19084 It describes almost exactly what I'm seeing. I'll put my thoughts there, see what happens.

I'm currently seeing this on a loaded VSCode workspace file with multiple folders in it, each with its own CMake project, and one of which currently uses CMakePresets.json. Each folder...

I'd like to pile up on this request. It should be possible to open a single folder with multiple sub-folders holding CMake projects, without requiring a VSCode workspace listing each...

As evidenced by other linked issues, this is a general problem with using presets. CMake allows command-line options to override things specified in presets, but this extension silently ignores most...

One loosely-related frustrating thing about this is that it's tempting to use CMakeUserPresets.json in order to provide overrides, however there doesn't seem to be a way to use this "user"...

@gcampbell-msft Yes, thanx! That sounds like a similar issue, and I agree that improving/generalizing tool acquisition (as mentioned here before) would provide good benefits. The extension generally doesn't rely on...

@qarni I'll need to set up a new machine/VM for this. In the meantime, your .zip says 1.13 but the extension is up to 1.18 now. Why the discrepancy? I'd...

@qarni I couldn't reproduce the issue with the 1.13 test build. But I was also unable to reproduce the issue with the current 1.18 either. I didn't set up a...