I'm building Wireshark for Windows from source, and have run into a problem. I previously was trying to run the .exe file from the build directory, which did not work. It told me I was missing a file. Now I've gone to the wireshark-gtk2 directory, where I'm supposed to, and that problem cleared up. However, now it is telling me "The program can't start because Qt5PrintSupport.dll is missing from your computer. Try reinstalling the program to fix this problem." I've checked and the file truly doesn't seem to be there. Why is this? What step did I miss to not have this file (or is it located somewhere else that my PATH can't see?) What do I do? asked 12 Jan '15, 05:38  mehubb985 |
One Answer:
When building on Windows, to run the built versions you must run from the special directories that contain all the 3rd party DLL's. For the new QT based version, use wireshark-qt-release\Wireshark.exe and for the older GTK based version use wireshark-gtk2\Wireshark-gtk.exe. Note the different program names. As to your issue, I can't think of any reason why the gtk version would require a QT5 DLL. Are you sure you're running Wirehark-gtk.exe? answered 12 Jan '15, 06:20  grahamb ♦ When I got this error, I was running the wireshark-qt-release\Wireshark.exe from the wirehsark-gtk2 directory. Running the Wireshark-gtk.exe from that directory seems to work. Running the wireshark-qt-release\Wireshark.exe file from the wireshark-qt-release directory had a similar error but with a different dll file. Not sure why that one didn't work. (12 Jan '15, 06:44) mehubb985 What version of Visual Studio and QT are you using? (12 Jan '15, 06:58) grahamb ♦ 2010 for Visual Studio, 5.3 for QT (12 Jan '15, 07:00) mehubb985 For QT 5.3 the build should be using the QT windeployqt tool to copy all the required QT components into wireshark-qt-release, so I can't think what's gone wrong there. What is the exact error when running wireshark-qt-release\Wireshark.exe? (12 Jan '15, 07:27) grahamb ♦ |
I just saw the same problem. My solution was to build and run the NSIS packager (which includes the actions of windeployqt?). After that the DLLs were all found when I ran my own build of wireshark.exe