Yes, I have also seen forum posts regarding recompaction errors, but mainly some old related to logging, which should be fixed.
I’m developing on Windows 11, with MSYS/MINGW64 environment and I’m using VSCode. CMake version is 3.29.2
Besides this problem with the recompaction error, actually my goal is to create dependency graph during configuration. I have not found a possibility to enable graphviz when using profiles. So this is a workaround to call cmake recursively just for the purpose of the graph.
It seems like there’s something that is preventing ninja from performing recompaction. Has the build been interacted with as a different user at any point? Could something else be poking the tree somehow?
You’re trying to re-run CMake during the build in a recursive way. I would recommend you don’t do that. In some build systems, that fails (I think Xcode rejects it now, it didn’t in the past).
In the next CMake feature release (3.31), CMake presets will gain support for a graphviz field in the configure presets. That’s a better way to incorporate running graphviz with your configuration step by default.
In the next CMake feature release (3.31), CMake presets will gain support for a graphviz field in the configure presets. That’s a better way to incorporate running graphviz with your configuration step by default.
Gotcha; that sounds much needed!
You’re trying to re-run CMake during the build in a recursive way. I would recommend you don’t do that. In some build systems, that fails (I think Xcode rejects it now, it didn’t in the past).
Isn’t the PID different? Why would that cause a recursive-like execution?
In the Xcode case, I think it detects a recursive call (yes, including separate processes) and it fails with some kind of locking-related failure. I don’t recall the details, sorry.