[PyQt] PyQt5 5.7.1 Bug: debug build on Windows broken

[Phil Thompson]

On 17 Jan 2017, at 8:58 pm, Mathias Born <mathias.born at gmx.de> wrote:
> 
>> -----Original Message-----
>> From: Phil Thompson [mailto:phil at riverbankcomputing.com]
>> Sent: Dienstag, 17. Januar 2017 13:01
>> To: Mathias Born <mathias.born at gmx.de>
>> Cc: pyqt at riverbankcomputing.com
>> Subject: Re: [PyQt] PyQt5 5.7.1 Bug: debug build on Windows broken
>> ...
>>> 
>>> It would be nice if there were an option to disable the use of the
> limited
>>> API for
>>> release builds.
>> 
>> I've added a --link-full-dll option to configure.py to force the full API
> DLL to be
>> linked. You should only need --debug if you want to build debug versions
> of
>> the PyQt modules.
> 
> Thanks, that new option will be very useful.
> 
> However, please clarify "--debug". I understand there are now 4 distinct
> 'debug' build options:
> 
> (1)
> Run configure.py on python_d.exe with option "--debug".
> This creates debug versions of the modules which link against the debug
> version of
> Python and the debug version of the MS-runtime libs.
> I verified that this works.
> 
> (2)
> Run configure.py on python_d.exe without option "--debug".
> What happens here?

Links against the debug version of Python.

> (3)
> Run configure.py on python.exe with option "--debug".
> This creates a configuration which cannot be built because Python does not
> allow
> the use of the limited API in debug mode.

--debug no longer requires a debug version of Python on Windows, so this creates debug versions of the modules (but untested).

> (4)
> Run configure.py on python.exe with option "--debug" and the new
> "--link-full-dll".
> Don't know whether this works, but it should create debug versions of the
> modules
> which link against the release version of Python and the release version of
> the
> MS-runtime libs. (Is that right? You can't mix debug and release versions of
> the runtime
> libs.)
> What would this be good for?

Nothing that I can see.

> Don't get me wrong, I'm happy to have option (1), but isn't all this a
> documentation
> nightmare?

I don't think so. --debug (now) does one thing only. Using a debug build of Python does one thing only.

Phil