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

List:       pykde
Subject:    Re: pyqtdeploy demo will not build
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2020-09-22 9:05:36
Message-ID: 904e4f997834220a1ebff88d08652267 () riverbankcomputing ! com
[Download RAW message or body]

As I said, pyqtdeploy knows nothing about the SDKs locations and assumes 
that xcrun will return the correct values. If it doesn't then that 
suggests a problem with your Xcode installation.

Phil

On 22/09/2020 09:53, Chris Robson wrote:
> Thanks for replying Phil, this thing is giving me one nasty headache,
> grrrr.... anyway
> 
> Sorry for the confusion, but it only works for macOS.  It does not
> work for the iPhone.
> 
> Below are the various outputs from the commands you suggested and I
> have tried previously.  But I just not sure this is not the problem. 
> The issue appears to be, I'm guessing here, that Apple has moved the
> c++/V1 headers
> 
> from
> 
> ./iPhoneOS14.0.sdk(or MacOSX10.15.sdk)/usr/include/c++/V1 directory
> 
> to:
> 
> /Library/Developer/CommandLineTools//usr/include/c++/v1/
> 
> If these are the correct files, my concern is using a link or even
> copying them back to the old path will break the MacOSX behavior.  So
> it seems to me something in the pyqtdeploy build process should be
> changed but what?
> 
> thanks.....Chris
> 
> iPhone:
> 
> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.0.sdk
>  
> macOS:
> 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk
>  
> 
> On 9/22/20 4:28 AM, Phil Thompson wrote:
> > You say that build-demo.py works fine. For both macOS and iOS? If so, 
> > what command are you actually running that causes the error?
> > 
> > pyqtdeploy uses xcrun to determine the locations of the SDks. For 
> > iOS...
> > 
> > xcrun --sdk iphoneos --show-sdk-path
> > 
> > For macOS...
> > 
> > xcrun --sdk macosx --show-sdk-path
> > 
> > Phil
> > 
> > On 21/09/2020 23:44, Chris Robson wrote:
> > > Phil
> > > 
> > > I think I found the c++ header files.  Am I overlooking something as
> > > to why the build process is pointing in the wrong direction? Are the
> > > files I found the ones that are used?  I could just config a soft 
> > > link
> > > but I suspect that is the wrong approach.  Thoughts?
> > > 
> > > Aka the build looks in:
> > > 
> > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/c++/v1 \
> > >  but the files are actually in:
> > > 
> > > /Library/Developer/CommandLineTools/usr/include/c++/V1/
> > > 
> > > On 9/21/20 6:26 PM, Chris Robson wrote:
> > > > Well I've moved on, realizing I want to deploy to iOS so moved to my 
> > > > Mac.  The pyqtdeploy build-demo.py commandline from the tutorial 
> > > > builds just fine. However, when trying to build for the iOS using 
> > > > the command pyqtdeploy-sysroot --verbose --target ios-64 
> > > > sysroot.toml the following error stops the build.  Looks like 
> > > > something isnt set right for Xcode, aka, the warning about using 
> > > > sysroot and a incompatible sysroot?  What I find so far is 
> > > > MacOSX10.15.sdk is there but not ./usr/include/c++.  I'm reading 
> > > > somehting about missing header files but its from 2018 so out of 
> > > > date.
> > > > 
> > > > I'm poking around trying to find were I didnt configure something 
> > > > correctly but any help you can give I'd be grateful.  Note, Xcode is 
> > > > installed and I am very successful using it to cross compile Python 
> > > > apps for iPhones, so I must be missing something here.... thanks
> > > > 
> > > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/ \
> > > >                 
> > > > ld: warning: building for iOS, but linking in .tbd file 
> > > > (/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/lib/libc++.tbd) \
> > > >  built for macOS/Mac Catalyst
> > > > ld: building for iOS, but linking in object file built for iOS 
> > > > Simulator, file 
> > > > '/var/folders/1m/c7ddhcn91ts281fx2t40l0xm0000gn/T/--ade64a.o' for 
> > > > architecture x86_64
> > > > clang: error: linker command failed with exit code 1 (use -v to see 
> > > > invocation)
> > > > ===================
> > > > Maybe you forgot to setup the environment?
> > > > pyqtdeploy-sysroot: execution of 
> > > > '/Users/chrislrobson/Qt/5.15.0/clang_64/bin/qmake' failed: returned 
> > > > exit code 3
> > > > 
> > > > FURTHER UP THE TRACE IS THE FOLLOWing ERROR::::::::
> > > > 
> > > > Running '/Users/chrislrobson/Qt/5.15.0/clang_64/bin/qmake 
> > > > SYSROOT=/Users/chrislrobson/develop-MAC/PyQt5/pyqtdeploy-3.1.1.dev2009161438/demo-working/sysroot-ios-64'.
> > > >                 
> > > > Info: creating stash file 
> > > > /Users/chrislrobson/develop-MAC/PyQt5/pyqtdeploy-3.1.1.dev2009161438/demo-working/sysroot-ios-64/build/Python-3.7.8/Python-3.7.8/.qmake.stash
> > > >  Project ERROR: Cannot run compiler 
> > > > '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++'. \
> > > >  Output:
> > > > ===================
> > > > Apple clang version 12.0.0 (clang-1200.0.32.2)
> > > > Target: x86_64-apple-darwin19.6.0
> > > > Thread model: posix
> > > > InstalledDir: 
> > > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> > > > clang: warning: using sysroot for 'MacOSX' but targeting 'iPhone' 
> > > > [-Wincompatible-sysroot]
> > > > ignoring nonexistent directory 
> > > > "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include/c++/v1"
> > > >  
> > > > On 9/21/20 4:40 PM, Phil Thompson wrote:
> > > > > On 21/09/2020 20:03, Chris Robson wrote:
> > > > > > It seems to be missing a file but as one can see from the rpm -qa 
> > > > > > list
> > > > > > the x11extras library is installed.
> > > > > > 
> > > > > > Build fails performing the build:  python build-demo.py --verbose
> > > > > > 
> > > > > > Error:
> > > > > > 
> > > > > > /home/ch/develop/TypMic/PYQTDEPLOY/pyqtdeploy-3.1.1.dev2009161438/demo/sysroot-linux-64/Qt/bin/qmake \
> > > > > >                 
> > > > > > -recursive PyQt5.pro
> > > > > > sip-install:
> > > > > > '/home/ch/develop/TypMic/PYQTDEPLOY/pyqtdeploy-3.1.1.dev2009161438/demo/sysroot-linux-64/Qt/bin/qmake \
> > > > > >                 
> > > > > > -recursive PyQt5.pro' failed returning 3
> > > > > > Info: creating stash file /tmp/tmp2kk_5t_s/.qmake.stash
> > > > > > Reading /tmp/tmp2kk_5t_s/QtCore/QtCore.pro
> > > > > > Reading /tmp/tmp2kk_5t_s/QtNetwork/QtNetwork.pro
> > > > > > Reading /tmp/tmp2kk_5t_s/QtGui/QtGui.pro
> > > > > > Reading /tmp/tmp2kk_5t_s/QtWidgets/QtWidgets.pro
> > > > > > Reading /tmp/tmp2kk_5t_s/QtX11Extras/QtX11Extras.pro
> > > > > > Project ERROR: Unknown module(s) in QT: x11extras
> > > > > > pyqtdeploy-sysroot: execution of 'sip-install' failed: returned 
> > > > > > exit code 1
> > > > > > 
> > > > > > OS: Fedora 31
> > > > > > 
> > > > > > pyqtdeploy version: 3.1.1.dev2009
> > > > > > 
> > > > > > 
> > > > > > pip list:
> > > > > > 
> > > > > > packaging    20.4
> > > > > > pip          20.2.3
> > > > > > pyparsing    2.4.7
> > > > > > PyQt-builder 1.5.0
> > > > > > PyQt5        5.15.1
> > > > > > PyQt5-sip    12.8.1
> > > > > > pyqtdeploy   3.1.1.dev2009161438
> > > > > > setuptools   41.6.0
> > > > > > sip          5.4.0
> > > > > > six          1.15.0
> > > > > > toml         0.10.1
> > > > > > 
> > > > > > 
> > > > > > Installed libraries:
> > > > > > 
> > > > > > qt5-qtx11extras-devel-5.13.2-1.fc31.x86_64
> > > > > > qt5-qtx11extras-5.13.2-1.fc31.x86_64
> > > > > > qt5-qtx11extras-doc-5.12.3-2.fc31.noarch
> > > > > 
> > > > > The demo builds it's own copy of Qt so the distro installation of 
> > > > > Qt is irrelevant.
> > > > > 
> > > > > See the "Note" in...
> > > > > 
> > > > > https://www.riverbankcomputing.com/static/Docs/pyqtdeploy/demo.html#building-the-demo \
> > > > >  Phil


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

Configure | About | News | Add a list | Sponsored by KoreLogic