Installation and Deployment

I rewrote the code again and now it works somehow... Thanks anyway to everyone

@jsulm Thank you

CMake was installed by the Qt unified installer for MacOS because it is now required. It does NOT update the system path when it installs (apparently). I have added the export to the .zshrc file I created in my login account. CMake functions just fine from inside QtCreator, so it manages it's path internally. In the case of MacOS, the QtMqtt module is built properly, it only leaves an artifact of an incorrect path in a few .h files. In the case of iOS however, it refuses to use the same project to build it, citing the "set to FALSE" error.

@Christian-Ehrlicher many thanks just using undef to avoid this issue

Hi and thanks for the information, Since windeployqt should handle that for you, there might be a bug it the list of dependencies to deploy for that module in it. You should check the bug report system to see if there's already something about that.

@JonBI don't know if that's the problem, but I downloaded the QWebView module using the maintenance tool but still QtCreator does not recognize it as an existing module.

@NiVa99 said in Qt5.15.2 amd64 Build from src - Missing symbol export "_cdecl QUnhandledException": think -developer-build option is the main diff. I No, see the header of qexception.h - you disable a feature and Qt just does what you asked for.

UPDATE: The offending header files in the automatically installed "include" folders for the iOS version of QtMqtt are missing part of the path. Example (but there are about 8-10 files that have this error): Contents of qmqttclient.h (/Users/login_name/Qt/6.2.3/ios/include/QtMqtt/qmqttclient.h) #include "../../../qtmqtt/src/mqtt/qmqttclient.h" Should actually be: #include "../../../Src/qtmqtt/src/mqtt/qmqttclient.h" EDIT: This has been reported to the bug list. EDIT: This allowed a qmake project which uses QtMqtt to function, however, the cmake version of that project is still broken citing that CMake sets a "FOUND" variable to "false", which kills the build, even though there doesn't seem to be a reason to set it to "false". Also reported to bug list.

@Christian-Ehrlicher Thanks.

@JonB okay thank you very much :)

Then you could install the dependencies of the Ubuntu Qt dev packages. This might help. Otherwise, use the Qt development packages from Ubuntu directly.

I just found out what I was doing wrong. I had set the wrong bit for the compiler. It was set to 32bit instead of 64bit. Thanks for the help, especially the news about QWebKit being depricated. I'll mark it as solved.

My guess is that qtbase-gui package triggered the installation of the dependencies you were needing.

Qt Automotive Suite is discontinued. Automotive-specific components are now under the Device Creation Enterprise Licence. see https://www.qt.io/product/features#js-7-17 for further information about what is available.

You do not link against a plugin - it's loaded dynamically during runtime.

@micha_eleric said in fatal error: private/qringbuffer_p.h: No such file or directory: Because it was the next on the list So what? You already installed libqt5serialport5-dev, there is no need to build it by yourself unless you have some real need to do so. So, simply use QtSerialPort you already installed and do not build it by yourself...

@Cyrille-de-Brebisson said in QT Multimedia not available? (QT 6.2.2): Does anyone have any idea as to why this is the case and what I need to do to enable QT multimedia on my build server? Because Qt 6.2.2 is "old" now (replaced by Qt 6.2.3), your installer only shows you the add-ons that you have already installed. To add more add-ons to Qt 6.2.2, tick the "Archive" checkbox on the right and click "Filter".

So basically you will have a dialog to query some data from your user. Then the usual way is to show the dialog in a blocking manner and then grab the data from it. Check QDialog and QInputDialog. You should also write down how your application shall work. Sharing data between widgets does not mean using global state variable but designing data sharing properly.

I've executed the command "export DYLD_PRINT_LIBRARIES=1" and as I can see, if I open the executable from terminal, it loads file from app bundle but if I use the "open" command to run the bundle, it loads file from "/System/Library", is this behaviors correct? Edit: Ok... After some tests with an empty app I found where the problem is. I got a class that make use a new thread for each object to execute a method, setting this thread as "static" have solved the problem. Could it be a problem related to an high amount of thread that are created? How can I solve this?