-
Notifications
You must be signed in to change notification settings - Fork 33
Compiling Boxee
This is just a placeholder for me to put down stuff related to my attempt to compile Boxee. Keep note this is for attempting build on a 32-bit Ubuntu - if you are running 64-bit Ubuntu use the python2.4-minimal_2.4.6-1ubuntu3.2.9.10.1_amd64.deb which can be found at
# wget http://64.12.96.232/pool/main/p/python2.4/python2.4-minimal_2.4.6-1ubuntu3.2.9.10.1_amd64.deb
First you'll need to install Ubuntu Desktop (12.10). I've done so using VMWare Fusion (also working on Parallels 12.04.2 LTS 32 and 64bit versions - preferably LTS for stability - also, use a clean install disk, not the actual 'download from parallels' as this causes the user directories to become virtual and goofing up your paths / making you use '' to avoid this, use a clean disk)
After install is complete, download and extract both the IntelCE SDK and the Boxee 1.5.1 source. It can be found at bbx.boxee.tv . Just log in with your boxee account and you'll find it in the downloads section.
Versions I've been using are: boxee-sources-1.5.1-b6a5be1.tar.xz (boxee source) Intel-13.11.232647-dist.tar.bz2 (intelce sdk sources)
From a terminal window do:
# sudo apt-get install wget patch flex bison gettext libtool autoconf cmake nasm gperf g++ gawk doxygen swig libsdl-image1.2-dev liblzo2-dev php5-cli libncurses5-dev texinfo # cd /tmp # wget http://64.12.96.232/pool/main/p/python2.4/python2.4-minimal_2.4.6-1ubuntu3.2.9.10.1_i386.deb # sudo dpkg --install python2.4-minimal_2.4.6-1ubuntu3.2.9.10.1_i386.deb
Then install the IntelCE SDK by going into wherever you downloaded the intel sdk and then:
# cd BASE # ./installer # cd ../GPL # ./installer
The configure and install the SDK:
# cd ~ # cd IntelCE-13.232647 # make menuconfig
accept the default settings once they come up
# sudo make
This will fail at building the display module. To circumvent edit the file package/display/display.mk and in DISPLAY_DEPS remove hdmi_hdcp .
There are still some things that fail, but not yet sure if essential. Try:
# sudo make -k
After this is complete you should have the CE4100 SDK installed! (located in your home user directory /home/username/IntelCE-13.232647 or $HOME/IntelCE-13.232647)
Now setup the Boxee side:
# sudo mkdir /opt/canmore # sudo ln -s $HOME/IntelCE-13.232647/build_i686/staging_dir /opt/canmore/IntelCE # sudo ln -s $HOME/IntelCE-13.232647/build_i686/staging_dir/bin /opt/canmore/toolchains # sudo ln -s $HOME/IntelCE-13.232647/project_build_i686/IntelCE/root /opt/canmore/targetfs # sudo ln -s $HOME/IntelCE-13.232647 /opt/canmore/sdk
Edit your .bash_profile and add /opt/canmore/toolchains to the PATH. E.g. by adding:
# nano ~/.bash_profile
E.g. by adding:
export PATH=/opt/canmore/toolchains:$PATH
Refresh your .bash_profile by issuing (if outside your home directory):
# . ~/.bash_profileif you are inside your home directory simply type:
# . .bash_profile(that is a space between dots)
You should now be able to test whether everything works by running:
# i686-cm-linux-gcc
The build currently still fails horribly. So maybe we'll have to fix more build errors manually. (please post any errors that you find) so far i've gotten to the point of ./configure failing at MAD
We need to prepare some things for the Boxee build:
# cd /opt/canmore/IntelCE/include # sudo mv config.h config.h.orig
Then create the powervr.ini and platform_config.hcfg files:
# sudo nano /etc/powervr.ini
Fill it with:
DisableHWTextureUpload=1
Then:
# sudo mkdir /etc/platform_config # sudo mkdir /etc/platform_config/ce4100 # sudo nano /etc/platform_config/ce4100/platform_config.hcfg
Fill it with:
media_base_address = 0x28000000 //640M
Links https://github.com/Boxee/client-3rdparty - Buildchain for all thirdparty binaries on Boxee Box https://build.pub.meego.com/package/show?package=xbmc-gles&project=home%3Aarfoll%3Axbmc-testing - XBMC for Meego (which runs on CE4100 hardware, like the Cocom) http://code.google.com/p/googletv-mirrored-source/source/browse/?repo=v1#hg%2Fintel-sdk - Some other code packages that could help with the issues with the intel sdk?