How to compile? about omxplayer HOT 14 CLOSED

I've made some progress. I installed the g++-4.7-arm-linux-gnueabihf Ubuntu package but now getting the same issue as this guy: http://gcc.gnu.org/ml/gcc-help/2013-02/msg00174.html

david(pts/4)@Moogie:~/src/omxplayer.popcornmix/helloworld$ arm-linux-gnueabihf-gcc -g -mcpu=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -marm hello.c -Wl,-t -o hello
/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/../../../../arm-linux-gnueabihf/bin/ld: mode armelf_linux_eabi
/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/../../../../arm-linux-gnueabihf/lib/../lib/crt1.o
/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/../../../../arm-linux-gnueabihf/lib/../lib/crti.o
/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/crtbegin.o
/tmp/ccv1NZnT.o
libgcc_s.so.1 (/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/libgcc_s.so.1)
/usr/arm-linux-gnueabihf/lib/libc.so.6
(/usr/arm-linux-gnueabihf/lib/libc_nonshared.a)elf-init.oS
/usr/arm-linux-gnueabihf/lib/ld-linux-armhf.so.3
libgcc_s.so.1 (/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/libgcc_s.so.1)
/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/crtend.o
/usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/../../../../arm-linux-gnueabihf/lib/../lib/crtn.o

Can the Ubuntu-packaged cross-compiler be made to work in this context?

from omxplayer.

Hi, I'm going to reply point by point

1. No, you can't compile it for amd64/i386 due some libraries are RPi exclusive.

2. You should be able to compile it using that guide (but I've not tested it), seems to use the official RPi cross-compiler from https://github.com/raspberrypi/tools

I use huceke's buildroot (https://github.com/huceke/buildroot-rbp) which I forked to have updated kernel & firmware (https://github.com/skgsergio/buildroot-rbp).

3. I don't know if Ubuntu armhf's crosscompiler can produce valid code for RPi... I think that it can't produce code for arm6 with hard float...

from omxplayer.

I don't know why I appear to have been tagged in this topic but I'm now getting emails about it and I have no idea what this even is let alone why I've become involved?!

from omxplayer.

@Moogie probably you marked this project as "Watched"

from omxplayer.

Nope, I only signed up a few days ago to enquire about a jquery plugin, I have no idea what this is all about, although looking below this posting box I can see now it says I am receiving notifications because I was mentioned. I have no idea why I was mentioned.

from omxplayer.

lol @Moogie I see it now, the machine of the user which opened this issue is named "Moogie" so when it apears as user@machine it makes a mention to you. Go to "Watch" or "Unwhatch" and set it to Ignore.

from omxplayer.

lol on the @ _ Moogie issue :)

And thanks skgsergio, will follow your pointers.

Is the goal of the buildroot to produce an entire OS including xbmc or whatever app? I assume I don't need it if I'm just using omxplayer on Raspbian, correct?

from omxplayer.

That buildroot is a base system and toolchain if you follow the readme. Is ready for compiling xbmc and omxplayer.

Anyway later today or tomorrow (Central European Time) I'll release a set of scripts to create rpi build env under Debian (I assume it will work under Ubuntu too) that use the RPi official toolchain for building omxplayer (and whatever you want, but it will get ready the buildenv with the dependencies of omxplayer).

from omxplayer.

@skgsergio
I'd be happy to accept a PR that makes building easier.
I think the current makefile with buildroot as its default target is not something most people want.

I'd have thought building natively on Pi is the most common task.
Then building with a cross compiler from https://github.com/raspberrypi/tools
And buildroot would be a distant third.

from omxplayer.

@popcornmix Hmmm... I think the propper way to do this is using autotools but... I've never used it (tried once and failed).

I can re-organize the makefile and make an easy way to select one of the 3 methods. I have to thing about it before doing it...

On the other hand I'll create a github repo with scripts for "the second method" like I said previously

from omxplayer.

Autotools would be great, but not something I know how to do, and it doesn't look simple.
I was just thinking of a makefile with different targets or make variables to select the type of build.
(with the default being native build on pi).

from omxplayer.

Taking apart what @popcornmix said and I'll do soon...

Here you have a proper and easy to use build env: https://github.com/skgsergio/rpi-buildenv
You said you are using Ubuntu so you should not have problems (I've tried it on Debian).

Currently I'm doing a new install into a new Debian system to check I've not missed something.

from omxplayer.

Thank you @skgsergio

from omxplayer.

@popcornmix I believe this can be closed

from omxplayer.