Qt5 platforms plugins ?
-
It MIGHT be an issue with your VS 2012 build. I don't have VS 2012 installed, so I can't investigate for you, sorry. Are you willing to try a VS 2010 build (or "MinGW":http://qt-project.org/forums/viewthread/23002/), and see if that works?
-
I've got exactly the same setup here: VS2010 from Qt download pages and personally compiled VS2012 version, but everything seems to work out of the box.
Another thing to try would be to use Profiling option in Dependency Walker. In the profiling window you can select "Use full paths when logging file names". The output is somewhat messy but you can use find(ctrl+f) to find qwindows.dll and other modules and check from what path they are actually loaded and why are they doubled.
-
@JKSH
Can't do with VS2010, I have problems installing VS2010 in my computer since it won't compile even an ordinary VS2010 app. Got errors like "oldnames.lib" something errors. Found out header files weren't installed. Tried and tried but never solved it ... even the M$ forum can't help... so I removed it. Only have VS2008 and VS2012 on my machine.But for the mingw, I think I will take a look at that since mingw is ok with my machine. Thanks
@Krzysztof
I will recheck dependency walker. Thanks -
[quote author="soroush" date="1358092375"]Did you set QT_PLUGIN_PATH environment variable ? [/quote]
NO....
-
[quote author="JKSH" date="1358040589"]Very strange. Some questions:
I presume it says Failed to load platform plugin "windows"., and not another plugin; is that correct?
What's your OS? What many bits?
Did you download the precompiled Qt 5.0.0, or build it yourself?
Is Qt 5 in your PATH?
Did you copy the other DLLs (e.g. Qt5Core.dll) into your application folder?[/quote]
Yes you are right. But it says that plugins are available... I really dont understand what is going on...
- Windows 7 Professional x64 bit.
- I have been using both of them but not at once.
- Qt is not in my environment
- Yes, I did.
-
I'm quite lost here, to be honest. :-/
Try running your program from within CDB -- it will show you a list of DLLs that are being loaded, and it just might provide a clue.
-
Well, I have found solution in copying also libEGL.dll or libEGLd.dll (depends on what type of building do you run!) into the root application library...what a freaking mistake!
-
[quote author="Peppy" date="1358179576"]Well, I have found solution in copying also libEGL.dll or libEGLd.dll (depends on what type of building do you run!) into the root application library...what a freaking mistake!
Thanks to: http://qt-project.org/forums/viewthread/21269[/quote]
Wow! Mine worked too! Thanks
-
Solved it for me as well.
-
Just wanted to say I had this issue as well. Solve for me. Found through google so I figured I'd bump it.
-
Adding libEGL.dll worked for me too. Was long for me to find the solution so I figured I'd bump it too.
-
I was getting that exact same "failed to load" error, however, I didn't compile my own binaries - I used the ones from the softwareforge project qt-x64 : http://sourceforge.net/projects/qtx64/ .
It turns out that they bundle a utility in there called qtbinpatcher.exe that patches the binaries where the paths have been hardcoded in. Once I ran that everything worked.
Is it just me, or does hardcoding an absolute path into the binaries like that seem like horrible idea? What were they thinking?
-
[quote author="Ph0t0n" date="1392352947"]I was getting that exact same "failed to load" error, however, I didn't compile my own binaries - I used the ones from the softwareforge project qt-x64 : http://sourceforge.net/projects/qtx64/ .
It turns out that they bundle a utility in there called qtbinpatcher.exe that patches the binaries where the paths have been hardcoded in. Once I ran that everything worked.
Is it just me, or does hardcoding an absolute path into the binaries like that seem like horrible idea? What were they thinking?[/quote]I agree that it is a horrible idea. Unfortunately, it's not something that's easy to undo -- so we'll have to deal with it for now.
Anyway, welcome to the Qt Dev Net! I'm glad you found a solution to your problem. Thank you for sharing your solution.
