{"id":8,"date":"2008-07-21T00:34:09","date_gmt":"2008-07-20T23:34:09","guid":{"rendered":"http:\/\/paguilar.org\/?p=8"},"modified":"2008-07-21T00:34:09","modified_gmt":"2008-07-20T23:34:09","slug":"compiling-enigma2-for-the-sh4-arch","status":"publish","type":"post","link":"https:\/\/paguilar.org\/?p=8","title":{"rendered":"Compiling enigma2 for the sh4 arch"},"content":{"rendered":"

[Update<\/strong>: A new post<\/a> that follows-up this one clarifies why compiling enigma2 for this arch may not be sufficient for running it properly]<\/p>\n

During the last days I’ve been asked to run enigma2 on the STb7109 cut 3.0 board, also called cocoref MB442, that is part of the sh4 arch family.<\/p>\n

Enigma2 is a DVR application that runs on top of Linux and several of the standard Linux subsystems such as the Frame-buffer,\u00a0 Linux DVB and V4L. It’s similar to applications such as MythTV, but it was designed and developed for running on embedded systems that have\u00a0 limited resources compared to a Desktop PC.<\/p>\n

I discovered that there are two different ways for doing this. The first one is through the use of a Makefile that downloads and compiles everything for you. This seems, of course, the easiest and fastest way for doing it, the only thing is that since it uses OpenEmbedded <\/a>that takes a lot of time<\/em> the first time for building the whole project since it downloads several GB of packages; then it compiles everything starting by generating the cross-toolchain; then it compiles all the requirements for enigma2; then it compiles enigma2 and generates a rootfs image ready for download to the target. This is a great procedure that eases your life after the first time, the big issue I had was that the enigma2 source didn’t compile, they gave me several errors.<\/p>\n

After waiting several hours for download everything, several GB less on my hard disk and compiling errors, I decided to do it manually: the configure<\/em>, make<\/em>, make install<\/em> way.<\/p>\n

——————————————————————————————————-<\/p>\n

License<\/strong><\/p>\n

The first issue that I found was that enigma2 has a weird<\/em> proprietary license that forbids you to modify, compile or do anything with the source code that you can download from here<\/a>.<\/p>\n

The only thing you can do is to take the version you download and derive a version\u00a0 that will be licensed under the GPLv2.<\/p>\n

That said, everything I describe in this procedure was done with a\u00a0 derived version of the official enigma2 source tree.<\/p>\n

——————————————————————————————————-<\/p>\n

Download the sources<\/strong><\/p>\n

The official enigma2 source code is obtained through the CVS tree. You can download a snapshot<\/p>\n

\ncvs -z3 -d:pserver:anonymous@dreamboxupdate.com:\/cvs co -P enigma2<\/pre>\n
or a certain release version:<\/p>\n
\ncvs -z3 -d:pserver:anonymous@dreamboxupdate.com:\/cvs co -r enigma2_rel24  enigma2<\/pre>\n
You will end up with a directory called enigma2.<\/p>\n
According to the license, you need to derive a version of this directory in order to do whatever you want. I derived a version and start the following procedure.<\/p>\n
——————————————————————————————————-<\/p>\n
Requirements <\/strong><\/p>\n
Enigma2 needs several packages in order to compile, I describe the installation of the packages I needed. Notice that enigma2 needs some other packages that I already had in my rootfs like libpng. I described the installation of some of those packages here<\/a>.<\/p>\n