Building » History » Revision 2
Revision 1 (Adam Sutton, 2012-08-09 11:40) → Revision 2/32 (Adam Sutton, 2012-08-09 12:27)
h1. Building
h2. Prerequisites
Before you can build TVHeadend you will TODO: I need several packages installed on your development machine.
The specific details will vary between distributions so we only cover the major ones here.
h3. Debian/Ubuntu
<pre>
$ sudo aptitude install build-essential git
</pre>
> Optional:
<pre>
$ sudo aptitude install libavahi-client-dev
</pre>
h3. Redhat
TODO: to fill this needs adding
h3. Gentoo
TODO: this needs adding
h2. Get Source
Next you must obtain the source code, this is hosted on "github":https://github.com/tvheadend/tvheadend.
To clone the repository simple run the command:
<pre>
$ git clone https://github.com/tvheadend/tvheadend.git
</pre>
h2. 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:
<pre>
$ ./configure
</pre>
However for more advanced options, please run the following:
<pre>
$ ./configure --help
</pre>
And then re-run configure with the required options, i.e.:
<pre>
$ ./configure --enable-transcoder --disable-dvbscan
</pre>
h2. Compiling
To compile TVHeadend run:
<pre>
$ make
</pre>
h2. Installing
It is possible to install TVHeadend using make, based on the ./configure options, by running:
<pre>
$ sudo make install
</pre>
However it's recommend that you run from the build directory for development/testing:
<pre>
$ ./build.linux/tvheadend
</pre>
And that you build a [[Packaging|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.
h2. Packaging
For more information about packaging TVHeadend please see [[Packaging|here]]
h2. 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 [[bugreporting|here]]. in.
h2. Prerequisites
Before you can build TVHeadend you will TODO: I need several packages installed on your development machine.
The specific details will vary between distributions so we only cover the major ones here.
h3. Debian/Ubuntu
<pre>
$ sudo aptitude install build-essential git
</pre>
> Optional:
<pre>
$ sudo aptitude install libavahi-client-dev
</pre>
h3. Redhat
TODO: to fill this needs adding
h3. Gentoo
TODO: this needs adding
h2. Get Source
Next you must obtain the source code, this is hosted on "github":https://github.com/tvheadend/tvheadend.
To clone the repository simple run the command:
<pre>
$ git clone https://github.com/tvheadend/tvheadend.git
</pre>
h2. 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:
<pre>
$ ./configure
</pre>
However for more advanced options, please run the following:
<pre>
$ ./configure --help
</pre>
And then re-run configure with the required options, i.e.:
<pre>
$ ./configure --enable-transcoder --disable-dvbscan
</pre>
h2. Compiling
To compile TVHeadend run:
<pre>
$ make
</pre>
h2. Installing
It is possible to install TVHeadend using make, based on the ./configure options, by running:
<pre>
$ sudo make install
</pre>
However it's recommend that you run from the build directory for development/testing:
<pre>
$ ./build.linux/tvheadend
</pre>
And that you build a [[Packaging|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.
h2. Packaging
For more information about packaging TVHeadend please see [[Packaging|here]]
h2. 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 [[bugreporting|here]]. in.