3 ms·
I use Eclipse CDT often. It's gotten gradually less painful and annoying over past years (and maybe I've done less to misconfigure it).
by einpoklum 6y ago
I use Eclipse CDT often. It's gotten gradually less painful and annoying over past years (and maybe I've done less to misconfigure it).
- cardiffspaceman 6y agoI used CDT until last year, and advocated it. I checked on the remote file access situation last March. because I remembered using the Eclipse solution for remote file access in 2014. However in 2020, the plug-in for it seemed to be orphaned or off-support in favor of a planned release in the distant future that would revive it. Meanwhile my colleagues were using VSCode with its solution. My biggest problem with CDT is setting up include paths and basing that and other parts of CDT on the actual cross compiler I use. I have a gazillion trees of source code at any given time, and they all have a related set of include paths and compiler settings. This is much easier to configure for VSCode than for CDT. In CDT each individual line item (and there can be dozens) has to be typed into a modal dialog box (remember those?). In VSCode this is all managed from a single JSON file. So on-boarding one of my trees is pretty easy. The downside is that VSCode's Intellisense wouldn't know a super class if the super class walked up with a big S on the chest of its uniform and said, I'm the super class. You can search for references to a symbol in VSCode but this is leaned on a little too hard in my opinion. The navigation story is a bit degraded.
- aidenn0 6y agoMaybe I'll try it again. The last time I used it (maybe 2013?) it was a hot mess. I spent an entire week with it to give it a fair shake, and it was terrible.
- einpoklum 6y agoConsider trying it again, but make sure not to reuse an old workspace/project, since you'll be importing a bunch of hot mess :-)