Installation and Deployment

@JoeCFD windown and qt-unified-windows-x64-4.6.0-online

@Noobery Did you take the time to Google qt download mirrors? Or search this forum for mirror?

@dev_liya Sir, my error is about similar to you but it didn't work for me. Error: The kit supports "", but the device uses "arm64-v8a, armeabi-v7a, armeabi".

@Christian-Ehrlicher I need to create a .txt file for the output of auto tests for documentation I am trying to put together. Thanks!

@jsulm Oh great, that actually has worked. Thank you so much :)

@Christian-Ehrlicher Yup.. it worked when i upgraded my Qt version. Thanks a lot. Just for education purposes, can i ask lets say if i am still using qt 5.8.0 and i wish to remove this message. Is there a way to do that? I believe this message is caused by this qt sqldriver file called qsql_psql.cpp. So I tried to remove the code that prompts this message in qsql_psql.cpp file and it didnt work when i run my application.

@acetone said in QSslSocket failure from Online Installer version (Ubuntu): Solved by manual linking with openssl1 and ssl1. Download old openssl sources: wget https://www.openssl.org/source/openssl-1.1.1q.tar.gz Compile: tar -xf openssl-1.1.1q.tar.gz cd openssl-1.1.1q ./config make Add to project: # .pro file: LIBS += -L/path/to/openssl-1.1.1q -lcrypto -L/path/to/openssl-1.1.1q -lssl This fixed the issue for me on Ubuntu 22.04 / Qt 5.15 but only when starting my program from Qt Creator, running it from the console shows the same ssl error...

@devQt93 this post doesnt have any help for a while. I just want to push it on top and take a look for any help.

I suspect that the libraries are installed along another module but I currently don't know which one.

@SGaist said in Kali Linux - Could not load the Qt platform plugin, (I need your help).: Hi and welcome to devnet, By default, for security purposes, root does not have access to the window server. Do you really need to run that application as root ? Thank you very much for answering. I will do this.

Hi, If memory serves well it's x86_64h that should be used.

I am going to to answer this my self it turns out that the problem was due to the directory /usr/local which on my system is empty. Deleting the directory made the problem go away. So on to the next issue ... Thanks anyway.