My reply is going to lead down a bit of a tangent...

If someone knows how to give you a more direct answer, then I would recommend you ignore mine!

I don't have a direct answer. But I have a long-standing curiosity about cross-platform development, so I took a moment to do a brief investigation.

When I need a point of reference for using Qt in a "massively cross platform" way, my "cheatsheet" that I often turn to is the Subsurface divelog project.

They are cross-compiling their Qt app on Linux to target windows. You can see their CI job config here. I know that's not the same as cross-compiling Qt itself.

However, I noticed (at the top of one of their scripts) that they call out how they are leveraging: https://github.com/mxe/mxe

And when I read the MXE page, I see they say: "MXE (M cross environment) is a GNU Makefile that compiles a cross compiler and cross compiles many free libraries such as SDL and Qt. "

Again, this is a very indirect stab and a mostly non-answer.

But if you end up in dead ends with anything you try, maybe MXE would give you a path forward.

@Dariusz I'm experiencing this same issue on Mac M2 with Qt 6.4.2, however the same code build on Mac Intel works fine and I don't have that ugly output.

You should check the configure logs to see exactly what is failing.

You should also do an out of source build so you can more easily nuke and restart when you change something or you have an error and need to restart.

please help me guys i need it ):

Hi,

If you copy the files over your target respecting the same folders as your desktop machine, then you won't have anything special to do.

Then why not install the suggested module ?

Well, I consider to remove/change the code in my qt app to not depend on qtwebengine... It just displays some wheather maps (images) from an online source. I think I can realize that by fetching those images somehow from that online source and display them on an QLabel or so. I think qtwebengine is quite an overkill for that :)

@RyuShai As I said on in your sysroot which you use to build for your target device. It doesn't help to install it on your host machine as you're building for another machine with different architecture (ARM). Your host machine is x86_64, right? If you install libs there they are for x86_64 as well - you cannot use them on ARM. Usually if you cross compile for other architectures you have a sysroot which contains all needed header files and libraries.

Ok, i found the solution.
I had to recompile qmake with pkg-config enabled.

Hi,

Where did you get this library from in the first place ?

Hi! I am trying to compile Qt 5.x for Windows Mobile 6.5, and getting a lot of errors about wcsftime and other functions told above. How did you solve that problems?

Hi,

I have been starting development using QT a few weeks ago and encountered a similar problem. Everything was fine, compiling the apps and deploying to the PI using QT Creator without issues. But as soon as I started the app (or wanted to debug) the app died with a Segfault.

After some hours, I noticed that libts on Jessie has been quite old. I re-installed Jessie-Lite and compiled libts on my own, directly from the GitHub repository here: lbts GitHub Repo .

Afterwards I simply followed the tutorial to cross-compile QT5 like documented in this tutorial: RaspberryPi2EGLFS

Basically I followed each step within the tutorial and the only thing I did not do, was to install any libts related packages (just check the apt-get install commands in the tutorial and don't install the libts related packages).

I know, the thread is quite old, but maybe someone will look it up.

@SGaist thank you for the fast reply. now I started to see the difference.

I am working on Nitrogen6 Max Board using Ubuntu Trusty for i.MX6 boards img (light weight desktop environment).
I have downloaded img file from timesys for direct use http://boundarydevices.com/trusty-ubuntu-mx6/.