CMake as a language makes PHP look good. Whenever I have to use it, there's a whole lot of warnings and often errors, too. Problem is, the line CMake says had an error may not be the line that caused it. And when everything finally works, in comes a new version that breaks other builds again.
So why does a make need a debugger in the first place? Your build script shouldn't be such a complex program that warrants its own development project.
Great that you used AI to build something useful, but it’s still weird to me when someone says “I built this”. Maybe the more correct way to say this is “I spec’d this”
CMake as a language makes PHP look good. Whenever I have to use it, there's a whole lot of warnings and often errors, too. Problem is, the line CMake says had an error may not be the line that caused it. And when everything finally works, in comes a new version that breaks other builds again.
So why does a make need a debugger in the first place? Your build script shouldn't be such a complex program that warrants its own development project.
Great that you used AI to build something useful, but it’s still weird to me when someone says “I built this”. Maybe the more correct way to say this is “I spec’d this”
I didn't know CMake introduced this debug adapter. This would have been very useful to me at some occasions.
Instead, I used printf debugging (aka `message(FATAL_ERROR )` debugging in CMake).
With this debug adapter, there also seem to be integrations in VSCode and CLion. I will have to try them out soon.