Thx, that's worked - I'll go without the gdb/3 stuff

@JoeCFD Where is it located in the relative /QT folder? /... like 5.12.5 , dist, Docs, Examples

@JonB Thank you for the answer this might be helpful i'm gonna try this out

The Qt version was indeed not properly installed. qmake expects a specific directory for target libraries $ ~/Qt6/6.2.4/qnx/bin/qmake -v QMake version 3.1 Using Qt version 6.2.4 in /home/werner/qnx710/target/qnx7/home/werner/Qt6/6.2.4/qnx/lib So to fix QT Creator, I simply had to create a symbolic link: $ cd ~/qnx710/target/qnx7 $ mkdir -p home/werner $ ln -s ~/Qt6 .

Sadly, No luck. I'm getting: [image: c594eac5-f9fb-42db-8dd2-0a89387898bc.png] Maybe there are other factors that I didn't consider. Though it's better than how it was before, because before it didn't even show this message. It just crushed. EDIT: When I copied the complier and Qt version from the computer where it works, It successfully complied and runs. So the issue defiantly stems from incorrect versions of either the complier or qt. But the Qt version is 4.7.4 which is what I currently have, so I guess the problem is the complier. Is it possible to know what complier version I'm using just from the exe?

You're right. I installed Debian 11 OS (which offers 32 bit version of Qt5.15.2) on different machine (1TB HDD etc). Thanks for the answers..

https://download.qt.io/official_releases/qt/

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.

@TomNow99 I guess you may want to take a look at this library: lwext4 Although "The main goal of the lwext4 project is to provide ext2/3/4 filesystem for microcontrollers" documentation also mentions compilation for Windows. And then take a look at project ext4-browser which relies on that library to provide "a file-archiver like utility which can create, read and modify ext2/3/4 disks and disk images on Windows and Mac OS systems." although the GUI is written using wxWidgets framework. So getting back to my suggestion, I guess you might combine lwext4 library and the ext2read GUI to achieve your goal...

Thank you very much

@sergitab94 Sorry for this reply I know this is an old post, but I followed your steps one by one but still my build fails. Anyway opennssl static build with Qt really frustrated me... C:\Qt\Static5113OpenSSL\src\qt-everywhere-src-5.11.3\qtbase\bin\qmake.exe -install qinstall C:\Qt\Static5113OpenSSL\src\qt-everywhere-src-5.11.3\qtbase\mkspecs\winrt-x86-msvc2015 C:\Qt\Static5113OpenSSL\StaticOpenSSL64\mkspecs\winrt-x86-msvc2015 C:\Qt\Static5113OpenSSL\src\qt-everywhere-src-5.11.3\qtbase\bin\qmake.exe -install qinstall C:\Qt\Static5113OpenSSL\src\qt-everywhere-src-5.11.3\qtbase\mkspecs\winrt-x86-msvc2017 C:\Qt\Static5113OpenSSL\StaticOpenSSL64\mkspecs\winrt-x86-msvc2017 mingw32-make[1]: Target 'install' not remade because of errors. mingw32-make[1]: Leaving directory 'C:/Qt/Static5113OpenSSL/src/qt-everywhere-src-5.11.3/qtbase' mingw32-make: *** [Makefile:92: module-qtbase-install_subtargets] Error 2 mingw32-make: Target 'install' not remade because of errors.

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 :)

Hi Do you really need that many kits installed ?? Desktop QT 5.6.2 MinGW 32bit -> can make normal win32 apps in 32 bit. Run on win 10 64 bit too ( as 32 bit) Desktop QT 5.6.2 MSVC2013 32bit. -> 32 bit, you must install compiler yourself. VS 2013 ONLY ( runs on 64 bit too) Desktop QT 5.6.2 MSVC2013 64bit -> 64 bit, you must install compiler yourself. VS 2013 ONLY ( runs ONLY 64 bit ) Desktop QT 5.6.2 MSVC2015 32bit -> 32 bit, you must install compiler yourself. VS 2015/17 ONLY ( runs on 64 bit too) Desktop QT 5.6.2 MSVC2015 64bit -> 64 bit, you must install compiler yourself. VS 2015/17 ONLY ( runs ONLY on 64 bit) Desktop QT 5.6.2 for Universal Windows Patform 32bit Not a Desktop app. WinRT only app Desktop QT 5.6.2 for Universal Windows Patform 64bit Not a Desktop app. WinRT only app Sounds to me you can just use mingw. for both 32/64 bit unless you want app to be 64 bit ?

"misc_common.h" is located in the "misc_common" folder, no ? That's the one you have to add to your project.

@ThirdStrand said in Force system QT libraries to use openssl libraries shipped with the application: @JKSH One would do this to ensure that the libraries used are the proper libraries which are expected in the program. In much the same way as we deploy the appropriate versions of Qt libraries, why not use a KNOWN library when deploying the libssl and libcrypto libraries? If you want to use known libraries in your app without the possibility of user interference you should probably use static libraries and not dynamic. Because even if the other libraries are not in the system path there is always at least one user who might want to exchange your library with another one - perhaps optimized for his computer ;) Had this a couple of times on windows with DLLs and a lot with java apps where users just replaced „outdated“ libraries. This has become the bane of my existence, and I am here in search of WHY it will work when it is in QtCreator and NOT work when deployed with the EXACT same loaded library files. I didn‘t see your used OS but I could imagine that Qt Creator uses LD_PRELOAD mechanism to ensure that the specific libs are loaded first. This at least should work an Linux, I don‘t know any trick for that on windows. AFAIK macOS offers a similar mechanism to Linux. By way of venting, this old question gets some new life. I have seen many "answers" which usually consist of "The user should install....", which anyone who has ever actually deployed retail software knows is an absolute NIGHTMARE. Witness ProtonVPN! This commercial application is deployed with a specific (v1.1.1j) set of OpenSSL libraries. Why? Because it is developed with that version and is tested with that version. Why opt to allow the end user to change the libraries and break your application at will? That's just self-defeating. Still this doesn‘t prevent the user from changing the libs themselves. And given the fact that the build environment doesn‘t often change it might very well be that they will be shipping an „outdated“ version - because the app was developed with it - and tested. When I worked on Air Traffic Control Software we almost never updated our libraries - because they were „tested“. As I said earlier: If you want to prevent user modification use static linking. This way the size of your deployed app will also shrink. But be sure to check possible licensing restrictions.

Still has errors !!

@AliReza-Beytari No, but you can bundle your application with other stuff (e.g. gcc, qmake et. al.) in one installer.

Hi, Did you compile your application with your desktop Qt and then copied it over the RPi2 ?