![]() PS: Also, Remote Development is a great feature that's available in VS Code (although I still prefer remote debugging in CLion). Share Improve this answer Follow answered at 10:25 Thibaut M. It has (or had in the previous version) some neat niche features like calculating struct/class size, macro expansion - also available in CLion now. In Clion configure the Remote Host to login as root (Files->setting->Build, Execution, Deployment->Toolchains->Credentials). One exception that I've noted is if your project heavily uses template meta programming (ie.: uses boost hana/fusion heavily), CLion can get unusably slow. ![]() While opening a bigger project with large cc files, the analysis is running over and over while typing taking constantly one or two CPU forcing me to disable analysis completely. Now it works only for 'hello world' projects. In the long run if you're going to spend alot of time with a project, even just for reference, properly setting it up with CMake is worth it and CLion is almost always the better choice when this can be done. I use Clion from version 2019.2 with remote development support. VS Code is also an excellent choice for mix language projects or opening a directory with human readable data files. While the latter provides users with an UI, the backend server is needed for hosting the source code and running a headless version of the IDE the user is subscribed to. I use CLion projects that I spend more time on and VS Code to open projects for quick reference as a file browser + viewer. Remote development is realised via a remote IDE backend and a local thin client. Use CLion and the enabled Remote Development Gateway plugin in it. I think this is the better way since both have their own strengths and weaknesses (Plus, it won't cost anything extra to keep VS Code around)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |