Re: Incorrect file names in sip-4.19 configure script for Windows
Patrick Stinson <[email protected]> Fri, 24 Apr 2020 08:07:22 -0800
| Newsgroups | gmane.comp.python.pyqt-pykde |
|---|---|
| Message-ID | <[email protected]> |
Yes. Some of the paths are different because there is no install step that produces a python dist for hierarchy - that I know of. Everything occurs in place in the source build dir and in different locations. For what it’s worth, I just built with PCBuild/build.bat as described here: https://cpython-core-tutorial.readthedocs.io/en/latest/build_cpython_windows.html Though some of these problems also have to do with using a debug build of python. > On Apr 24, 2020, at 12:16 AM, Phil Thompson <[email protected]> wrote: > > 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