Revision handling and packaging
Keeping track of your source code means greater control of revisions.
The most popular way to handle revisions is to use git. The git protocol has become the solution of choice for most projects. If you want to contribute to an ongoing project on Github then git is essential. The legacy protocols for version control are Subversion (SVN) and the Concurrent Versioning System (CVS). Developers are still using these, although their focus has turned to git because of how well it handles branching.
Once you’ve finished the first version of your program, you need to send it out for people to run. Developers will compile from source, but users need a binary package.
Eclipse makes use of a Github plugin for importing any project. Git is integrated with a plugin, but other systems that come as standard are in the import menu. In that menu you can install from many different sources, including RPM source and a host of online platforms. Once you’ve finished debugging you can create a binary file. Java is built-in, but if you’re using other languages then you’ll need to get hold of the appropriate plugins.
Netbeans handles all revisions within its Teams menu. It supports Git Mercurial and subversion. Cloning from a remote is supported because the wizard accepts a URL. Submodules will be cloned automatically unless you decide otherwise. Adding files and committing changes is done in the Git Repository Browser.
When you set your project for building, you can package it for RPM and Debian packages, although this isn’t the usual approach.
Pycharm supports Git, Mercurial and Subversion, and has Github integration, which is handled well. Qt Creator also has a simple but powerful interface for git with different functions.
Code::blocks requires you to add a plugin to handle git. It hasn’t been updated since 2015, so you may want to use other git tools. Sending the final binary to platforms and making app images may be a challenge. The solution is to set the compiler targets correctly.