3 ms·
VS Code is a competent enough almost-IDE at least for a CMake project. The main issue I have so far is remote debugging in gdb appears not to work very well (y
by adhesive_wombat 5y ago
VS Code is a competent enough almost-IDE at least for a CMake project.
The main issue I have so far is remote debugging in gdb appears not to work very well (you can step but you can't use normal gdb commands on the console like you can locally).
Also the autocompletion seems to work only sometimes but that's likely my fault since I haven't actually configured that.
So far, it's working better for me than Sublime did, which was very laggy at times. Both are memory hogs, though.
- emerged 5y agoRemoteSSH extension is a far easier approach to debugging C++ remotely in VScode.
- adhesive_wombat 5y agoInteresting! Can you then debug remotely but still use local symbols and sources? The remote is a pretty weedy embedded platform, so you don't want to compile there, and I don't think there is even enough disk space for a complete checkout of the source. So you want to just run gdbserver there and have all the rest of the debugging junk running on a "real" computer.
- emerged 5y agoIt behaves as if you’re local to the machine. Changed my life when I first found it.
- IshKebab 5y ago> almost-IDE It is an IDE!