Raspberry Pi omxplayer device

[phenigma]

I agree that a qemu chroot enironment it is by far the easiest to setup and use initially.

J.

[hari]

I'm doing non-intel stuff for years now and have been through a lot of pain with different cross compiling environments and approaches. Native compilation also hurts as it takes ages, even with "beefy" cpus like the recent ARM ones. Using binfmt-misc and a static qemu in a chroot just rocks.

For interested readers, this is a good start: http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach

Instead of step 6) I'd just run /debootstrap/debootstrap --second-stage

[tschak909]

More importantly, this can be adapted so that MakeRelease can build arm packages for linuxmce. (I would suggest this as an exercise, to be able to run the Ubuntu_Helpers_NoHardCode scripts under such an environment.)

-Thom

[golgoj4]

1. i <3 this thread
2. how were you intending to approach the omxplayer and playing videos?
3. goddamned wait time for a pi!!!!!!!ack!!!

-golgoj4

[coley]

I'll wiki it once I go over my steps

Think this should cover it
http://wiki.linuxmce.org/index.php/RaspberryPi#Debian_Chroot_Environment
If I've missed something please update, or ping me and I will.

-Coley.

I should really get this thread back on topic

[phenigma]

More importantly, this can be adapted so that MakeRelease can build arm packages for linuxmce. (I would suggest this as an exercise, to be able to run the Ubuntu_Helpers_NoHardCode scripts under such an environment.)

-Thom

I am using MakeRelease and the Ubuntu_Helpers_NoHardCode scripts to build for the Pi within both a chroot/qemu environment AND a scratchbox cross-compile environment.  The qemu environment is by far and away simpler and easier to setup compared to the cross-compile method.

J.