Re: Incorrect file names in sip-4.19 configure script for Windows

On 24/04/2020 06:50, Patrick Stinson wrote:
> Hello,
> 
> I ran into a few problems with configuring, building, and installing
> sip-4.19.19 script on windows using python built from source (with
> PCBuild\build.bat). Here they are along with my workarounds:
> 
> 
> SIP
> 
> - It expects site-packages\PyQt5 to already exist when passing
> —sip-module=PyQt5.sip. I worked around this by patching configure.py
> to create the dir if it doesn’t exist (see attached diff)
> 
> - For a python built from source, configure.py expects pythonxx.lib or
> pythonXX_d.lib to be in PYTHON_ROOT\\libs. I hacked configure.py to
> use PYTHON_ROOT\\amd64 instead (see attached diff).
> 
> - As with sip above, I hacked configure.py to include the '_d' debug
> suffix for each entry in installed.txt so that `nmake install` would
> pick up the correct file names (see attached diff).
> 
> 
> PYQT5
> 
> - The include paths need to include both PYTHON_ROOT\include for
> Python.h and PYTHON_ROOT\PC for pyconfig.h. I worked around this by
> manually appending PYTHON_ROOT\PC to include_paths just before the
> call to generate_module_makefile().
> 
> - As describe above with sip, for a python built from source,
> configure.py expects pythonxx.lib or pythonXX_d.lib to be in
> PYTHON_ROOT\\libs. I hacked configure.py to use PYTHON_ROOT\\amd64
> instead (see attached diff).
> 
> - As with sip above, I hacked configure.py to include the '_d' debug
> suffix for each entry in installed.txt so that `nmake install` would
> pick up the correct file names  (see attached diff).
> 
> 
> Am I making any big mistakes here that would make life easier?

Are you saying that a Python installation built from source behaves 
differently than one installed from python.org?

Phil
_______________________________________________
PyQt mailing list    [email protected]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt