Developers
This section is for both people distributing software using Zero Install, and for people working on the Zero Install system itself.
- Packaging guide
- This guide takes you through the steps involved in making a package available through Zero Install. You will need to be able to upload (static) files to a web-server.
- Specifications
- Formal specifications for the file formats used by the injector.
- Python API
- The 0launch command-line interface to Zero Install is sufficient for most purposes. However, sometimes you may want to use the Python library interface. This is used by programs such as 0compile and 0publish, and is also a useful reference for people wanting to modify the injector itself.
- Using GIT
- How to get the very latest developer versions using GIT.
- Design
- A more detailed description of the design of Zero Install.
- Tests
- A set of test interfaces to check that the injector is working correctly.
Off-site documentation
- Compiling with SCons and GTK
-
Article showing how to use Zero Install in your build scripts to download the SCons build system and use it to compile your program.
- Easy GTK binary compatibility
-
This blog article shows how to use Zero Install to compile your program against older versions of library headers than are the default on your system. Binaries created this way work on a wider range of systems (all systems with a GTK version newer than the headers). Also, since they download the required headers automatically, users don't need to have the headers already on their system in order to compile your program.
The binaries produced this way do not depend on Zero Install, so you can use Zero Install as part of your build process even if you don't distribute the resulting binaries that way.
- brucalipto.org's packaging guide
-
Piero shows how to package software for Zero Install, using subversion as an example.
If you're looking for information about the old filesystem-based version of Zero Install, see The /uri/0install filesystem.
