@JonB Thanks Jon. I will look into those suggestions. I think at this point though, the best thing for me to try, rather than thrashing around with my current project, would be for me to start a new project focused on just replicating this specific issue. I'll try and pare this down to minimal required code, just enough to reproduce the problem This will make findings clearer and easier to communicate to others. If I get to a point where I have something useful to share, I'll do so. Thank you again..Mark
The reason linuxdeployqt does not support your latest ubuntu is not, that its not up to date, but it is on purpose.
If you build your appimage on a new linux and then want to run it on an older installation it might not work there since e.g. the libc version on the older system does not support new features that have been added. And running on any system is the whole point of the appimage.
@J-Hilk Thanks for the reply. This adds a bit of complexity to my WIX installer since I don't want to list all 700+ files individually. Do you know if there is anyway to deploy these files in a folder other than where the executable is located? I would like to dump all of the QT dependencies in one folder (which can have subfolders) but I need to be able to "blow away" all of the Qt related dependencies by deleting one directory while being confident that I didn't delete anything but Qt dependencies.
After the advice from @SGaist I started to experiment a bit with settings of the build steps: problem disappeared after I did these three steps one by one (after each I checked if the problem is gone - it disappeared after the last step:
turning off QML debugging and profiling switch (default was "leave default", effective call showed CONFIG+=qml_debug now it is CONFIG-=)
turning off QtQuick compiler (default was "leave default, effective call showed CONFIG+=qtquickcompiler now it is CONFIG-=)
deleting shadow build folders (I do it routinely once a week or so anyway).
Now the problem is gone, I am marking the topic as "solved".
This virtual maschine need to support Bluetooth Low Energy.
If you have an USB bluetooth dongle/adapter, than you can most likely inject this dongle into the virtual machine and use it there. Note that even bluetooth adapters built into your laptop may be an USB devices and could work that way.
@hskoglund It worked!
I read the docs in OpenSSL provided with Qt (file INSTALL, src folder, section "Notes on shared libraries), where it states that:
On Windows build with MSVC or using MingW, shared libraries are named
libcrypto-1_1.dll and libssl-1_1.dll for 32-bit Windows, libcrypto-1_1-x64.dll
and libssl-1_1-x64.dll for 64-bit x86_64 Windows, and libcrypto-1_1-ia64.dll
and libssl-1_1-ia64.dll for IA64 Windows. With MSVC, the import libraries
are named libcrypto.lib and libssl.lib, while with MingW, they are named
libcrypto.dll.a and libssl.dll.a.
Of course, files provided with Qt are build with MSVC which is just odd considering that I installed mingw only. Anyway, instead of going with installation of provided msvc packages (they are in the Qt folder tree, ms redist 2010) I downloaded OpenSLL 1.1.1d (or 184.108.40.206 as the dll description states) precompiled with mingw from official mirror.
Works like a charm.
What mislead me was that Qt started to provide OpenSSL binaries as toolkit whereas previously I always downloaded myself. Dumb me thought that toolkit would be oriented towards the build chain / compatible.
Ok. I found the cause why I was not getting anything QML related from the tool. My widget is not in the exe file but in a DLL so I had to specify the dll instead.
But the list of files the tool is getting is huge compared with the one I got by doing the process "manually" and includes most of the .qml files. So my doubt is, do we need to deploy all this files with my application? is not enough with the dlls???
Sorry, it took me a bit of time to make the tests:
A simple "Hello world" project runs correctly in Qt Creator?
When using the external lib, the program crashes. I suspect an incompatibility of this old lib with Windows 10.
I need to further investigated this issue...