Installation and Deployment

@kkoehne said in Could NOT find Qt6WebSockets (missing: Qt6WebSockets_DIR): This was raised before: https://forum.qt.io/topic/136147/failed-to-build-qt-6-3-0-from-source-on-ubuntu-22-04/3 . https://bugs.launchpad.net/ubuntu/+source/draco/+bug/1958432 might be the upstream bug for this.

soved in simple manner: configure -release work fine!

@Prashant0203 Can you please explain better what the problem is? What is "Tool"? What is "property"? What "UI"?

@jiapei100 said in OpenSSL3 support for Qt5.15.5 ?: When will Qt be compatible with OpenSSL3 ? It would be much quicker for you if you had just Googled qt openssl 3 ! https://forum.qt.io/topic/136960/does-qt-support-openssl-3-x

@J-Hilk I did read that part and implemented it, but the issues were still there. It was more of a "I was using the class like my left foot" problem. I got new errors but none warranting a continuation of that thread. Still, thank you for your time and patience !

Ok, I added some debug-commands and a "CONFIG += console" to the .pro-file. With this, I found out that the app is actually starting, but crashes at some point. It seems like the problem is not my app, but the communication with a connected device (I was given the code for the communication from another project, so I just assumed it would work...). The only difference is that the other project is compiled with MingGW32 instead of MinGW64, so I'm gonna try this too, even if it is running on a 64 bit computer, this should work, right? Anyway, thank you very much for your time and quick help! I think this is really the most helpful forum I know!

Thanks a lot

@nadimnadaf said in qt installation error: Like that number of errors will show. The screenshot shows that you are trying to install Qt 6.3.1. This cannot work on Ubuntu 18.04, as @hskoglund said. Install Qt 5.15 instead. If you see errors about sdktool when you try to install Qt 5.15, you can click "Ignore".

@OlegD said in Qt and Tesseract Linkage: Same error INCLUDEPATH +=D:\MinGW\msys\1.0\src\tesseract-ocr\include LIBS +=-D:\MinGW\msys\1.0\src\tesseract-ocr\include Remove that LIBS line, it's just plain wrong.

@nadimnadaf said in (Workaround Available) Error during installation of Qt 5.8.0 on Windows 10 x64 using offline installer: I have problem with installing a qt Hi, You should open a thread into which you explain exactly what is your issue, what exactly you are trying to install, on which OS, etc.

@kkoehne cd C:\Work\Qt\5.15.2\Src configure.bat -platform win32-msvc -release -mp -opensource -confirm-license -static -static-runtime -optimize-size -prefix "C:\Work\Qt\5.15.2\msvc2019_64_static_size" return: Qt is now configured for building. Just run 'nmake'. Once everything is built, you must run 'nmake install'. Qt will be installed into 'C:\Work\Qt\5.15.2\msvc2019_64_static_size'. Prior to reconfiguration, make sure you remove any leftovers from the previous build. I went on :nmake return: 'cmd' is not recognized as an internal or external command, operable program or batch file. NMAKE : fata1 error U1077:return code "0x2" NMAKE : fata1 error U1077:"cd":return code "0x2"

@kkoehne said in Download QT5: @sierdzio , chances are you're using some sort of ad-blocker? There seems to be a particular issue with the built-in ad-blocker for the Vivaldi browser, see e.g. https://forum.vivaldi.net/topic/70770/miss-elements-in-qt-download-page Spot on! I'm using Vivaldi :-) Thanks for sharing.

@Mefil said in QT deployment - binary and QT dlls to different folders: Hi. I want to position my binary file in folder like out/forms/ and qt dll in folder like out/QT. I try this code: int main(int argc, char *argv[]) { QStringList s; s.append("E:\\develop\\repositories\\rep_sw_new\\trunk\\sw\\QT\\out\\QT\\platforms"); s.append("E:\\develop\\repositories\\rep_sw_new\\trunk\\sw\\QT\\out\\QT"); QCoreApplication::setLibraryPaths(s); QApplication a(argc, argv); Widget w(argc, argv); w.show(); return a.exec(); } It helps with qwindows.dll issue but did not help with QT dlls. I didn't want upgrade PATH or move dlls to system32, because it will crush other programs on PC. PS/ I want to have a lot of binaries in different folders wich used one dir with QT dlls/ PSS/ Sry for my eng/

I've been playing with this today, and I just discovered that my commands are building a 64-bit Qt library, which 1) isn't what I intended, and 2) might be part of the problem. I've looked at the options for the configure command, and I don't see a way to specify that I want a 32-bit library. Can someone advise me on what to do here? EDIT: I even added these entries in the qt.pro file to: CONFIG -= x86_64 CONFIG += x86 Somehow, my build still insists on creating a a Qt library with a profile x66-windows-msys-pe-64bit. WHAT am I doing wrong? Thanks... EDIT 2: this question is really a different subject, so I'm going to ask it in a different thread. Leaving this one open for now until I get to the bottom of the missing libraries.

@thaidy said in QT Deploy QPSQL Plugin: @hskoglund said in QT Deploy QPSQL Plugin: what happens if you move the declaration into for example your MainWindow.h class: QSqlDatabase DB; DB = QSqlDatabase::addDatabase("QPSQL"): IT WAS THAT, THANK YOU VERY MUCH!! Glad this has solved problem, certainly better than some static variable. However, this is still not right/advised. Per https://doc.qt.io/qt-5/qsqldatabase.html#details, red box warning: Warning: It is highly recommended that you do not keep a copy of the QSqlDatabase around as a member of a class, as this will prevent the instance from being correctly cleaned up on shutdown. If you need to access an existing QSqlDatabase, it should be accessed with database(). If you chose to have a QSqlDatabase member variable, this needs to be deleted before the QCoreApplication instance is deleted, otherwise it may lead to undefined behavior. Qt asks you to simply call static QSqlDatabase QSqlDatabase::database(const QString &connectionName = QLatin1String(defaultConnection), bool open = true) whenever you need to access a QSqlDatabase, and not to keep even a member variable QSqlDatabase around. You don't need it.

@Ebrahimi89 said in Qt Franework Installer compile on Windows10: jom: C: \ Users \ me \ Documents \ qtfwi \ build \ src \ sdk \ Makefile.Debug [debug \ installerbase.res] Error 1 jom: C: \ Users \ me \ Documents \ qtfwi \ build \ src \ sdk \ Makefile [debug] Error 2 jom: C: \ Users \ me \ Documents \ qtfwi \ build \ src \ Makefile [sub-sdk-make_first] Error 2 jom: C: \ Users \ me \ Documents \ qtfwi \ build \ Makefile [sub-src-make_first] Error 2 11:07:34: The process "C: \ Qt5.15.2 \ Tools \ QtCreator \ bin \ jom \ jom.exe" exited with code 2. Error while building / deploying project installerfw (kit: Desktop Qt 5.15.2 MSVC2015 64bit) When executing step "Make This is not the actual error, which is probably a few lines before. This is just jom (the build tool) that it gives up. Can you paste the lines before this one? Btw, the forum allows editing code and command line output , please use this to make things easier to read!

@mmmmmmmmmmmmmmmmmmmmmmm Well, that is already a different error message from the one you reported earlier! Plus you said it was working and then "nothing changed, suddenly stopped worked". We don't why that might be. It looks like it has having trouble locating a symbol in one of the DLLs it was compiled/linked to use. What about starting with a basic program like: #include <iostream> int main() { std::cout << "Hello World!"; return 0; } Does that work? Does your executable work if run from a Command Prompt instead of from within Qt Creator? What #includes does your code have, and what does it link with? Show your .pro file, and if possible a minimal example of code which does not work, we do not want reams if it is large code.