[PyQt] PyQt compile error on Windows XP

[Markus Dahlbokum]

On Thursday 06 November 2008 23:37:47 Phil Thompson wrote:
> On Mon, 3 Nov 2008 15:22:44 +0100, Markus Dahlbokum <dahlbokum at intes.de>
>
> wrote:
> > On Monday 03 November 2008 13:39:20 you wrote:
> >> On Mon, 3 Nov 2008 13:10:42 +0100, Markus Dahlbokum <dahlbokum at intes.de>
> >>
> >> wrote:
> >> > Hi,
> >> >
> >> > I'm building PyQt on win XP with the following configuration:
> >> >
> >> > msvc2005
> >> > qt 4.4.3 commercial (static)
> >> > qwt 5.1.1 (static)
> >> > python 2.5.2
> >> > sip 4.7.7
> >> > PyQt 4.4.3 commercial
> >> > PyQwt 5.1.0
> >> >
> >> > All compiles worked but the last step didn't. I'm building PyQt in
> >> > combination
> >> > with PyQwt: configure.py from PyQt with options -g and --mwg-qwt set.
> >>
> >> NMAKE
> >>
> >> > crashes when reaching _qt module:
> >> >
> >> >         cd _qt
> >> >         "C:\Program Files (x86)\Microsoft Visual Studio
> >>
> >> 8\VC\BIN\nmake.exe"
> >>
> >> > Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
> >> > Copyright (C) Microsoft Corporation.  All rights reserved.
> >> >
> >> >
> >> > cl -c -nologo -Zm200 -Zc:wchar_t- -O2 -MD -W3 -w34100 -w34189
>
> -DUNICODE
>
> >> > -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_NO_D
> >> > EBUG -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -DQT_WEBKIT_LIB -DQT_TEST_LIB
> >> > -DQT_SQL_LIB -DQT_SCRIPT_LIB -DQT_NETWORK_LIB -DQT_
> >> > GUI_LIB -DQT_CORE_LIB -I. -Ic:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\qwt -Ic:
> >> > \compile\install\python-2.5.2\
> >> > include
>
> -IC:\compile\source\qt-win-commercial-src-4.4.3\mkspecs\default
>
> >> > -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\
> >> > include\ActiveQt -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\QtAssistant -IC:
> >> > \compile\source\qt-win-commerci
> >> > al-src-4.4.3\include\QtXmlPatterns -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\QtXml -IC:
> >> > \compile\source\qt-
> >> > win-commercial-src-4.4.3\include\QtWebKit -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\QtTest
> >>
> >> -IC:\compile\so
> >>
> >> > urce\qt-win-commercial-src-4.4.3\include\QtSvg -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\QtSql -IC:\compil
> >> > e\source\qt-win-commercial-src-4.4.3\include\QtScript -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\QtNetwork
> >> > -IC:\compile\source\qt-win-commercial-src-4.4.3\include\QtGui -IC:
> >> > \compile\source\qt-win-commercial-src-4.4.3\include\Qt
> >> > Core -IC:\compile\source\qt-win-commercial-src-4.4.3\include -Fo @C:
> >> > \DOCUME~1\bokum\LOCALS~1\Temp\nm1B27.tmp
> >> > sipQtCoreQVariant.cpp
> >> > .\sipQtCoreQVariant.cpp(233) : error
> >> > C2065: 'sipMappedType_QMap_0200QString_0200QVariant' : undeclared
> >> > identifier
> >> > sipQtSqlQSqlQuery.cpp
> >> > .\sipQtSqlQSqlQuery.cpp(882) : error
> >> > C2065: 'sipMappedType_QMap_0200QString_0200QVariant' : undeclared
> >> > identifier
> >> > Generating Code...
> >> > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> >>
> >> Studio
> >>
> >> > 8\VC\BIN\cl.EXE"' : return code '0x2'
> >> > Stop.
> >> > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> >>
> >> Studio
> >>
> >> > 8\VC\BIN\nmake.exe"' : return code '0x2'
> >> > Stop.
> >> >
> >> > Are these undeclared identifiers known with this configuration? Does
> >>
> >> anyone
> >>
> >> > have an idea how to fix this?
> >>
> >> See if you get the same problem without Qwt. Note that the --mwg-*
> >> options
> >> are internal, no longer used and will be removed.
> >>
> >> Phil
> >
> > Yes, the same behaviour when the --mwg option is not set.
> > Gerard from PyQwt helped me out with this and modified the configure.py
>
> to
>
> > work with these versions. On Linux the same configuration works fine. But
> > on
> > windows the compile crashes as described. (I've used the original
> > configure.py to test without qwt)
>
> The problem is a SIP bug triggered by a typedef in QAxBase (which is why
> the problem is Windows specific).
>
> I've added a workaround to tonight's PyQt snapshot.
>
> Phil


Thanks a million.
Markus