Installation and Deployment

Hi and welcome to devnet, I would try to get a more recent version of your cross-compiler. Gcc 4.8.3 is a bit outdated.

@dgrz1985 I don't use Qt under Windows so I can't say what is/is not necessary. By the sound of it, the easiest would be to run it through Qt Creator setting the Run Environment to have that variable set, if you say it does not work from command line. Anyway, your output is somewhat curtailed, there are some references in there to why it cannot load the qwindows.dll. A "specified procedure cannot be found" might indicate some version mismatch between what you have and what is expected, I don't know. You might glean more information if you run a Dependency Viewer on qwindows.dll. That's all I know. You might be able to Google for why qwindows.dll is not working for you. Or they may be other people here using Windows who can answer.

Just for testing, create a new QML ui file - not just QML file. Give it a name TestForm.ui.qml. I think the QML designer accepts only ui files while the QML files (main.qml in your case) are intended for text editing only.

Hi and welcome to devnet, Did you check that you have all required dependencies available ? Take a look at the configure test logs to exactly what failed.

Created a bug report.

@StrandedFox said in PHP script exec() on QT App - errors with Could not load the Qt platform plugin "xcb" in "" even though it was found.: I somehow need to get rid of the app from starting its GUI modules...? At some extent, you may want to have the same only Qt app running as GUI or console given a CLI argument at startup, see this article. However, that approach won't free you from changing your current Qt app to decouple some GUI parts from the PNG generation parts.

i had the same problem in visual studio 2019 community with Qt 6.0.0 after, searching every forum etc.. and trying the install of visual studio 2015 build tools x64 and visual studio redistrubutable 2015 x64 which didn't solve the problem too i tried updating windows sdk version from 10.0.18362.0 to 10.0.19041.0 which i though i should not at first cause it may work with the 6.0.1 qt version and 6.0.0 and then problem was SOLVED. i'm currently using visual studio community 4.8.03761 if that might help others so just check that you have window sdk version 10 updated ( EVEN IF YOU THINK YOU DONT EVEN NEED IT) and that your compiler is well chosen. ( i had mvsc2019_64 and work with LLVM etc.. version in build settings) hopefully this helps you guys.

@akhi95 I figured out QProcess::execute() might be helpful. But since it's a CPP function, not sure how to use it in my component script (JS).

Hi and welcome to devnet, This Stack Overflow thread might be a good start. Hope it helps

@oblivioncth I can confirm that this was fixed in 6.0.1

Thank you very much for that suggestion. It looks like resolving the problem truly was as easy as uninstalling Qt completely and then reinstalling it again. During the installation process, I selected the default option instead of custom installation and everything went fine. Additionally, the problem with Kits was also resolved.

Because it's the toolchain in the board SDK, I have compiled Qt5.12.2 successfully with gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu.Thanks. Besides, it still makes another error if I use gcc-linaro-7.5.0 to compile Qt5.15.2 . I will check it later.

@AnneRanch Hi If you do try CloneZilla, please promise me to triple check what is the source and what is the destination as it will copy the empty disk to the full one, make one cry in the keyboard.

@AnneRanch said in How to configure "git" - Linux ?: WHY IDE cannot intelligently point out to the user that "git" is missing ? Feel free to provide a patch for it...

@Doug-Hutcheson said in Newbie question: Warning Device type is not supported by Qt version: success! if your issue is solved, please don't forget to mark your post as such!

@JKSH I will wait until the issues with the installer are resolved.

Works now. Closing.

Build log: https://pastebin.com/2y6AhZ8N All in all it probably comes down to Qt awful buildsystem which pulls in wrong header files . It builds the complete qt5 package fine but fails to build qtdeclarative separately with exakt the same build options for qtbase and with the same qmake & mkspecs config. I guess cross compiling Qt5 boils down to never touch a running system or you end up with a trainwreck and clusterf$%&