Toolchain for compiling Python / Kivy / other libraries for iOS
92f38fe2d7
Now all the cythonized modules are rewrite with a mangled name of package + module name. This avoid symbol conflict if you have the same module.so as another library (for example, audiostream.sources.thread and python thread.so was in conflict). Then, a custom builtin importer is loaded before the application start, and when you will want to import audiostream.sources.thread, if will import builtin audiostream_sources_thread. kivy/ios/lxml/audiostream recipes are impacted. A full rebuild is needed. |
||
|---|---|---|
| src | ||
| tools | ||
| .gitignore | ||
| README.rst | ||
Kivy for IOS
============
(This is a work in progress.)
#. Using brew, you can install dependencies::
brew install autoconf automake libtool pkg-config mercurial
brew link libtool
brew link mercurial
#. Install Cython::
# easy-install method
sudo easy_install cython
# pip method if available (sudo might be needed.)
pip install cython
#. Build the whole toolchain with `tools/build_all.sh`
#. Create an Xcode project for your application with `tools/create-xcode-project.sh test /path/to/app`
#. Open your newly created Xcode project
#. Ensure code signing is setup correctly
#. Click on play
Notes
-----
A build phase is added to the project that processes and moves your
app's files to the Xcode project before every build. If you would like
to handle this process manually, remove the "Run Script" build phase
from your target and use `tools/populate-project.sh /path/to/app`
after every change. You can also change the path to your app by modifying this build phase.