Download

From GNU Radio
Revision as of 01:36, 8 March 2017 by Mbr0wn (talk | contribs) (Imported from Redmine)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Source Download instructions

Stable

The latest stable release, as well as older stable releases, of GNU Radio can be found here:
http://gnuradio.org/releases/gnuradio/

Also, check the news (in the box at the right) for announcements on the latest stable releases.

Development

Get the latest weekly development code as a tarball:

SHA1 Sum:

If you prefer the latest development code, wish to contribute to GNU Radio, or want to work with features that haven't yet made it into the stable branch, you can check out the source from the git repository:

$ git clone --recursive http://git.gnuradio.org/git/gnuradio.git

If you are using a legacy version of git (pre-1.6), use this command instead of the above:

$ git clone --recursive git://git.gnuradio.org/gnuradio

If you prefer a Github workflow, you can also fork or clone from our Github mirror. If you plan to merge your changes into the GNU Radio upstream, this is often the best method.

$ git clone --recursive https://github.com/gnuradio/gnuradio.git

Later, to update your local repository you can run:

$ git pull
$ git submodule update --recursive

The development code comes in three flavours: master, maint and next (these are in fact the names of the git branches). master is the main branch, which will be the next stable release. next is where all the crazy stuff is happening, the most bleeding edge code out there. maint is a maintenance branch of the most current release, i.e. the latest stable release plus bugfixes.

If you're using the git cloned code, you can switch between these three branches by going to your git-cloned repository and issuing the 'git checkout' command with the branch name desired. After a checkout, update submodules, like this:

$ git checkout maint
$ git submodule update --recursive

Even more bleeding-edge development code (Katana-edge)

The next branch is too stale for your taste? Some of the developers have exposed their development repositories. If you want to check these out, we're assuming you know what you're doing, so no more explanations: