microsoft / vscode-cmake-tools

CMake integration in Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=vector-of-bool.cmake-tools
MIT License
1.47k stars 453 forks source link

Remove the debugging/running feature with F7 and use the vs-code defaults #552

Open robclouth opened 6 years ago

robclouth commented 6 years ago

Firstly: great extension! I use it all the time and I love it. Thanks for putting in the effort.

I have a suggestion though: integrate further with cpptools to automatically create a launch file and/or build tasks instead of having your own custom system with custom shortcuts. I think it would fit better into the vscode way of doing things if you could press F5 to run and so on.

That's all! Thanks.

grigorig commented 5 years ago

This wouldn't just be better, the current implementation is extremely confusing. It took me some time to figure out that the cpptools launch configuration is completely separate from the cmake-tools launch configuration.

I actually wouldn't mind a cmake-tools specific debug/run system, as long as it doesn't conflict with the cpptools debug/run features, or if it replaces them.

andreeis commented 4 years ago

Related to https://github.com/microsoft/vscode-cmake-tools/issues/1202.

vbrzeski commented 4 years ago

Going to second what @grigorig said as I spent a day learning something that doesn't seem entirely useful :)

Great plugin regardless!

Zingam commented 2 years ago

Is there any chance for a proper integration of cpptools and cmake-tools? I don't know what is exact situation but it's confusing for other language integrations too. For example a debugger extension intercepts F5 instead of the language integration extension. Can a language extension take precedence over the debug extension in that case? I have no idea. I cannot find official VSCode recommendations how to implement a proper integration.

pktiuk commented 1 year ago

That's a shame, that such a crucial addon for C++ development is not so well integrated with cpptools.