Glad to see there's more than me looking at the Pi and lmce.
What dev environment have you set up? is it a scratchbox type setup?
I started cross compiling some of the pluto libs as their code is currently compiled into qOrbiter, and they'll be needed as libs if any DCE devices are to run on the Pi. But I was messing with too many makefiles and parked it. Then you chimed in
I was thinking of the media stuff and probably the best route, correct me if I'm wrong, would be to create an omxplayer device for the Pi as that is specifically built for the Pi and can make use of the h/w acceleration.
Wheezy seems to be a bit faster according to some reports and also there is a hardfp image of wheezy out there.
Sorry, took off to the cottage after that post. No internet there.
I setup a scratchbox environment and a 1004 build enironment. I added configuration files for an armel squeeze build and altered MakeRelease to use the scratchbox environment. I altered the build database so debian squeeze was used and updated package names in the database that were different/redundant/not required under debian. Then I altered many makefiles to permit the use of the armel build libraries through a variable, and added the library directories to the variable in the existing build scripts (buildmaindebs) and began building the system. Then I set about installing the packages for an MD and doing some manual configuration to get the system to boot. So I am essentially using the standard old build system with scratchbox, database data for squeeze and configs for debian squeeze armel.
I will likely rebuild for wheezy hardfp (probably raspian). I wasn't aware of omxplayer, sounds like a great way to go. We can continue this discussion in another thread if you wish, little OT for this one.