Table Of Contents
Creating packages for MacOSX¶
Packaging your application for the MacOSX 10.6 platform can only be done inside MacOSX. The following method has only been tested inside VirtualBox and MacOSX 10.6, using the portable package of Kivy.
The package will only work for the 64 bit MacOSX. We no longer support 32 bit MacOSX platforms.
|NOTE: Currently, packages for OSX can only be generated with Python 2.7. Python 3.3+ support is on the way...|
Official Packaging method¶
Due to a lot of problems with including libraries and files on osx with other methods we now have a simpler and easier way to package Kivy apps on osx.
Since kivy 1.9 kivy package on osx is a self contained portable distribution. It is now possible to package kivy apps using the method described below to make it easier to include frameworks like sdl2 and gstreamer:
1: Make sure you have the Kivy.app(unmodified) from the download page. 2: run the following commands:
> mkdir packaging > cd packaging packaging> git clone https://github.com/kivy/kivy-sdk-packager packaging> cd kivy-sdk-packager/osx osx> cp -a /Applications/Kivy.app ./Kivy.App
This step above is important, you have to make sure to preserve the paths and permissions. A command like cp -rf will copy but make the app unusable and lead to error later on.
Now all you need to do is to include your compiled app into the Kivy.app, simply run the following command:
osx> ./package-app.sh path/to/your/app
This should copy Kivy.app to yourapp.app and include a compiled copy of your app into this package.
That’s it, your self contained package is ready to be deployed!
when you double click this app you can see your app run.
This is a pretty big sized app right now however you can simply remove the unneeded parts from this package.
For example if you don’t use Gstreamer, simply remove it from YourApp.app/Contents/Frameworks. Similarly you can remove the examples dir from /Applications/Kivy.app/Contents/Resources/kivy/examples/ or kivyt/tools, kivy/docs...
This way the whole app can be made to only include the parts that you use inside your app.
You can edit the icons and other settings of your app by editing the YourApp/Contents/info.plist to suit your needs, simply double click this file and make your changes.
Last step is to make a dmg of your app using the following command:
osx> create-osx-dmg.sh YourApp.app
This should give you a compressed dmg that will even further minimize the size of your distributed app.
Unofficial Method using Pyinstaller¶
- Latest Kivy (the whole portable package, not only the github sourcecode)
- PyInstaller 2.0
Please ensure that you have installed the Kivy DMG and installed the make-symlink script. The kivy command must be accessible from the command line.
Thereafter, download and decompress the PyInstaller 2.0 package.
Create the spec file¶
As an example, we’ll package the touchtracer demo, using a custom icon. The touchtracer code is in the ../kivy/examples/demo/touchtracer/ directory, and the main file is named main.py. Replace both path/filename according to your system.
Open a console.
Go to the pyinstaller directory, and create the initial specs:
cd pyinstaller-2.0 kivy pyinstaller.py --windowed --name touchtracer ../kivy/examples/demo/touchtracer/main.py
The specs file is named touchtracer/touchtracer.spec and located inside the pyinstaller directory. Now we need to edit the spec file to add kivy hooks to correctly build the executable. Open the spec file with your favorite editor and put theses lines at the start of the spec:
from kivy.tools.packaging.pyinstaller_hooks import install_hooks install_hooks(globals())
In the Analysis() method, remove the hookspath=None parameter. If you don’t do this, the kivy package hook will not be used at all.
Then, you need to change the COLLECT() call to add the data of touchtracer (touchtracer.kv, particle.png, ...). Change the line to add a Tree() object. This Tree will search and add every file found in the touchtracer directory to your final package.
You will need to specify to pyinstaller where to look for the frameworks included with kivy too, your COLLECT section should look something like this:
coll = COLLECT( exe, Tree('../kivy/examples/demo/touchtracer/'), Tree("../../../../../../Applications/Kivy.app/Contents/Frameworks/"), Tree("../../../../../Applications/Kivy.app/Contents/Frameworks/SDL2_ttf.framework/Versions/A/Frameworks/Freetype.Framework"), a.binaries, #... )
The Tree inclusion of frameworks is a work around a pyinstaller bug that is not able to find the exact path of libs including @executable_path.
There is a issue open on pyinstaller issue tracker for this. https://github.com/pyinstaller/pyinstaller/issues/1338
Make sure the path to the frameworks is relative to the current directory you are on.
- We are done. Your spec is ready to be executed!
Build the spec and create a DMG¶
Open a console.
Go to the pyinstaller directory, and build the spec:
cd pyinstaller-2.0 kivy pyinstaller.py touchtracer/touchtracer.spec
The package will be the touchtracer/dist/touchtracer directory. Rename it to .app:
pushd touchtracer/dist mv touchtracer touchtracer.app hdiutil create ./Touchtracer.dmg -srcfolder touchtracer.app -ov popd
You will now have a Touchtracer.dmg available in the touchtracer/dist directory.
If you want to read video files, audio, or camera, you will need to include gstreamer. By default, only pygst/gst files are discovered, but all the gst plugins and libraries are missing. You need to include them in your .spec file too, by adding one more arguments to the COLLECT() method:
import os gst_plugin_path = os.environ.get('GST_PLUGIN_PATH').split(':') coll = COLLECT( exe, Tree('../kivy/examples/demo/touchtracer/'), Tree(os.path.join(gst_plugin_path, '..')), a.binaries, #... )
For Kivy.app < 1.4.1, you also need to update one script included in our Kivy.app. Go to /Applications/Kivy.app/Contents/Resources/kivy/kivy/tools/packaging/pyinstaller_hooks/, and edit the file named rt-hook-kivy.py, and add this line at the end:
environ['GST_PLUGIN_PATH'] = join(root, '..', 'gst-plugins')