microsoft / microsoft/vscode-cmake-tools
Feature request: Allow running a custom target after configuring
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### Brief Issue Summary
I use vscode for some QT Projekts, there require to run some tools to generate header / source files.
The problem is, that code indexers and other tools would ideally require those generated files. Also features like recompiling a source-file wont work because of missing generated files.
What needs to be done in my case:
``` bash
# configure
cmake -DCMAKE_GLOBAL_AUTOGEN_TARGET=ON
# post-configure
cmake --build . --target autogen
# only now many features will work correctly
```
I would like if I could configure a set of "post-configure" targets, like
``` json
"cmake.configurePostTarget": [
"autogen"
]
```
vscode should configure, then potentially check if the targets exists and start them or just try running them (failure is not fatal).
### CMake Tools Diagnostics
_No response_
### Debug Log
_No response_
### Additional Information
_No response_
Contributor guide
Research direction
Start by tracing the configure workflow and the handling of the proposed cmake.configurePostTarget setting. Check how CMake build targets are invoked, using autogen as the example, and determine where a missing target or failed post-configure command should be tolerated. Done means configured targets are attempted after configuration without making configuration failure fatal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100