Rooba
/
kivy
mirror of https://github.com/kivy/kivy.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: revisions to guide/packaging-ios-compile.rst

This commit is contained in:
Zen-CODE 2014-04-22 22:31:42 +02:00
parent 62c1f2f7da
commit 2dbb95dfc9
1 changed files with 20 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/sources/guide/packaging-ios-compile.rst
View File

@ -3,7 +3,7 @@
Compiling for IOS Compiling for IOS
================= =================
(work in progess - not referenced from external links) (work in progess)
Creating your distribution Creating your distribution
-------------------------- --------------------------
@ -53,12 +53,27 @@ of these other folders (*.cache*, *tmp* and *build*) and re-run the
Troubleshooting Troubleshooting
--------------- ---------------
The kivy-ios project is still a "work-in-progress" and uses many libraries which The kivy-ios project uses many libraries which
may change and break things independently of kivy. It may thus sometimes be may change and break things independently of kivy. It may thus sometimes be
necessary to remove any packages which do not compile in order to complete your necessary to remove any packages which do not compile in order to complete your
build. build or isolate the offending package.
# TODO: Add instructions on steps editing/isolating errors The 'build-all.sh' script assembles many sub-scripts into one, comprehensive
build script. If you open this file, you will see something similar to::
If you encounter an issue which you cannot resolve, remember you can always #!/bin/bash
. $(dirname $0)/environment.sh
try $(dirname $0)/build-libffi.sh
try $(dirname $0)/build-python.sh
try $(dirname $0)/reduce-python.sh
...
You can comment out problematic scripts using the hash (#) symbol. Some scripts
are essential (e.g. *build-python.sh*), but others can be safely removed if your
application does not require them.
We hope you never have to care about this, but if you encounter an error which
you cannot resolve, this may help. Remember, you can always
:ref:`contact us <contact>` for help. :ref:`contact us <contact>` for help.