'Re: [PyQt] Incorrect file names in sip-4.19 configure script for Windows'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: pykde
Subject: Re: [PyQt] Incorrect file names in sip-4.19 configure script for Windows
From: Patrick Stinson <patrickkidd () gmail ! com>
Date: 2020-04-24 16:07:22
Message-ID: B0EA1CE9-523B-497E-B327-1F8DBB14B6A5 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

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 <phil@riverbankcomputing.com> 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

[Attachment #5 (text/html)]

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body \
dir="auto"><div dir="ltr">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:&nbsp;<a \
href="https://cpython-core-tutorial.readthedocs.io/en/latest/build_cpython_windows.html">https:/ \
/cpython-core-tutorial.readthedocs.io/en/latest/build_cpython_windows.html</a></div><div \
dir="ltr"> </div><div dir="ltr">Though some of these problems also have to do with using a \
debug build of python.</div><div dir="ltr"> <blockquote type="cite">On Apr 24, 2020, at \
12:16 AM, Phil Thompson &lt;phil@riverbankcomputing.com&gt; \
wrote: </blockquote></div><blockquote type="cite"><div dir="ltr">On 24/04/2020 \
06:50, Patrick Stinson wrote: <blockquote \
type="cite">Hello, </blockquote><blockquote type="cite">I ran into a few \
problems with configuring, building, and installing </blockquote><blockquote \
type="cite">sip-4.19.19 script on windows using python built from source \
(with </blockquote><blockquote type="cite">PCBuild\build.bat). Here they are \
along with my workarounds: </blockquote><blockquote \
type="cite">SIP </blockquote><blockquote type="cite">- It expects \
site-packages\PyQt5 to already exist when passing </blockquote><blockquote \
type="cite">—sip-module=PyQt5.sip. I worked around this by patching \
configure.py </blockquote><blockquote type="cite">to create the dir if it \
doesn't exist (see attached diff) </blockquote><blockquote type="cite">- For a \
python built from source, configure.py expects pythonxx.lib \
or </blockquote><blockquote type="cite">pythonXX_d.lib to be in \
PYTHON_ROOT\\libs. I hacked configure.py to </blockquote><blockquote \
type="cite">use PYTHON_ROOT\\amd64 instead (see attached \
diff). </blockquote><blockquote type="cite">- As with sip above, I hacked \
configure.py to include the '_d' debug </blockquote><blockquote \
type="cite">suffix for each entry in installed.txt so that `nmake install` \
would </blockquote><blockquote type="cite">pick up the correct file names (see \
attached diff). </blockquote><blockquote \
type="cite">PYQT5 </blockquote><blockquote type="cite">- The include \
paths need to include both PYTHON_ROOT\include for </blockquote><blockquote \
type="cite">Python.h and PYTHON_ROOT\PC for pyconfig.h. I worked around this \
by </blockquote><blockquote type="cite">manually appending PYTHON_ROOT\PC to \
include_paths just before the </blockquote><blockquote type="cite">call to \
generate_module_makefile(). </blockquote><blockquote type="cite">- As describe \
above with sip, for a python built from source, </blockquote><blockquote \
type="cite">configure.py expects pythonxx.lib or pythonXX_d.lib to be \
in </blockquote><blockquote type="cite">PYTHON_ROOT\\libs. I hacked \
configure.py to use PYTHON_ROOT\\amd64 </blockquote><blockquote \
type="cite">instead (see attached diff). </blockquote><blockquote \
type="cite">- As with sip above, I hacked configure.py to include the '_d' \
debug </blockquote><blockquote type="cite">suffix for each entry in \
installed.txt so that `nmake install` would </blockquote><blockquote \
type="cite">pick up the correct file names &nbsp;(see attached \
diff). </blockquote><blockquote type="cite">Am I making any big mistakes here \
that would make life easier? </blockquote> Are you saying that \
a Python installation built from source behaves differently than one installed from \
python.org? Phil </div></blockquote></body></html>

[Attachment #6 (text/plain)]

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

[prev in list] [next in list] [prev in thread] [next in thread] 