@hskoglund No

@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.

@PleaseHelp said in Cannot install qt: With the online installer I get literally no messages. "Your download should start automatically. If it doesn’t, click here." And then it doesn't and I click "here" and literally nothing happens. That sounds like an issue from your web browser. Try a different browser (Chrome, Firefox, Safari, Edge). Disable your extensions.

@fsfarimani no I have not checked each and every package. Also, not every package starting with qt has something to do with that framework. For example qtfaststart is a video related package. If you want more information about the packages provided by brew, you should contact their maintainers. The Qt Project does not handle them.

@SGaist It worked!! 😄😄😄😄 Thanks!!! So for anyone else who stumbled here, the trick was to get this package from the Qt installer : MSVC 2017 64-bit And then go in Qt Creator, and use the aforementioned package as a "kit" to compile the project.

@gregorburger Yes, we had such an issue last week, I hope it will work soon.

@nwoki Hi It means even it reports thats its QtWidgets that crashes, its likely not that DLL if a plain empty GUI project works. ( for exact same folder , same pc) I would next add some openGL to the test project see if it still runs. As it seems might be direclt related to Qt ( like wrong Qt dll loaded) so it could be the openGL for clients gfx card.

Hi and welcome to devnet, Do you mean the Qt Installer Framework ?

@aha_1980 i cleaned my old project build tried it again. The build is successful but when i try to run same error as mentioned above. any changes : just uninstalled Qt5.9.1 .other than that nothing much. this is my compiler tab if it helps any !! p.. i have downloaded windows 10 SDK too now there is no triangle on msvc 32bit one but the problem still remains :/ .

It will be in the future when you'll build Qt again.

@JScars Please try binaries from http://download.qt.io/snapshots/ci/qtwebkit/qtwebkit/qtwebkit-Windows-Windows_7-Mingw53-Windows-Windows_7-X86.7z

Old post but I had the same error; I had to build qtdeclarative BEFORE qwebchannel to solve this error.

Because QT_INSTALL_PLUGINS is defined at build time and is known to qmake. As for the double $ problem, that's rather a question for the NodeBB folks

@Bart_Vandewoestyne said: we're storing our Qt build in our version management system This is a strange thing to do, since Qt guarantees binary compatibility between minor versions, but well, you're free to choose. Unfortunately, I don't see how you could decrease the size further, beside deleting the docs, as the libraries are in the /lib directory and they're the next biggest size. Maybe store only the libs that you're using, i.e. these that you're going to deploy. No point in keeping QtXml if you're not using it, right?

Alternatively, you can get the standalone Qt + Qt Creator package from http://www.qt.io/download-open-source/ -- you don't need to wait for the distro packagers to catch up. The latest versions are Qt 5.5 and Qt Creator 3.6.0

Were you able to solve this issue? I ran into the same problem on a Virtual Machine with Ubuntu Server 14.04

Hi and welcome to devnet, What sources did you download ? You have an option in the installer to get the sources that matches your installed Qt. If you take the time to search the forum, you'll find several threads about the MySQL plugin and OS X.

Hi. I did what you said and it worked! thank you very much

Hi and welcome to devnet, Usually: chmod +x name_of_the_file.run and then ./name_fo_the_file.run

Thanks for your answer It's actually a dll but I get what you are saying. I tried adding target.files = $$DESTDIRNAME/*.dll target.files += $$DESTDIRNAME/*.lib target.files += $$DESTDIRNAME/*.pdb where DESTDIRNAME is the same value as DESTDIR but no change

Hi @PabloAmunt, packaging for Linux is a major pain in the ass. If you are targeting Ubuntu the place to start is the Ubuntu packaging guide: http://packaging.ubuntu.com/ Good luck!