Qt Creator and other tools

I ran into the same problem and this problem is very very annoying during daily work. I filed a bug report for that issue.

@anp405, my first guess would be that by setting PYTHONPATH you are losing the location of PyQt5 package. This depends on your Python and environment setup, but if there is some PYTHONPATH existing, you are overriding it completely instead of complementing. You can verify this by opening a new command line session, setting PYTHONPATH to wherever your code sets it, then running Python interpreter and trying to import PyQt5. Another guess would be that your child process uses different Python environment (e.g. built-in system Python 2), which does not have PyQt5 installed in its site-packages.

Rebuilding on ubuntu 1904 with no system qt5 packages, but with Qt5.12.3 bin bundle solved the problem.

@sgaist I'm having the same problem. But, I do not know how to debug the pyqt5.dylib file. can you explain? thanks

What did you do to fix your issue? I have the same problem.

@sierdzio thanks, added $$escape_expand(\n\t), now it builds

It complains about "2.13" which means it expects Qt 5.13. So going back to Qt 5.12 will definitely not fix the problem. I don't know, maybe the example is broken.

To me, looking at the most current (1903) version of Windows 10, that you have to sent the whole thing as ONE line to the cmd process. The log I captured showed it only doing the first line (partial command). This caused it to try to do the examples, etc. Sent it over as ONE long line in the powershell file, and seems to be working better! But having this all on one is great! Thanks

Solution is to uninstall Qt5 and previous versions. Then install Qt again, selecting the minimum of stuff that you need, including the MSVC 2017 kit. Works now!

@peterchen If you do not get a better answer: The readdir failure looks like it;s having a problem somewhere during the mingw32-make involving a bad directory specification. I do not know the answer, but if you Google for mingw32-make readdir you will find others reporting this issue which may help you diagnose the problem.

@zzc2422 Thanks for reporting back. So please mark this topic as SOLVED now. Regards

That was a wrong move. You basically removed your distribution provided Qt. You can remove the development related package but you should not replace it with the pre-built package. As I already suggested, use the full path to the qmake version you want to use so you ensure you don't mix stuff in your system. Qt Creator does that for you when you have several Qt version installed.

I got around this by setting images in my .qss and setting them in resources.

@alan-b said in Qt Static Build for 32 and 64 bit: When I setup the 32bit Kit, I get an error next to the kit saying the 32bit compiler cannot produce code for this Qt version (x86-windows-msys-pe-64bit). Does this mean I have to build two versions of the static libraries, one for 32bit and one for 64bit ? Yes, you need two completely separated toolchains.

Hi @andyfilms, Can you check if the comment from Maaike at QTCREATORBUG-22812 helps you? For people with the same problem who find this bug report and a Ryzen CPU or another CPU with this problem: Setting environment variable QT_NO_CPU_FEATURE=rdrnd helps! Regards

@paule32 said in What is the default PlugIn-Directory ?: Hello, what is the default Plugin-Directory for QtCreator Plugin's? I have two installation Folders: 1: /usr/local/Qt5/5.13.0 This directory contains a version of the Qt library. It does not contain the Qt Creator IDE. 2: /usr/local/Qt5/Tools/QtCreator This directory contains the Qt Creator IDE. The plugins are in /usr/local/Qt5/Tools/QtCreator/lib/qtcreator/plugins/