Python Pyqt Install
What MacOS version are you running?
There seem to be two signifcant differences between that I think might be the cause of the issue:
1. I think the issue might be caused because the cefpython module was built using clang and linked against libc++ and the Python.org package is built with an old version of gcc 4.2. It seems that Python.org package is built with gcc 4.2 compiler while system Python 2.7 is built with clang compiler. I've checked also Homebrew Python that works fine with cefpython and it seems that it is also built with clang compiler (it checks for ENV.compiler option). I think that Chromium/CEF can work with both gcc and clang compilers, however I've had problems with making it work with gcc compiler. So the cefpython module links against libc++. Since Chromium v56 the minimum OS supported is MacOS 10.9+. MacOS 10.9+ no longer uses GCC/libstdc++, but uses libc++ and Clang. So it is okay for cefpython to be built with clang and linked against libc++, as the minimum requirements for Chromium do support this (Mac OS 10.9+).
2. I wonder if the `--enable-universalsdk=/Developer/SDKs/MacOSX10.6.sdk` flag is causing any issue, but it's a little chance I think.
I think that the issue can be resolved if you build Python yourself. Download Python sources from Python.org and build it with the --enable-framework flag. Make sure that Python builds with clang. If you're using Mac OS 10.9 or higher that should be the default. The Python.org binaries that you've installed were built with gcc 4.2, so that it supports old OSes (Mac OS 10.6+).
I am not sure if anything can be done (and should) the cefpython side. It is how things work on Mac. They replaced the default compiler to clang/libc++ on Mac OS 10.9. And Mac OS 10.9 is the minimum requirement for cefpython/CEF/Chromium. The minimum supported version of gcc supported by Chromium is gcc 4.8+.
I hope this clears things up.
Cheers.
There seem to be two signifcant differences between that I think might be the cause of the issue:
1. I think the issue might be caused because the cefpython module was built using clang and linked against libc++ and the Python.org package is built with an old version of gcc 4.2. It seems that Python.org package is built with gcc 4.2 compiler while system Python 2.7 is built with clang compiler. I've checked also Homebrew Python that works fine with cefpython and it seems that it is also built with clang compiler (it checks for ENV.compiler option). I think that Chromium/CEF can work with both gcc and clang compilers, however I've had problems with making it work with gcc compiler. So the cefpython module links against libc++. Since Chromium v56 the minimum OS supported is MacOS 10.9+. MacOS 10.9+ no longer uses GCC/libstdc++, but uses libc++ and Clang. So it is okay for cefpython to be built with clang and linked against libc++, as the minimum requirements for Chromium do support this (Mac OS 10.9+).
2. I wonder if the `--enable-universalsdk=/Developer/SDKs/MacOSX10.6.sdk` flag is causing any issue, but it's a little chance I think.
I think that the issue can be resolved if you build Python yourself. Download Python sources from Python.org and build it with the --enable-framework flag. Make sure that Python builds with clang. If you're using Mac OS 10.9 or higher that should be the default. The Python.org binaries that you've installed were built with gcc 4.2, so that it supports old OSes (Mac OS 10.6+).
I am not sure if anything can be done (and should) the cefpython side. It is how things work on Mac. They replaced the default compiler to clang/libc++ on Mac OS 10.9. And Mac OS 10.9 is the minimum requirement for cefpython/CEF/Chromium. The minimum supported version of gcc supported by Chromium is gcc 4.8+.
I hope this clears things up.
Cheers.
Download ClientLaunch for macOS 10.7 or later and enjoy it on your Mac. ā€ˇClientLaunch is launched automatically when it is needed. By clicking special ClientLaunch links, you launch common online files with your locally installed programs. MacOS automatically chooses the appropriate program for each file format (i.e., the default program). If anybody encounters error: configure.py: error: '/Users/xxx/Qt5.3.2/5.3.2/clang64/bin/qmake' is not an executable. S/he should change it to configure.py: error: '/Users/wangyu/Qt5.3.2/5.3/clang64/bin/qmake' is not an executable. Or any path qmake actually lives.
About the App
- App name: pyqt5
- App description: Python bindings for v5 of Qt
- App website: http://www.riverbankcomputing.co.uk/software/pyqt/download5
Install the App
Pyqt App Exec
- Press
Command+Space
and type Terminal and press enter/return key. - Run in Terminal app:
ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)' < /dev/null 2> /dev/null
and press enter/return key.
If the screen prompts you to enter a password, please enter your Mac's user password to continue. When you type the password, it won't be displayed on screen, but the system would accept it. So just type your password and press ENTER/RETURN key. Then wait for the command to finish. - Run:
brew install pyqt5
Install Pyqt4 Mac
Done! You can now use
pyqt5
.