Garrett Campbell

@Maddimax This is a good call-out, and thanks for the reproduction steps! Marking this as a bug and we will assess it when we can. Thanks!

@chrish42 Is it possible that `CMakePresets.json` would allow you to do what you're searching for?

@khteh In the terminal screenshot you included, the build time is there. In the original screenshot in the original creation of the issue, the screenshot is showing the `configure` process...

 Or are you looking for a more explicit kind of output?

@khteh Both, this is what I was referring to in this comment: https://github.com/microsoft/vscode-cmake-tools/issues/4461#issuecomment-2886768583 @AnsonSoh Had the setting disabled so that the output went to the "Output" pane

@khteh Could you walk me through how you're building? If it's showing up in the terminal view then somehow you must be using the task or some other build method.

@AnsonSoh @khteh Okay, I see the repro here: https://github.com/microsoft/vscode-cmake-tools/issues/4461#issuecomment-2900037748, so that may be a bug that we need to investigate. For this comment, thanks for the specific repro steps, we...

@malsyned I think that this is a useful PR and is an interesting additive feature. There is also minimal risk for regression, as by default this will not perform any...

@malsyned Unfortunately these are known flaky issues with our tests. The Mac has a flakiness in one test and the Windows occasionally hits a timeout. I requeued the tests.

@malsyned What about an option where we simply sort the configurations we provide, and essentially de-prioritize the Utility targets? It makes me nervous to fully remove a target from intellisense...