• The easiest approach is to donload the zipped UHSDR source code from Github UHSDR repository and unpack.
• If using Eclipse: create a work space pointing at the local directory where UHSDR has been unpacked. Check Eclipse settings after that (active build etc.)

• Download Github Desktop. The .exe file is the executable (portable) program and does not need installation
• Provide your github username and password, clone the Github UHSDR repository
• Optional: Create a local branch for your source code changes
• If using Eclipse: create a work space pointing at the local directory where UHSDR has been unpacked. Check Eclipse settings after that (active build etc.)

• If git is not intalled on your system:

  $apt-get install git

• Clone UHSDR repository:
  • Go to the directory where you want to store the GIT clone, then type

    $git clone https://github.com/df8oe/UHSDR.git

See also GNU MCU Eclipse workspace preferences

• Good if you need new Eclipse settings specially for this Github clone
• There will be a new Eclipse work space assigned to this import. The new work space can have its own Eclipse settings. Everytime you switch to this work space Eclipse will change all settings accordingly.
• Start Eclipse. File→Switch workspace→Other
• Enter directory of local UHSDR clone.
• When using this new work space Eclipse will use settings of UHSDR clone. So please check Eclipse settings (active build, ..)

• Good if this Github clone should work under your standard Eclipse settings
• File→Import, then General→Existing Projects into work space, hit “Next”
• “Select root directory”. Use “browse” button and point to local github mchf root (in my case: $HOME/uhdsrd/UHSDR/mchf-eclipse/)
• Hit “Finish”

The heart of any open source project is the contributions by individuals. Source code for the project is using git currently and can be found here. There is a good explanation of github workflow here that is worth a read before branching and hacking on the code. And an online book written directly from the git creators you can find here.

We have specific instructions for contributors collected in guidelines for contributing.

For own developments and experiments in code you should NOT use merge/pull to integrate your changes in df8oe's active-devel. Instead use git “rebase” command, as documented on our contribution page. We had very little trouble to follow that approach for the last two years. It also has its issues but in general, once you understand how to operate it, it works quite well. The main benefit of the rebase approach is that it keeps all your “local” changes together on top of the last official release you rebased on. Opposed to the merge approach you have been running, which does mingle your changes with the external changes in the time history.