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.
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.