That's what I meant by saying, I tested it directly from the command line. It worked, but when it's done automatically by Qt Creator, it fails.
I still don't understand why... I opened uic.exe in Qt/qt/bin with DependencyWalker, to see what dlls it is using. It doesn't rely on many dlls.
KERNEL32.dll, MSVCRT.dll, USER32.dll in system32; LIBGCC_S_DW2-1.dll in Qt/qt/bin (where uic.exe is, too), and LIBSTDC++-6.dll from my MinGW directory.
The systems PATH variable looks like the following:
%SystemRoot%;
%SystemRoot%\System32;
D:\Entwicklung\Qt\qt\bin;
D:\Entwicklung\MinGW\bin;
D:\Entwicklung\Qt\bin;
D:\Entwicklung\MinGW\msys\1.0\bin;
...
...
...
My users PATH variable is empty and I didn't change anything in Qt's project build environment.
So, if uic.exe is working with the dlls, I've written above why doesn't it in Qt Creator? Since I adjusted the PATH to search in the correct directories first, Qt Creator should use the same dlls, as when it's called directly...





Reply With Quote

Bookmarks