Hi and welcome to the forums Yes it should run on most other windows 10 64 bit. Maybe even win 7. But there is no guarantee as such with brand new mega patches. A license would give you many benefits but it's not better to deploy as such.

I second everything @mrjj has said so far. It seems that the absence of a window manager might be the key issue here. However, in case other people end up on this page due to a matching error phrase, I will share a workaround that I encountered for OpenGL/QSurfaceFormat errors in the past. A couple years ago I was working on a Qt/QML project and I was using Xephyr during testing to create the X display. A subset of team members experienced an OpenGL-related issue. It seemed to depend on each person's graphics hardware. We ended up with a technical memo that said something like "when launching the app for testing, if you see any error about OpenGL, GLX, EGL, QSurface, or similar, the workaround is to install VirtualGL from virtualgl.org and insert vglrun into the command, like so:" DISPLAY=:12 vglrun -- $PROJECT_HOME/build/projectname/gui/test_app &

I somehow workaround it. On the RaspberryPi I created a bash script in /usr/bin: /usr/bin/x5 #!/bin/bash xhost +local: sudo /home/pi/adas0002 --platform xcb I made it executable and then on my Desktop-Pc in Qt-Creator I have "/usr/bin/x5" in "Alternate executable on device". Now my application starts with root even without invoking any terminal. I know this is very bad in security point of view but I dont care on my little offline Raspi...

Hi, I am able to open the application by double click. I made change in Icon and Exec path. Exec=APP_PACKAGE_PATH/SquidStat.sh Icon=APP_PACKAGE_PATH/Squidstat.png

@stecco ok. Ho impostato clang come compilatore c++

@SGaist Ahh, okay I see it. Clone Build Config -> Delete Build Steps -> add Custom Process Step Thanks for the inspiration!

Hi, You have to build your application on the oldest Linux distribution you have to support.

@BINALECTRUM said in Android build and deploy. 64bit, Clang, new app store developer console rules [2018 & 2019]: Is Qt going more in embedded/car side and just slowly drops Android/mobile platform? In Roadmap 2018 there is nothing new about mobile platform. i heavily doubt that. I guess the reason is more because Qt runs more or less stable on Android. There are no bigger features which need to be implemented, mostly bug fixing. What is your move Qt team on new app store rules in developer console: minimal platform-26 in August 2018 and 64-bit apk in 2019? Some new changes in build and deploy area? i asked this at the beginning of the year, but unfortunately haven't received an answer.

Latest drivers ?

@torpeanders I always use just one resource file per project, and although not completely sure, it looks like having RESOURCES += ... is intended for just one resource file. I'm not sure if you need two resource files, I'd ask what is your use case for that, please remember that you can have subfolders to split just in case; i.e. I usually have a subfolder images for the icons and a subfolder translations and then it's a question of using the proper path QIcon(":/images/cut.png") So if even this trick cannot avoid you having two resource files, please have a look at the documentation as it explains how to create/deal with external resource files (it'll be your 2nd one).

I haven't played with that system recently but AFAIR, you should be able to build the sysroot for your system on your desktop machine. Then you could use scp to copy the bits you need over to your device. Doesn't your system provide a possibility to start from another device like a SD card or even a nfs ?

Oh ok, thanks to both of you! I think I am just going to make videos on it and show that without actually sending it. Thanks though!

Then there might be something I'm missing about your current setup. In any case, take a look at this excellent blog article about that subject. That should give you the clues needed to solve your situation.

@lindevs said: libqxcb.so libqxcb.so depends on these .so files: libQt5XcbQpa.so.5 libQt5DBus.so.5 So in my case project structure looks: myapp myapp.sh platforms\libqxcb.so libQt5Core.so.5 libQt5Gui.so.5 libQt5Widgets.so.5 libicudata.so.56 libicui18n.so.56 libicuuc.so.56 libQt5XcbQpa.so.5 libQt5DBus.so.5

If you mean that macdeployqt still gives you the same error, then that's normal. We run it before modifying these libraries. If you want macdeployqt to not scream at these libraries, you can change the original files and put the whole path to them with -change.

thank you @yuvaram and @jsulm i will try your solution.

Thank you very much @SGaist and @raven-worx for helping me out. I fixed this issue by using runtime libraries from this project: https://sourceforge.net/projects/postgresql-mingw-w64/

It is: Qualcomm Snapdragon 805 You should either create another virtual device with x86 CPU or use Qt for Android ARM.

Thanks for the reply ,will certainly try the QtSpalshScreen thing when I get on the machine with the proper environment.I have noticed that when you start a new android project with Qt creator the project just runs fine. It is only when I import an external project in my instance of Qt Creator that the problem occurs.I decided to just learn a few basics on android native development ,deal with problems in the native environment ,and hopefuly it will be easier to deal with these on the Qt side of things.

The problem solved and I updated the wiki page to include the solution: https://wiki.qt.io/Build_Qt_5_MySQL_Plugin_for_Android#Using_mariadbclient_.28Option_2.29

@SGaist said: You are missing the openssl libraries It's not related to my issue because it points to "libqsqlmysql.so" which is not needed in my application (the needed one is libqsqlmysql.so) Any way, I fixed the problem (thanks to Hamish Moffatt from Qt mailing list) by removing "libqsqlmysql.so" (the old plugin original file shipped by Qt Installer) outside sqldrivers folder

@timday said in [Solved] What's the equivalent of macdeployqt's -qmldir=... option for iOS builds?: so I created an imports.qml in the subdirectory referencing the imports I wanted... and all seems well again 100 upvotes if I had them to give. 5 years later and this imports.qml trick still solved my iOS issue. thank you!

Good ! Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

@JKSH This img of qt version: http://i62.tinypic.com/dhaiqb.png I'm use the qt creator and qt version 5.4.2 downloaded of qt.io

Maybe this guide will help on Windows CE: http://wiki.qt.io/Deploy_an_Application_on_Windows What error message do you get when you try to start the application?

@SGaist ok. thanks

And that's the information I missed. I found that qgif should be in 'plugins' folder, but it seems to work in qt4 only. qfgif.dll has to be stored in 'imageformats' subfolder. Thanks a lot!