Wiki de xouillet

User Tools

Site Tools

Trace:
xbmc-rpb_arch

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
xbmc-rpb_arch [2012/07/14 12:43] – created xouilletxbmc-rpb_arch [2015/10/13 16:48] (current) – external edit 127.0.0.1
Line 4: Line 4:
  
 This wiki will explain the steps I have followed to cross-compile the [[http://www.raspberrypi.org/|rasbperrypi]]-optimzed This wiki will explain the steps I have followed to cross-compile the [[http://www.raspberrypi.org/|rasbperrypi]]-optimzed
-xmbc named [[https://github.com/xbmc/xbmc-rbp|xmbc-rbp]].+xbmc named [[https://github.com/xbmc/xbmc-rbp|xbmc-rbp]].
  
 The compilation is done from an x86 computer and will generate arm binaries suitable for Raspberry Pi. All the The compilation is done from an x86 computer and will generate arm binaries suitable for Raspberry Pi. All the
Line 12: Line 12:
 ===== Why ? ===== ===== Why ? =====
  
-In fact, a PKGBUILD for xmbc-rbp is already available in [[http://aur.archlinux.org/packages.php?ID=60530|AUR]]. This package+In fact, a PKGBUILD for xbmc-rbp is already available in [[http://aur.archlinux.org/packages.php?ID=60530|AUR]]. This package
 is, as far as I know, fully functionnal « but » it respects [[http://archlinuxarm.org/developers/distcc-cross-compiling|Arch Linux ARM official way of generating package]] is, as far as I know, fully functionnal « but » it respects [[http://archlinuxarm.org/developers/distcc-cross-compiling|Arch Linux ARM official way of generating package]]
 that is compiling directly on the target device, eventually with the help of [[http://en.wikipedia.org/wiki/Distcc|distcc]] to distribute the work, even on x86 computer. that is compiling directly on the target device, eventually with the help of [[http://en.wikipedia.org/wiki/Distcc|distcc]] to distribute the work, even on x86 computer.
  
-The former method has the advantage that all the preprocessing is done on the target system, with target include/libraries/… which is much more simple.+The former method has the advantage that all the preprocessing is done on the target system, with target include/libraries/… which is much more simple, but the compilation of XBMC on  
 +the Rasperry Pi is long and painful. You need for example an extra swap space.
  
 The method explained here will do all the compilation on the x86 computer but will need to access the root system of the Rasbperry Pi for the libraries and include of extern libraries. The method explained here will do all the compilation on the x86 computer but will need to access the root system of the Rasbperry Pi for the libraries and include of extern libraries.
Line 36: Line 37:
   pacman -S hicolor-icon-theme fribidi lzo2 smbclient libtiff libpng libcdio yajl libmysqlclient libjpeg-turbo \   pacman -S hicolor-icon-theme fribidi lzo2 smbclient libtiff libpng libcdio yajl libmysqlclient libjpeg-turbo \
             libsamplerate libssh libmicrohttpd python2 libass libmpeg2 libmad libmodplug rtmpdump unzip xorg-xdpyinfo \             libsamplerate libssh libmicrohttpd python2 libass libmpeg2 libmad libmodplug rtmpdump unzip xorg-xdpyinfo \
-            libbluray libnfs afpfs-ng libshairport avahi bluez jasper tinyxml raspberrypi-firmware+            libbluray libnfs afpfs-ng libshairport avahi bluez jasper tinyxml raspberrypi-firmware boost
  
  
 ==== Mouting target system ==== ==== Mouting target system ====
  
-As explained in the [[xmbc-rpb_arch#why_?|Why section]], the target system must be accesible. For the moment, I have only tested by mounting the +As explained in the [[xbmc-rpb_arch#why_?|Why section]], the target system must be accesible. For the moment, I have only tested by mounting the 
 root partition of the Raspberry Pi SD on the compiler. root partition of the Raspberry Pi SD on the compiler.
  
 ==== Building ==== ==== Building ====
  
-Here your can find my [[http://www.xouillet.info/arch/xbmc-rbp/PKGBUILD|PKGBUILD]]. As you can tell, it is heavily base on the [[http://aur.archlinux.org/packages.php?ID=60530|xbmc-rbp-git] packet on AUR.+Here you can find my [[http://www.xouillet.info/arch/xbmc-rbp/PKGBUILD|PKGBUILD]]. As you can tell, it is heavily base on the [[http://aur.archlinux.org/packages.php?ID=60530|xbmc-rbp-git]] packet on AUR.
 I don't distribute it on AUR as it has no sense to be built and installed on the same platform. I don't distribute it on AUR as it has no sense to be built and installed on the same platform.
  
Line 65: Line 66:
 Then copy the **xbmc-rbp-git-20120714-1-x86_64.pkg.tar.xz** package on your Raspberry Pi, install it via Then copy the **xbmc-rbp-git-20120714-1-x86_64.pkg.tar.xz** package on your Raspberry Pi, install it via
  
-  pacman -U xbmc-rbp-git-20120714-1-x86_64.pkg.tar.xz+  pacman --arch=x86_64 -U xbmc-rbp-git-20120714-1-x86_64.pkg.tar.xz
      
 Start with Start with
Line 73: Line 74:
  
 And enjoy ! And enjoy !
 +
 +==== Post scriptum ====
 +
 +The architecture hack (makepkg -A and pacman --arch) is a bit dirty, but I can't find a way to build cross-compiled ArchLinux package in a nice way. If someone is aware of that, please mail me
 +(my address is in the PKGBUILD).
 +
 +===== Troubleshoots with XBMC =====
 +
 +XBMC-RBP works fine, very fine once installed, video are read fluenty, menus are quite fluent.
 +
 +Some bugs still appears, I will list then and their workaround as I find them.
 +
 +  * Screen flashes : when reading video, some blank screen appears. This can be removed with the workaround found [[http://archlinuxarm.org/forum/viewtopic.php?f=31&t=3004&start=60#p18411|here]]. It consists to add before running xbmc :
 +
 +  /opt/vc/bin/tvservice -o 
 +  /opt/vc/bin/tvservice -p
 +  xbmc
 +
 +Warning thought : It will blank your console, so the only access to your RPi will be via ssh.
 +
 +
 +
  
xbmc-rpb_arch.1342269806.txt.gz · Last modified: (external edit)