Looks like the hint I found here: http://stackoverflow.com/questions/4699311/how-to-install-qt-on-windows-after-building/17640221#17640221
--> cd <path> --> installer.exe --runoperation QtPatch windows <path> qt5 worked. At least as far as I could verify it at the moment. So generally with some cleanup work I can get a self compiled Qt5, which is equivalent to one of the official installer packages. A perfect solution this this certainly not. Guido On Sun, 23 Mar 2014 02:46:43 +0100 Guido Seifert <warg...@gmx.de> wrote: > > Thank you. Your answer at least shows me that I am not the only one with this > problem. I was not sure, if is was only my combination of configure options, > which causes this problem. I will try your solution, but still... Isn't this > something that really should be fixed? I don't think I had this problem with > Qt 5.1. > > Guido > > > Well, you could try what we do under Windows: Map a network drive to the > > path > > where you want Qt to function, and then build it there. For example, we map > > drive letter Q: and then build Qt there under Q:\Qt\<version>. We can then > > point the mapped drive to any other location on the disc, and Qt is > > perfectly > > happy. And this mapping can be used on any Windows machine where we want to > > develop. > > > > Just an alternative to think about. > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
