- All (478)
- jom (0)
- Qt Linguist (7)
- Qt Eclipse Integration (9)
- Qt Designer (7)
- Qt Creator (4)
- Qt build system: qmake (31)
- Qt build system: configure (3)
- Qt Assistant (5)
- Printing (4)
- Porting from Qt 3 to Qt 4 (1)
- Plugins (7)
- Qt Visual Studio AddIn (2)
- Qt/MFC Migration (2)
- QtScript (3)
- MDI (2)
- XML (1)
- Widgets (22)
- WebKit (5)
- Tools and Containers (2)
- Threads (2)
- Text Handling (10)
- SQL (6)
- QtTest (1)
- QtService (1)
- Platform: Windows (49)
- Platform: Unix (16)
- Platform: Mac OS X (18)
- Image Formats (2)
- I/O (2)
- Graphicsview (8)
- Font handling (9)
- Event System (18)
- Drag and Drop (4)
- Dialogs (6)
- Desktop integration (3)
- ActiveQt (3)
- Itemviews (60)
- Layout (4)
- Qt Quick (10)
- Qt SDK (1)
- Licensing (2)
- Platform: Embedded Linux (38)
- Painting (32)
- OpenGL (4)
- Object Model (6)
- Network (5)
- Multimedia (3)
- Miscellanous (23)
- Main Window (19)
- Look and Feel (23)
- Development (0)
- Getting Involved (0)
- Routines (0)
Why do I get the following error: QtMain.lib(qtmain_win.obj) : fatal error LNK1103: debugging information corrupt; recompile module?
This error can occur when downloading the wrong binary package, e.g when downloading qt-win-commercial-4.6.3-vs2008.exe and using it with Visual Studio 2005, so make sure you have downloaded the correct package.
This error can also occur when having 2 compilers installed and not using the same compiler that was used for building the package. In this case, you need to ensure that your environment is set up correctly for the compiler you want to use. If you have installed the binary package for VS 2008 for example, you need to use it with the VS 2008 compiler. In order to do so, then use the command prompt provided with the binary package or select the “Visual Studio with Qt SomeVersion” option in the Start menu.
You can check if the correct compiler is set up in your environment, by typing
- set
in the command prompt provided with the binary package. Then you need to make sure the compiler you want to use is listed first in your PATH environment variable.
Alternatively, you can use the command prompts provided with Visual Studio and call
- set qmakespec=theMkSpecYouUse
- PATH=%path%;yourQtVersion/bin;
to make sure you use the Qt version built with that compiler.
1 comment
December 3, 2011
Lab Rat
it’s a bug.
you should rebuild qt for win32-msvc2005
at present, we need keep qt’s all files for win32-msvc2008, and we need copy all these files to another directory and rebuild it for msvc2005.
if we are working for a wince project at the same time, we need copy qt to a new directory like ‘qt-wince’ for rebuilding qt for wince platform.
then we need keep 3 copies of QT for these platforms.
:(