[PyQt] faulty PyQt 4.10 Makefile on Windows

[Phil Thompson]

On Sun, 21 Apr 2013 15:24:38 +0200, Mathias.Born at gmx.de wrote:
> On 21.04.2013, 11:37:50 Phil Thompson wrote:
>> On Sun, 21 Apr 2013 11:25:15 +0200, Mathias.Born at gmx.de wrote:
>>> On 21.04.2013, 10:58:11 Phil Thompson wrote:
>>>> On Sun, 21 Apr 2013 01:10:01 +0200, Mathias.Born at gmx.de wrote:
>>>>> Hi,
>>>>> 
>>>>> Both, the latest stable PyQt 4.10 as well as
>>>>> PyQt-win-gpl-snapshot-4.10.1-66f4c96140c6.zip
>>>>> generate Makefiles with errors on my Windows machine.
>>>>> 
>>>>> Instead of
>>>>> 
>>>>>     @if not exist  
>>>>>     D:\_cpp_projects_\Python\Python-3.3.0\Lib\site-packages\PyQt4
>> mkdir 
>>>>  
>>>>>      D:\_cpp_projects_\Python\Python-3.3.0\Lib\site-packages\PyQt4
>>>>> 
>>>>> I get
>>>>> 
>>>>>     @if not exist   # legacy
>>>>>     D:\_cpp_projects_\Python\Python-3.3.0\Lib\site-packages\PyQt4
>> mkdir 
>>>>  
>>>>>         # legacy
>>>>>     D:\_cpp_projects_\Python\Python-3.3.0\Lib\site-packages\PyQt4
>>>>> 
>>>>> in the 'install' target. Then, Microsoft nmake complains.
>>>>> 
>>>>> Manually removing all "# legacy" fixed it. But I couldn't figure out
>>>> which
>>>>> of the
>>>>> build tools put it in there.
>>> 
>>>> That will come from Qt. Which version of Qt?
>>> 
>>>> Phil
>>> 
>>> The official "qt-everywhere-opensource-src-5.1.0-alpha.7z" from
>>> http://qt-project.org/wiki/Qt-5.1-Alpha
>>> 
>>> Compiled without errors.
> 
>> ...so a Qt bug.
> 
>> Phil
> 
> I find that very strange. Are you saying that a Qt bug changes a
> Makefile in _your_ PyQt package where it attempts to copy
> the modules to "..\Lib\site-packages\PyQt4"?

Yes. configure.py reads qmake's spec files to create the Makefiles.

> Admittedly, I couldn't find the text "# legacy" anywhere in sip, nor
> in PyQt.
> Even if it is a Qt bug, would you not be interested in knowing more
about
> it?
> It prevents building PyQt ...

...against an unsupported version of Qt.

Phil