Same as post #3, dependency upon libgcc_s_dw2-1.dll.
It is, but only for the current running instance of Qt Creator. Closing Qt Creator and restarting it from its normal shortcut, that entry is again reported as an invalid Qt installation.And when you add it there then it is not recognized?
I agree with you! That's why I keep pursuing this matter even after having written the following:The question is a bit pointless as Trolls didn't indend it to be dependant on the PATH contents. You must have done something wrong.
At this point, it seems that my original objective should be considered completed, since I could start Qt Creator from a customized batch file that also sets up the environment for it to properly locate the static Qt installation.
EDIT: I tried copying libgcc_s_dw2-1.dll next to qmake.exe (inside C:\Qt\2010.01-Static\bin). Now Qt Creator, when run from its normal shortcut of course, is able to recognize the static Qt installation by pointing to qmake.exe.
qtcreator03.png
But, every project that is built with this configuration ends up with a dependency upon libgcc_s_dw2-1.dll.
Does this mean that I have to rebuild a static version of QMake and if so, how can I do this? Wasn't it supposed to have been taken care of when I configured and built Qt from the sources? Or was the use of the dynamic Qt installation's command prompt environment to build the static Qt, an error in the first place? Please, do not be intimidated by the many and tightly packed questions, I'm just venting a little frustration! And thank you wysota, for bearing with me so far!
Bookmarks