can you send me your .config files please, for hard and soft.
I had looked at crosstool and buildroot when I started on this - but when I could just get the bcm toolchain from git I parked it.

thanks,
-Coley.

armel for now - AFAIR I need 64bit host for bcom toolchain cross to hfp. I didn't dig too far.
I did download the new rasbian image today so might take that for a whirl.

-Coley.

I may go back and stick with armel for now - unless I compile my own qt5 _again_ for hardfp. And I feel that would involve getting dirty with some some qt config options. Although you can pass in Bsquask as a distro option, might be worth investigating... must add to list of things to do.

-Coley.

so jealous...i cant even order one yet!

Do you order from RS/Farnell in the states too? They have opened up the order pages again, you can even order more than one pp.
They have some neat cases too - but shocking lead times!

-Coley.

Did you setup for armel or armhf?  I might be able to provide the pluto armel libs for now if you have any troubles.  I am trying to setup an armhf enironment for raspian now.

J.

armel for now - AFAIR I need 64bit host for bcom toolchain cross to hfp. I didn't dig too far.
I did download the new rasbian image today so might take that for a whirl.

-Coley.

Code:

coley@VirtualBoxK1204:~/src/rpi_scratch/omxplayer$ file omxplayer.bin
omxplayer.bin: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0xa7418aeb2fb380510775c2adc54b2c0fef1c0f9e, stripped

Yay! got my sb2 environment going.
need to go building some pluto libs now ...

-Coley.

We can continue this discussion in another thread if you wish, little OT for this one.
J.

and new topic started here - http://forum.linuxmce.org/index.php/topic,12689.0.html

Just make sure the GPU/RAM memory split is set to something more sensible...

"something more sensible" - what do you mean? what values do you suggest?
If qOrbiter is to run on this too it needs most RAM allocated to the GPU.

-Coley.

@phenigma can you please share info on how you managed to compile and install lmce on Raspberry Pi ?

see his post here - http://forum.linuxmce.org/index.php/topic,12606.msg90675.html#msg90675

-Coley.

following on from this post in qOrbiter on Pi discussion:
http://forum.linuxmce.org/index.php/topic,12606.msg90675.html#msg90675
lets keep discussions on new player device here.

Details on player http://elinux.org/Omxplayer

-Coley.

Whomever is ready to write an omxplayer device, let me know, and I will be available to provide a chalk talk in IRC.

-Thom

Thanks Thom, would be interested, my TZ is UTC+1hr if you are trying to line up more than me to listen.
-Coley.

make clean and re-run qmake between builds
qt 4.8.1 - for_desktop gcc(x86) qOrbiter compiled successfully.
qt 5.0 - for_desktop gcc(ARM) bcm cross-compiler, qOrbiter compiled successfully.

This done again with older qtcreator, so as I thought IDE agnostic.
stumped as to why its failing for you

-Coley.

Don't know how regex will get you out of that corner, ">=" should cover anything less than 5.0.0.
Its why the bloody macro is failing is the brain tease.

-Coley.

Yep, that's going to work okay. That's the end result of the macro.
That check was what I was using before discovering the other macro in Qt sources.
Magic numbers never good - have been steered away from them from an early age

-Coley.

make clean and re-run qmake between builds
qt 4.8.1 - for_desktop gcc(x86) qOrbiter compiled successfully.
qt 5.0 - for_desktop gcc(ARM) bcm cross-compiler, qOrbiter compiled successfully.

any more info you need from my env?

-Coley.

nope - no magic about it.
It worked in some instances and not in others, but once I included the <QtGlobal> header where the macro wasn't behaving all worked fine.
I'll try compilation on diff versions of qtcreator, but don't see how that will impact this macro.

-Coley.