Table of Contents
When building an app with
cx_Freeze on MacOSX all dependent libraries (
.so files on MacOSX) are packaged into the application bundle. It is this that makes the application portable to other systems, without requiring a second install of Qt.
When launching the Application, the libraries should therefore be loaded from within the bundle. However, in your case the system libraries are still being loaded:
One of the two will be used. Which one is undefined. means that either of these could be loaded. If it picks the correct one, great! If it doesn’t you’ve got two separate sets of libraries loading simultaneously, and that fails shortly afterwards. As an aside, you may find that if you try your Application on another system it will work fine! Sometimes.
For an overview of the problem I suggest taking a look at the following bug #33.
Before you begin
Make sure you have an up-to-date version of cx_Freeze installed. I would suggest trying to clone the repository and installing from there.
Secondly, ensure that the Qt plugins are being correctly built into your application. Cx_Freeze previously looked for the
qt-menu.nib file to determine if it was building a Qt application. This is no longer available in Qt5, but you can pass it on the command-line when building your app. Set it to whatever you want, it really doesn’t matter:
python setup.py bdist_mac --qt-menu-nib=/usr/local/Cellar/qt5/5.3.1/plugins/platforms/
This may be enough to fix your problem. But if not, you have two options:
Ready to build your own apps?
Create Simple GUI Applications with Python and Qt
The complete beginners guide to building cross-platform GUI applications with Python. Step by step from displaying your first window, to fully functional and useable software.
Join 300+ readers already using this book to build awesome things.
77 page ebook, 2.5 hours of video tutorials
Each library file contains the paths to it’s dependencies. If you’re receiving this error, it means some of those paths are either a) still pointing to the original file, or b) not specific enough (and being found on your
DYLD_LIBRARY_PATH). However, you can re-write paths using
install_name_tool from the command line (as described here:
install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtWidgets.framework/Versions/5/QtWidgets @executable_path/QtWidgets build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtCore.framework/Versions/5/QtCore @executable_path/QtCore build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtPrintSupport.framework/Versions/5/QtPrintSupport @executable_path/QtPrintSupport build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib install_name_tool -change /usr/local/Cellar/qt5/5.3.1/lib/QtGui.framework/Versions/5/QtGui @executable_path/QtGui build/MyApp.app/Contents/MacOS/qt_plugins/platforms/libqcocoa.dylib
This rewrites the paths in the libraries to point into your application folder, using
@executable_path as the base. You will need to do this for all the paths that you find loading incorrectly. I’d suggest wrapping it up into an script, to run automatically after the build.
If you want to look at which libraries a file is referencing you can use
otool. For example, in a successfully built application of mine:
otool -L libqcocoa.dylib libqcocoa.dylib: @executable_path/../Resources/qt_plugins/platforms/libqcocoa.dylib (compatibility version 0.0.0, current version 0.0.0) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 20.0.0) ...
There was an updated workaround in the issue tracker that suggests that just importing the correct module in your app will get it to function, however it seems unlikely that you’ve made an application without
If the above doesn’t work, there is another approach outlined here. This is a bit of a sledgehammer approach in that it simply prevents loading of plugins at all.
qt.conffile next to the executable (in the
.appbundle that contains:
[Paths] Plugins = '.'
Either set the environment variable
QT_PLUGIN_PATH=""(you can do this within your application before importing
PyQt. Or call
QtGui.QApplication.setLibraryPaths()before creating your application object.
The result is no plugins, so your application will not have access to the MacOSX Cocoa style and UI (e.g. file, colour dialogs).
Get regular FAQs tips & tutorials direct to your Inbox.