Kodi Community Forum

Full Version: how to actually install Kodi after cross-compiling?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5
I finally succeeded in cross-compiling Kodi for the RPi2 using the README.raspberrypi that came with the source. Question is now... how exactly to install it on my Pi? I tried copying files to directories that mirrored an install from a native compile on the Pi itself, but then it crashes saying it can't find Kodi data files. After copying the /xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/bin/kodi to the Pi's /usr/local/bin, it complained it couldn't find files in arm-linux-gnueabihf. Am I supposed to copy the entire /opt/xbmc-bcm folder to the Pi's /opt directory, and run it from there?
@greenbag

with
Code:
mkdir XXXXX/root-kodi/
make install DESTDIR=XXXXX/root-kodi/

where the actual dir and environment (build machine) is still the one you used to build it.
then XXXXX/root-kodi will be "rootfs" of the installation (so meaning "/" on RPI). what you find there - is going to be copied to / on target device.
(2016-04-04, 12:47)mk01 Wrote: [ -> ]@greenbag

with
Code:
mkdir XXXXX/root-kodi/
make install DESTDIR=XXXXX/root-kodi/

where the actual dir and environment (build machine) is still the one you used to build it.
then XXXXX/root-kodi will be "rootfs" of the installation (so meaning "/" on RPI). what you find there - is going to be copied to / on target device.

Thanks for the reply. Smile

I'm still a little lost. Following the directions, even on the same Ubuntu release, the build was in /opt, and files were copied to:

Code:
$ sudo apt-get install git autoconf curl g++ zlib1g-dev libcurl4-openssl-dev gawk gperf libtool autopoint swig default-jre

    $ git clone https://github.com/raspberrypi/tools

    $ sudo cp -r tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64 /opt

    $ git clone https://github.com/raspberrypi/firmware

    $ sudo mkdir -p /opt/bcm-rootfs/opt

    $ sudo cp -r firmware/opt/vc /opt/bcm-rootfs/opt

    $ sudo mkdir -p /opt/xbmc-bcm

    $ sudo chmod 777 /opt/xbmc-bcm

    $ git clone https://github.com/xbmc/xbmc

    $ cd xbmc/tools/depends

    $ ./bootstrap

    PATH="$PATH:/opt/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin" \
       ./configure --host=arm-linux-gnueabihf \
       --prefix=/opt/xbmc-bcm/xbmc-dbg \
       --with-toolchain=/usr/local/bcm-gcc/arm-bcm2708hardfp-linux-gnueabi/sysroot \
       --with-firmware=/opt/bcm-rootfs \
       --with-platform=raspberry-pi \
       --build=i686-linux

    $ make -j4

    $ cd ../..

    CONFIG_EXTRA="--with-platform=raspberry-pi \
       --enable-libcec --enable-player=omxplayer \
       --disable-x11 --disable-xrandr --disable-openmax \
       --disable-optical-drive --disable-dvdcss --disable-joystick \
       --disable-crystalhd --disable-vtbdecoder --disable-vaapi \
       --disable-vdpau --enable-alsa" \
    $ make -C tools/depends/target/xbmc

    $ make -j4

    $ sudo make install


-----------------------
Kodi built successfully
-----------------------
greenbag@lotusland:~/xbmc$ sudo make install
[sudo] password for greenbag:
Copying kodi binary to /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/
You can run kodi with the command 'kodi'
Copying support and legal files...                                            
Done!
Copying system files to /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/share/kodi
Copying bindings to /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/include/kodi

I then looked at where everything went from an install from a compile on the Pi..

/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/share/kodi is the .kodi directory that goes in /home/username (addons, media, system, userdata)

/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/bin/kodi is the shell script that goes in /usr/local/bin

/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/include/kodi contains a bunch of *.h files that go to /usr/local/include

/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi contains kodi.bin, /addons, /system and some *.cmake files.... I think I just found at least 1 error.. I only copied kodi.bin, not even the directory. That might be the system files it's looking for. Whoops.

Also.. I just noticed 3 symlinked xbmc folder in the build directory.. are they to be copied over as well? There's also xbmc, xbmc-standalone, xbmc.desktop. I only copied the kodi* files.

/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/include/xbmc
/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/xbmc
/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/share/xbmc

The /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/bin/kodi shell script is prefixed to...

Code:
APP=Kodi
bin_name=kodi
SAVED_ARGS="$@"
prefix="/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf"
exec_prefix="/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf"
datarootdir="${prefix}/share"
LIBDIR="${exec_prefix}/lib"
CRASHLOG_DIR=${CRASHLOG_DIR:-$HOME}
USERDATA_DIR="${HOME}/.${bin_name}"

Does that need to be changed as well? Did I just go about this the wrong way to begin with?
I don't know why you ommited DESTDIR=XXXXX parameter Smile) so again -- assuming "make -j4" is your last command and Kodi is build:

Code:
mkdir -p /opt/xbmc-bcm/INSTALLED/usr/local
make install DESTDIR=/opt/xbmc-bcm/INSTALLED/usr/local

- /usr/local is default prefix (you have not specified different).
- so after "install" you will have include/xbmc, lib/xbmc, share/xbmc under /opt/xbmc-bcm/INSTALLED/usr/local

- and again, /usr/local is already part of final location. that means, if you on RPI /opt would also be accessible, you do :
Code:
cd /opt/xbmc-bcm/INSTALLED
cp -av ./ /

or

Code:
cd /opt/xbmc-bcm/INSTALLED
tar -c * | gzip > ../kodi-compiled-myself.tar.gz

what would be then unpacked on RPI's rootfs
Code:
cd /
tar -zxf ................compiled-myself.tar.gz
(2016-04-04, 13:36)mk01 Wrote: [ -> ]I don't know why you ommited DESTDIR=XXXXX parameter Smile) so again -- assuming "make -j4" is your last command and Kodi is build:

Code:
mkdir -p /opt/xbmc-bcm/INSTALLED/usr/local
make install DESTDIR=/opt/xbmc-bcm/INSTALLED/usr/local

- /usr/local is default prefix (you have not specified different).
- so after "install" you will have include/xbmc, lib/xbmc, share/xbmc under /opt/xbmc-bcm/INSTALLED/usr/local

- and again, /usr/local is already part of final location. that means, if you on RPI /opt would also be accessible, you do :
Code:
cd /opt/xbmc-bcm/INSTALLED
cp -av ./ /

or

Code:
cd /opt/xbmc-bcm/INSTALLED
tar -c * | gzip > ../kodi-compiled-myself.tar.gz

what would be then unpacked on RPI's rootfs
Code:
cd /
tar -zxf ................compiled-myself.tar.gz

Sorry.... that was the actual instructions in the readme that I followed before you mentioned it. I was just showing how I got to where I am. Your explanation's a lot clearer... I shall give it a shot.

Thanks. Smile
So... it installs everything to /opt on the Pi, and running "kodi" isn't recognised. Running it from the /usr/local/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/bin says permission denied.

Sorry to sound daft, but shouldn't the install have installed to the same directories as an actual install from a repository.. ie: putting .kodi in /home/username?

How the hell do you run this then? Tongue
.kodi in user home is created upon first start.


btw: are we sure, we do exactly the same ? Smile look:
Code:
mk@media:~/BUILD/xbian-package-xbmc/build/imx6-v17/working$ mkdir /tmp/XXXXX; make install DESTDIR=/tmp/XXXXX
Copying kodi binary to /tmp/XXXXX/usr/local/lib/kodi/
(2016-04-05, 00:48)mk01 Wrote: [ -> ].kodi in user home is created upon first start.


btw: are we sure, we do exactly the same ? Smile look:
Code:
mk@media:~/BUILD/xbian-package-xbmc/build/imx6-v17/working$ mkdir /tmp/XXXXX; make install DESTDIR=/tmp/XXXXX
Copying kodi binary to /tmp/XXXXX/usr/local/lib/kodi/

I literally c/p'd the commands you gave me, so yeah.. I'm sure we do the exact same. The only difference, was I called mine kodi16.tar.gz, so the last command "after" copying the tarball to the pi's root was...

Code:
cd /
tar -zxf kodi16.tar.gz

No difference really.


edit: I just tried again, this time running it from /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/bin instead of /usr/local/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/bin. It worked.. and yes, created ~/.kodi upon first use. Smile

I guess I just tried starting it from the wrong directory before. lol. Tongue

Thanks for the help mk01.. I never would have gotten it. Big Grin
@greenbag: try "sudo checkinstall". This will result in a .deb file which you can install on your raspberry (dpkg -i). Theoretically this worked for me, but there must be some other error during the cross compiling process (althoug the make process ended with a success message). The size of my kodi.bin is 371MB. Do you have an idea what the problem could be?
@rucksman

The size issue is due to kodi.bin not being stripped of debug symbols. Run strip on the Raspberry Pi against kodi.bin

Edit add --disable-debug to your configure line for a smaller kodi.bin
Thanks for your quick reply, MikeB2013. Strangely enough
Code:
strip -s --input-target=binary /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/kodi.bin
changes nothing on the size. It's exactly the same size before and after the strip-command. I had to use --input-target=binary because without it I got an error (saying that the format of the file could not be recognized).
(2016-04-05, 11:36)rucksman Wrote: [ -> ]Thanks for your quick reply, MikeB2013. Strangely enough
Code:
strip -s --input-target=binary /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/kodi.bin
changes nothing on the size. It's exactly the same size before and after the strip-command. I had to use --input-target=binary because without it I got an error (saying that the format of the file could not be recognized).

You need to do the strip on the Raspberry Pi (sudo strip <path-to>kodi.bin) assuming Raspbian Jessie. I seem to recall running it on Ubuntu did not work - its been a while since I tried, I am building native in Raspberry Pi (using an SSD).

Mike
(2016-04-05, 08:51)rucksman Wrote: [ -> ]@greenbag: try "sudo checkinstall". This will result in a .deb file which you can install on your raspberry (dpkg -i). Theoretically this worked for me, but there must be some other error during the cross compiling process (althoug the make process ended with a success message). The size of my kodi.bin is 371MB. Do you have an idea what the problem could be?

Thanks, rucksman... I was just about to ask how to deb package it.. lol. Big Grin I tried using checkinstall when compiling on the pi, while running Ubuntu Mate.. it says it installed the files, but then complains it can't find a tar file... then gets stuck in a loop looking for what looks like translation packages.. "entering CAN... not found, exiting, entering ITA... not found, exiting....". That was paraphrasing, but you get the idea. It looked as if it would work while compiling on Raspbian Jessie... but then it froze on me while making the *deb package. I prefer Ubuntu over Raspbian... much more stable, and I can compile using -j4 without it freezing on me. Need to use a swap partition, but it works. I could also enable libbluray in kodi's compile... even though the same libbluray1 and libbluray-dev were installed in Raspbian as in Ubuntu, it kept telling me libbluray wasn't installed and would stop on error.. required library not found. Ubuntu Mate compiled it no problems. Ubuntu 14.04 LTS was another story though... I couldn't get the required libraries installed to compile kodi to begin with. I prefer 14.04 LTS out of all the os's though.. it's maintained by Ubuntu themselves, it's not a community project like Ubuntu Mate. It'll also be supported for a few more years along with the desktop version of 14.04 LTS.

But after finally getting the cross-compile to work... I'll never compile on the Pi again... except for tvheadend server.. haven't figured out a cross-compile for that yet. Running ./Automake.sh creates a deb file though, so only have to do it once. Tongue

I shall try to checkinstall kodi into a deb package from my Ubuntu desktop. It'll make life so much easier. And I can install on Ubuntu 14.04. Smile




edit: btw... the reason I was having issues cross-compiling to begin with, is I seemed to have left out the "\" at the end of the CONFIG_EXTRA section. I reconfigured everything into 1 line, removing the \ breaks, as if I would do if compiling ffmpeg. I didn't realize that \ at the end actually set up the config for the "make -C" command that followed. I thought I screwed up when I was stuck with "<" at the beginning of the lines, and there was no $ to indicate ready for the next command. That only took me a week to figure out. Tongue

Code:
CONFIG_EXTRA="--with-platform=raspberry-pi \
       --enable-libcec --enable-player=omxplayer \
       --disable-x11 --disable-xrandr --disable-openmax \
       --disable-optical-drive --disable-dvdcss --disable-joystick \
       --disable-crystalhd --disable-vtbdecoder --disable-vaapi \
       --disable-vdpau --enable-alsa" \
$ make -C tools/depends/target/xbmc
(2016-04-05, 08:51)rucksman Wrote: [ -> ]@greenbag: try "sudo checkinstall". This will result in a .deb file which you can install on your raspberry (dpkg -i). Theoretically this worked for me, but there must be some other error during the cross compiling process (althoug the make process ended with a success message). The size of my kodi.bin is 371MB. Do you have an idea what the problem could be?

lol... it seems that tar error I was mentioning popped up on me again, but this time I let it run through... and it actually continued to build the deb package. I guess I didn't wait long enough when trying on the Pi itself.. I only waited 20 minutes. Tongue

Code:
This package will be built according to these values:

0 -  Maintainer: [ root@lotusland ]
1 -  Summary: [ Kodi16.1 ]
2 -  Name:    [ xbmc ]
3 -  Version: [ 16.1.000 ]
4 -  Release: [ 1 ]
5 -  License: [ GPL ]
6 -  Group:   [ checkinstall ]
7 -  Architecture: [ amd64 ]
8 -  Source location: [ xbmc ]
9 -  Alternate source location: [  ]
10 - Requires: [  ]
11 - Provides: [ xbmc ]
12 - Conflicts: [  ]
13 - Replaces: [  ]

Enter a number to change any of them or press ENTER to continue:

Installing with make install...

========================= Installation results ===========================
Copying kodi binary to /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/
You can run kodi with the command 'kodi'
Copying support and legal files...                                            
Done!
Copying system files to /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/share/kodi
Copying bindings to /opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/include/kodi    

======================== Installation successful ==========================

Copying files to the temporary directory...tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Australia): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Zealand): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Canada): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Argentina): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (India): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Australia): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Zealand): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Canada): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Argentina): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (India): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Zealand): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Canada): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Devanagiri): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Argentina): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (India): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Australia): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Zealand): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Canada): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Devanagiri): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mongolia): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Iran): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Cyrillic): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Argentina): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (India): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Australia): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Zealand): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Canada): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Devanagiri): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mongolia): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Iran): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Cyrillic): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Argentina): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (India): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

OK

Stripping ELF binaries and libraries...strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/addons/library.xbmc.codec/libXBMC_codec-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/addons/library.xbmc.addon/libXBMC_addon-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/addons/library.kodi.adsp/libKODI_adsp-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/addons/library.kodi.audioengine/libKODI_audioengine-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/addons/library.xbmc.pvr/libXBMC_pvr-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/addons/library.kodi.guilib/libKODI_guilib-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/kodi.bin'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/system/players/dvdplayer/libdvdnav-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/system/libcpluff-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/system/ImageLib-arm.so'
strip: Unable to recognise the format of the input file `/var/tmp/tmp.WWx5IuTBpT/package/opt/xbmc-bcm/xbmc-dbg/arm-linux-gnueabihf/lib/kodi/system/libexif-arm.so'
OK

Compressing man pages...OK

Building file list...OK

Building Debian package...
OK

Installing Debian package...OK

Erasing temporary files...OK

Writing backup package...OK
OK

Deleting temp dir...OK


**********************************************************************

Done. The new package has been installed and saved to

/home/greenbag/xbmc/xbmc_16.1.000-1_amd64.deb

You can remove it from your system anytime using:

      dpkg -r xbmc

**********************************************************************

greenbag@lotusland:~/xbmc$


Mine just came to 99.9MB's.
I had the same issues with the languages, but I did not care too much about it as long as it finished successfully.

Concerning the CONFIG_EXTRA: I did the exact same thing (reconfigure everything into 1 line and removing the \) and was not successful at all like you. In the end I did put the whole CONFIG_EXTRA stuff in one line into the Makefile in tools/depends/target/xbmc/ which worked for me.

I did all the cross compiling and checkinstall in a VM running Ubuntu 14.04.

Probably your deb package won't work due to the "7 - Architecture: [ amd64 ]" (at least it did not work for me). I had to change it to "armhf" which then built a working .deb file for the raspberry.
Pages: 1 2 3 4 5