[Solved] Where is dumpcpp?
-
Hi,
Simple question: Where is dumpcpp? Its not located in my qt 5.4 install, is there a specific component that i must install to get access to it?
Thanks.
-
Hi and welcome to devnet
dumpcpp.exe is part of the compiler. Which compiler do you have installed?
-
Hi,
Simple question: Where is dumpcpp? Its not located in my qt 5.4 install, is there a specific component that i must install to get access to it?
Thanks.
OK I found the qtactive sources and built it myself. I downloaded the source via the Qt maintenance tool under:
Qt 5.4->Source Components-> Add-ons-> qtactiveat
-
Did you install the MinGW compiler through the maintenance tool?
I have Qt 5.3 and Qt5.4 installed with MinGW 4.8 and 4.9. dumpcpp.exe is stored in the respective bin folder of MinGW compilers.Yes I did; MSVC compilers were configured by the initial installer, but I just installed MinGW today. Here a picture of the maintenance tool showing all the components that are installed:
There is no dumpcpp.exe anywhere within my qt folder.
[edit, koahnig] link to image corrected
-
That is the path where I found it: c:\Qt\5.4\mingw491_32\bin\dumpcpp.exe
I have checked the MinGW version is showing the same numbers as in your case. However, I have Qt 5.4.1 installed and not Qt 5.4.2.Anyway, you have found a solution for your problem.
-
That is the path where I found it: c:\Qt\5.4\mingw491_32\bin\dumpcpp.exe
I have checked the MinGW version is showing the same numbers as in your case. However, I have Qt 5.4.1 installed and not Qt 5.4.2.Anyway, you have found a solution for your problem.
Yeah its not there:
Thanks for your help anyway, I've got dumpcpp working, now to fight through a bunch more ActiveX interop problems :)
-
I found it on JIRA as bug report, but it is closed already. However, it does not show why it has been closed. Possibly because of newer version?
-
I've downloaded the 5.5 msvc2013 kit and dumpcpp.exe has returned to the bin folder.
-
@SGaist
You are right, but that is closed as well. However, at least it shows that it has been fixed for 5.5.0.
Yesterday, I must have followed another route which ended also with closed, but no reference why. Neverthelees, I understand that this is probably a drawback of the reporting system rather than Qt libs.
