Library sources

The library sources are hosted on GitHub with Git to manage the sources. There are currently 2 Git branches available. If you don't know how to use Git yet, don't be afraid. It is easy to learn. Follow the Git Getting Started guide.

In short, you can get the code as follow:

$ git clone --depth 10 https://github.com/didier-barvaux/rohc.git
$ cd rohc/

Then follow the wiki instructions to learn how to build the library from sources.

master branch (active development)

The master branch represents the primary line of development.

You can get the code as follow:

$ git clone --depth 10 https://github.com/didier-barvaux/rohc.git
$ cd rohc/
$ git co master

You can also browse the master code online.

2.0.x branch (stable)

The 2.0.x branch is bugfix-only branch for the maintenance of the 2.0.0 release. The 2.0.x releases are fully supported. They will become old stable as soon as major version N+1 will be released.

You can get the code as follow:

$ git clone --depth 10 https://github.com/didier-barvaux/rohc.git
$ cd rohc/
$ git co 2.0.x

You can also browse the 2.0.x code online.

1.7.x branch (old stable)

The 1.7.x branch is bugfix-only branch for the maintenance of the 1.7.0 release. The 1.7.x releases are in maintenance mode. Only very important fixes may be committed.

You can get the code as follow:

$ git clone --depth 10 https://github.com/didier-barvaux/rohc.git
$ cd rohc/
$ git co 1.7.x

You can also browse the 1.7.x code online.

Releases

Next major release: 2.1.0 Git branch roadmap
Current stable release: 2.0.0 download release notes
Previous stable release: 1.7.0 download release notes

Sponsors

Viveris Technologies logo
Viveris Technologies
provides to the project the skills of its engineering teams in the telecommunications, network and Linux fields.

Viveris Technologies proposes the knowledge and expertise gained on the ROHC library to companies and people that are interested in network header compression, but do not have the skills or the time to integrate the ROHC mechanisms in their application or infrastructure.

back to top