Compiling / AutoBuild for Raspberry RPi

Todd D

Sorry, Noob, both to TVHeadend and compiling things.

I am having trouble building TVHeadend on the Raspberry Pi. Here is what I ran...
cd /usr/src/
git clone -b master https://github.com/tvheadend/tvheadend.git

cd /usr/src/tvheadend/

...to get things to compile I had to...

vi config

...and set (or I get the erros in the box)...

"libvpx_static:no"

cc: error: /usr/src/tvheadend/build.linux/ffmpeg/build/ffmpeg/lib/libvpx.a: No such file or directory
   Makefile:623: recipe for target '/usr/src/tvheadend/build.linux/tvheadend' failed
   make[2]: *** [/usr/src/tvheadend/build.linux/tvheadend] Error 1
   make[2]: Leaving directory '/usr/src/tvheadend'
   debian/rules:11: recipe for target 'override_dh_auto_build' failed
   make[1]: *** [override_dh_auto_build] Error 2
   make[1]: Leaving directory '/usr/src/tvheadend'
   debian/rules:5: recipe for target 'build' failed
   make: *** [build] Error 2
   dpkg-buildpackage: error: debian/rules build gave error exit status 2

"libfdkaac:no"

ERROR: fdk-aac package not found
   dh_auto_configure: ./configure --build=arm-linux-gnueabihf --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libexecdir=${prefix}/lib/tvheadend --disable-maintainer-mode --disable-dependency-tracking returned exit code 1
   debian/rules:8: recipe for target 'override_dh_auto_configure' failed
   make[1]: *** [override_dh_auto_configure] Error 2
   make[1]: Leaving directory '/usr/src/tvheadend'
   debian/rules:5: recipe for target 'build' failed
   make: *** [build] Error 2
   dpkg-buildpackage: error: debian/rules build gave error exit status 2

...then ran...

./Autobuild.sh

...and everything compiled, built into tvheadend_4.1-2322~g879d532-dirty_armhf.deb and seems install and run. I can see my ATSC EPG, schedule recordings and play them as .TS files. I have not tried (and don't plan on) transcoding them since I doubt the raspberry can handle it.

I had to edit config because trying to set all the different --disable-xyz flags didn't seem to do what I was expecting.

(Previously I had toyed around with things until I have an ATSC tuner running on /dev/dvb/adapter0/ ... It's a PCTV HD mini Stick 80e. So that was sorted.)

Quesitons:

1. What will my build of TVHeadendnot do? I have downloaded, compiled and installed then newest x264, x265 and FFMPEG, so those are already on my system.

2. How can I make this build work with all the normal options on?

Be gentle. I appologize in advance if this is info I should have been able to find via google/forum search...but I just couldn't find it.

Thanks,

Todd

PS Thanks for this nice piece of software. It runs at abotu 5% cpu while recording on my little RPi 2. It just works.

Jonathan Thomson

1) The "static" options simply mean that the code is "baked" into the tvheadend package/binary and needs no external packages - if you already have those packages then disabling the static options is fine

2) I found that the instructions on the wiki didn't work with me so I adapted/expanded them in "this" blog post on my site. I think there are missing dependencies in the wiki article which I've included in my post. The first guide deals with building tvheadend for installation on the build machine (i.e. no .deb file is created). For most people this is fine, but if you need to move the package to another machine you will need "this" guide which again has the updated dependancies list - this builds a .deb file which can be installed or moved between (similar) machines.

You don't actually need the .deb file - when the build completes, you can just "sudo make install" to install the binaries and jobs a good 'un.

Todd D

Thank you very much for the info. I'll check it very soon.

.deb packages....ya, I know, but I just feel better doing a package install. Also partly because as soon as there is an "official" 4.1 arm .deb, I will just switch over to using that. (I need 4.1 right now to get the ATSC EPG.)

Thanks again,
Todd

Jonathan Thomson

Just as an aside, you can install from source AND have the official repository configured in apt - if and when a new version is made available via apt, it will overwrite your self-built version, so you don't need the .deb version to do that either ;)