buildozer/README.rst

111 lines
3.3 KiB
ReStructuredText
Raw Normal View History

2012-12-19 02:34:32 +01:00
Buildozer
=========
2013-03-16 02:31:39 +01:00
This tool is currently in alpha.
2012-12-19 02:34:32 +01:00
2012-12-20 01:02:57 +01:00
Buildozer is a tool for creating application packages easily.
2012-12-19 02:34:32 +01:00
2014-01-13 20:05:00 +01:00
The goal is to have one "buildozer.spec" file in your app directory, describing
your application requirements and settings such as title, icon, included modules
etc. Buildozer will use that spec to create a package for Android, iOS, Windows,
OSX and/or Linux.
Buildozer currently supports packaging for Android via the `python-for-android
<http://github.com/kivy/python-for-android/>`_
2014-01-13 20:05:00 +01:00
project, and for iOS via the kivy-ios project. Support for other operating systems
is intended in the future.
2012-12-19 02:34:32 +01:00
2014-10-27 11:50:28 +01:00
Note that this tool has nothing to do with the eponymous online build service
2014-10-27 11:51:30 +01:00
`buildozer.io <http://buildozer.io />`_.
2014-10-27 11:50:28 +01:00
Usage example
-------------
2012-12-19 02:34:32 +01:00
#. Install buildozer::
# latest dev
git clone https://github.com/kivy/buildozer
cd buildozer
sudo python2.7 setup.py install
# via pip (latest stable)
sudo pip install buildozer
# via easy_install
sudo easy_install buildozer
2012-12-19 02:34:32 +01:00
#. Go into your application directory and do::
buildozer init
# edit the buildozer.spec, then
2012-12-20 01:04:39 +01:00
buildozer android debug deploy run
Example of commands::
# buildozer commands
buildozer clean
# buildozer target command
buildozer android update
2012-12-20 01:04:39 +01:00
buildozer android deploy
buildozer android debug
buildozer android release
2012-12-20 01:04:39 +01:00
# or all in one (compile in debug, deploy on device)
buildozer android debug deploy
# set the default command if nothing set
2012-12-20 01:04:39 +01:00
buildozer setdefault android debug deploy run
Usage
-----
::
Usage: buildozer [--verbose] [target] [command1] [command2]
Available targets:
2012-12-20 01:01:19 +01:00
android Android target, based on python-for-android project
ios iOS target, based on kivy-ios project. (not working yet.)
Global commands (without target):
2012-12-20 01:01:19 +01:00
clean Clean the whole Buildozer environment.
help Show the Buildozer help.
init Create a initial buildozer.spec in the current directory
2013-09-23 12:17:47 +02:00
setdefault Set the default command to do when no arguments are given
2012-12-20 01:01:19 +01:00
version Show the Buildozer version
Target commands:
2012-12-20 01:01:19 +01:00
clean Clean the target environment
update Update the target dependencies
debug Build the application in debug mode
release Build the application in release mode
deploy Deploy the application on the device
run Run the application on the device
2012-12-19 02:34:32 +01:00
buildozer.spec
--------------
2012-12-20 00:48:24 +01:00
See `buildozer/default.spec <https://raw.github.com/kivy/buildozer/master/buildozer/default.spec>`_ for an up-to-date spec file.
Default config
--------------
You can override the value of *any* buildozer.spec config token by
setting an appropriate environment variable. These are all of the
form ``$SECTION_TOKEN``, where SECTION is the config file section and
TOKEN is the config token to override. Dots are replaced by
underscores.
For example, here are some config tokens from the [app] section of the
config, along with the environment variables that would override them.
- ``title`` -> ``$APP_TITLE``
- ``package.name`` -> ``$APP_PACKAGE_NAME``
- ``android.p4a_dir`` -> ``$APP_ANDROID_P4A_DIR``