Building¶

Prerequisites¶

Before you can build Tvheadend you will need several packages installed on your development machine.

The specific details will vary between distributions so we only cover the major ones here.

Debian/Ubuntu¶

$ sudo aptitude install build-essential git pkg-config libssl-dev bzip2 wget

Optional:

$ sudo aptitude install libavahi-client-dev zlib1g-dev libavcodec-dev libavutil-dev libavformat-dev libswscale-dev

Redhat / Centos / Fedora¶

Redhat/Centos/Fedora Build assumptions¶

Redhat/Centos/Fedora are a package managed OS and as such tvheadend should be installed from an rpm on a production system.  
This set of instructions details using tools git, mock and rpmbuild to package the source into an rpm and then install the rpm

Build Environment Configuration¶

install the software used for building tvheadened
$sudo yum install git mock

create a user to do the building as -- this is not a requirement, but does provide a modicum of compartmentaliztion when building
$sudo useradd -g mock mock
$sudo passwd mock

for more details view the Centos/Fedora Mock pages starting
     http://fedoraproject.org/wiki/Projects/Mock

Getting the files to work with¶

tvheadend sources are retrieved as follow
$su mock
$mkdir git
$cd git
$ git clone https://github.com/tvheadend/tvheadend.git

create a workfiles holding directory
$mkdir ~/tvheadend

you'll also need a starter source rpm and specfile such as attached placed in the ~/tvheadend folder:
      tvheadend-3.9.2618-git.e5dc86b.1.spec
      tvheadend-3.9.2618-git.e5rc86b.1.el7.centos.src.rpm

Step by Step Building the RPM¶

enter the local git repository and reset local to most current remote
$cd ~/git/tvheadend
$git fetch origin
$git reset --hard origin/master

determine the commit id of the master branch - for ex. "e5dc86b3dd32f80c337da75cc0d2e00702c45fe1" 
$git show-ref --head

determine the version id of this build as well - for ex. "v3.9-2618-ge5dc86b"

$git describe --dirty --match "v*" 

create the spec file for the next version note new and old are the revision strings
in this example tvheadend-new-spec would be tvheadend-3.9.2618-git.e5dc86b.1.spec

$cp tvheadend-old.spec tvheadend-new.spec

open the new spec and edit as follows
update the global commit string to match the current master commit - for ex. "e5dc86b3dd32f80c337da75cc0d2e00702c45fe1"
change the version string to match the new being built - - for ex. version "3.9-2618" note the revision is automatic
except for the 1,2,3 or whatever patch might be applied
change the git archive comment line to be the correct values commit tag and filename
change the source0 filename also
also modify the changelog to reflect the new version
save the spec file for use later

$vi tvheadend-new.spec

switch to the git tvheadened master and export the archive file called for in the new spec to the ~/tvheadend folder

$cd ~/git/tvheadend
$git archive e5dc86b3dd32f80c337da75cc0d2e00702c45fe1 --format=tar --prefix=tvheadend/ | gzip > ../tvheadend-3.9.2618-git.e5dc86b.tar.gz
$mv ../tvheadend-3.9.2618-git.e5dc86b.tar.gz ~/tvheadend

mock setup {for Fedora you'll need to use the rpmfusion environment} {for centos you'll need to use nuxro's repos as an environment}
the /nux-7-x86_64.cfg attached works for me with nux.ro's repo and centos7

[nux-dextop]
name=Nux.Ro RPMs for general desktop use
baseurl=http://li.nux.ro/download/nux/dextop/el7/$basearch/ http://mirror.li.nux.ro/li.nux.ro/nux/dextop/el7/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nux.ro
protect=0

[nux-dextop-testing]
name=Nux.Ro RPMs for general desktop use - testing
baseurl=http://li.nux.ro/download/nux/dextop-testing/el7/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-nux.ro
protect=0

clean the mock build environment

$mock --init -r nux-7-x86_64

now build the previous version in the clean environment

$mock -r nux-7-x86_64 --rebuild tvheadend-3.9.2618-git.e5dc86b.1.el7.centos.src.rpm

copy in the new source tar and spec files

$mock -r nux-7-x86_64 --no-clean --copyin tvheadend-3.9.2618-git.e5dc86b.1.tar.gz builddir/build/SOURCES/
$mock -r nux-7-x86_64 --no-clean --copyin tvheadend-3.9.2618-git.e5dc86b.1.spec builddir/build/SPECS/tvheadend.spec

shell in and confirm new source and spec are present and then build new src.rpm

$mock -r nux-7-x86_64 --no-clean --shell
<mock>$ls -lah builddir/build/SOURCES
<mock>$ls -lah builddir/build/SPECS
<mock>$rpmbuild -bs builddir/build/SPECS/tvheadend.spec
<mock>$exit

copy out the new src.rpm

$mock -r nux-7-x86_64 --no-clean --copyout builddir/build/SRPMS/tvheadend-3.9.2618-git.e5dc86b.1.el7.centos.src.rpm ./

build the new version from the source rpm

$mock -r nux-7-x86_64 --rebuild tvheadend-3.9.2618-git.e5dc86b.1.el7.centos.src.rpm

move the results to your working folder

$cp /var/lib/mock/nux-7-x86_64/result/*.rpm ./

Install the RPM¶

$sudo yum install /home/mock/tvheadend/tvheadend-3.9.2618-git.e5dc86b.1.el7.centos.x86_64.rpm

Gentoo¶

TODO: this needs adding

Get Source¶

Next you must obtain the source code, this is hosted on github.

To clone the repository simple run the command:

$ git clone https://github.com/tvheadend/tvheadend.git

Configuring¶

TVHeadend comes with a configuration script that allows you to enable/disable optional components and set install paths, etc.

Most people will be fine with the defaults and can run:

$ ./configure

However for more advanced options, please run the following:

$ ./configure --help

And then re-run configure with the required options, i.e.:

$ ./configure --disable-dvbscan

Compiling¶

To compile Tvheadend run:

$ make

Installing¶

It is possible to install Tvheadend using make, based on the ./configure options, by running:

$ sudo make install

However it's recommend that you run from the build directory for development/testing (see Development):

$ ./build.linux/tvheadend

NOTE: its VERY important you run test builds from git root, so command should look similar to above.

And that you build a package if you wish to install Tvheadend permanently and hook into the system start scripts etc.

Use of make install is not very traceable and so removal can sometimes be painful, and it might overwrite an existing installation.

Packaging¶

For more information about packaging Tvheadend please see here

Reporting Problems¶

If you have problems with a custom compiled version of Tvheadend its important that any issue reports include details of the specific version of source you used. For more details please see here.