DoctorWatson
1st May 2009, 09:59
I'm having quite a time trying to get Qt and Visual C++ to place nice. I have a fully functional windows C++ console app that I want to convert into a Qt GUI app. My app needs to use some Windows libraries, such as setupapi.lib, so it can talk to some hardware.
I tried using Qt Creator first, but MingW complained about files from the Windows SDK (i.e. winnt.h) due to inline assembly, compiler-specific macros and what not. Also, my app using std::wstringstream, which MingW doesn't seem to support.
So I then complied Qt with Visual C++, but now the std::wstringstream problem does not go away. This has lead me to believe that when I execute the following,
C:\Project> qmake
C:\Project> nmake
The make file generated by qmake seems to be point Microsoft's nmake to the MingW version of the STL libraries. Unfortunately I'm not quite savvy enough with Qt to know how to get it to stop doing that.
Has anyone run into this problem before? Any ideas?
I tried using Qt Creator first, but MingW complained about files from the Windows SDK (i.e. winnt.h) due to inline assembly, compiler-specific macros and what not. Also, my app using std::wstringstream, which MingW doesn't seem to support.
So I then complied Qt with Visual C++, but now the std::wstringstream problem does not go away. This has lead me to believe that when I execute the following,
C:\Project> qmake
C:\Project> nmake
The make file generated by qmake seems to be point Microsoft's nmake to the MingW version of the STL libraries. Unfortunately I'm not quite savvy enough with Qt to know how to get it to stop doing that.
Has anyone run into this problem before? Any ideas?