microsoft / microsoft/vscode-cmake-tools
No cache object found when manually configuring build folder before cmake-tools
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### Brief Issue Summary
Only way to get rid of the error
[rollbar] Unhandled exception: Unhandled Promise rejection: Post-folder-open Error: No cache object found [object Object]
Is to remove build folder and then ask cmake-tools to configure without configuring with terminal.
What I tried:
- Reset Cmake Tool Extension
- rm -rf build &&
cmake -C CMakeConfig/linux_gcc7.cmake --preset=gcc7_linux_x86_64 -DAMSR_BUILD_TESTING=ON -DAMSR_BUILD_TEST2020=ON -DAMSR_BUILD_DOC=ON -DAMSR_BUILD_EXAMPLE=ON \
-DBULLSEYE_ENABLE=ON -DAMSR_BUILD_BENCHMARK=ON -DCMAKE_CXX_FLAGS=(string join ' ' (cmake -LA -N . | grep CMAKE_CXX_FLAGS_INIT | \
cut -d= -f2) -- "-Wfatal-errors") -DAMSR_BUILD_TEST2020=ON -DAMSR_BUILD_TESTING=ON -DCMAKE_CXX_FLAGS_DEBUG="-g -O0"
We have a LOT of presets and targets. A gazillion .jsons are created, might be related
### CMake Tools Diagnostics
_No response_
### Debug Log
_No response_
### Additional Information
_No response_
Contributor guide
Research direction
Start by reproducing the post-folder-open error in CMake Tools using the reported manual CMake command and the project's many presets and targets. Inspect the extension's handling of the generated cache objects and compare behavior with configuring the build folder through CMake Tools; done means the existing folder opens without the “No cache object found” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100