qmake for cross-compile

[skypuppy]

Do you guys have a link (or method) for getting/installing a qmake on Debian Jessie AMD64 to cross-compile for an armv7hf machine (Beaglebone Black and Raspberry Pi2?) Especially the RPi2?

This Qt is driving me <censored> nuts! This vendor doesn't have x library ready. That vendor doesn't know what Qt is. That other vendor has heard of Qt... Debian is getting better but still no qmake cross-compile. qmake for local machine works just fine. Gaaak.

If it makes a difference, the Linux Jessie desktop AMD64 has Qt 5.5.1 and the RPi2 has Qt 5.3.2 with qmake version 3.0.

Thanks,
Skypuppy

As you can tell, EXTREME noob!

[anda_skoa]

Debian for PC can't easily ship a cross-compile package of Qt because that depends so much on the target toolchain, target system layout, etc.

Depending on what operating system you have on the device, the easiest way might be to check if there is a native build environment for the target.

Then you could simply develop on the PC and build on the device only if you need to test device specific things.

Cheers,
_

[skypuppy]

Yeah, that was my first attempt. Unfortunately, Qt for the RPi2 is not ready for prime time. It gives an error message during startup about DRI2, can't register or authenticate or something. (from memory)

So, I dropped back to develop and write code on the desktop Linux box. Everything on the Linux box works just fine if that is the only platform being used. However, the sensors use I2C and the PC doesn't have that, so enter the RPi2 requirement. Following Derek Molloy's books and videos, tried to set it up so that code is written on the desktop with qt UI and windows on the desktop but sensor readings on the RPi2 feeding the desktop via WiFi or Bluetooth, and that is where things go haywire. Qtcreator on the desktop wants a qmake for the armv7hf and there is NONE to be found. <sigh> I'm getting really SICK of stuff not being available, but I soldier on and try to make things work. No good. Molloy's directions give a work-around but it involves Qt4 on the RPi2 and I already have pulled eye teeth to get Qt5 on the RPi2.
I REALLY want to learn and use Qt for both environments, Rpi2 and desktop AMD64, because I want source code line-by-line debugging with variables values. I need to see where my algorithm breaks down while code is executing and I like the *promise* of Qt. So, I'm not married to Qt but it sure looks attractive at this point. It gets uglier and uglier every time I try to do something though, due to THIS not being ready or THAT not being ready.