[PyQt] pyqtdeploy-build fails for iOS app

David Morris othalan at othalan.net
Mon Jun 18 10:07:50 BST 2018


It turns out that having PYTHONPATH set was causing the problem.  No clue
how or why.   I have no need for PYTHONPATH anymore so I simply removed it
and am back up and running attempting to get everything compiled.

David

On Sun, Jun 17, 2018 at 3:19 PM, Phil Thompson <phil at riverbankcomputing.com>
wrote:

> On 17 Jun 2018, at 6:24 am, David Morris <othalan at othalan.net> wrote:
> >
> > Phil,
> >
> > "pyqtdeploy-0.0.dev0-py3.6.egg" appears because I am compiling my own
> version of pyqtdeploy from source with a tiny modification to add newline
> characters to the XML file (so that changes in the file can be properly
> detected by version control systems).  In order to eliminate this potential
> unknown, I repeated everything with Python 3.6.4 and the official
> pyqtdeploy 2.1 (installed using `pip install pyqtdeploy==2.1`).  Here is
> the identical error:
> >
> > pyqtdeploy-build --build-dir /Users/morrisde/contract/
> PiranhaColorQt10-2/ios/sysroot/pump --target ios-64 --sysroot
> /Users/morrisde/contract/PiranhaColorQt10-2/ios/sysroot pump.pdy
> > Traceback (most recent call last):
> >   File "/usr/local/var/pyenv/versions/3.6.4/bin/pyqtdeploy-build", line
> 7, in <module>
> >     from pyqtdeploy.pyqtdeploybuild_main import main
> >   File "/usr/local/var/pyenv/versions/3.6.4/lib/python3.6/
> site-packages/pyqtdeploy/__init__.py", line 28, in <module>
> >     from .builder import Builder
> >   File "/usr/local/var/pyenv/versions/3.6.4/lib/python3.6/
> site-packages/pyqtdeploy/builder/__init__.py", line 28, in <module>
> >     from .builder import Builder
> >   File "/usr/local/var/pyenv/versions/3.6.4/lib/python3.6/
> site-packages/pyqtdeploy/builder/builder.py", line 33, in <module>
> >     from PyQt5.QtCore import (QByteArray, QCoreApplication, QDir, QFile,
> > ModuleNotFoundError: No module named 'PyQt5.QtCore'
> > make: *** [pump_xcode] Error 1
> >
> > The above is for python 3.6.4, installed using pyenv but no virtualenv
> to test if the virtual environment was the problem.
> >
> > Any ideas?
>
> I've never used pyenv. I use the standard venv all the time with no
> problems.
>
> Phil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20180618/7894bd88/attachment.html>


More information about the PyQt mailing list