1 .TH 0COMPILE 1 "2009" "Thomas Leonard" ""
3 0compile \- create a Zero Install binary package from source
7 .B 0compile autocompile SOURCE-URI
10 [\fB--no-prompt\fP] [\fBSOURCE-URI\fP [\fBDIR\fP] ]
13 [\fB --nosandbox\fP ] [\fB--shell\fP]
16 [\fBDOWNLOAD-BASE-URL\fP]
25 [\fB--no-prompt\fP] [\fBSOURCE-URI\fP]
27 .B 0compile include-deps
29 .B 0compile report-bug
33 0compile can be used to compile a Zero Install package from its source code.
38 Download and build the source code for the given program. Also download and build
39 any missing dependencies, recursively. The resulting binaries will be placed in the
40 Zero Install implementation cache (just like normal binary downloads). A feed file
41 describing each new binary is created under $XDG_CONFIG_DIRS/0install.net/0compile/builds/
42 and registered with Zero Install (using "0launch --feed").
45 On error, 0compile will display the name of the temporary directory in which it was
46 compiling the component which failed. You can cd to this directory and fix the problem
47 using the other 0compile commands.
52 To set up a build environment for the GNU Hello World example:
54 .B 0compile setup http://0install.net/tests/GNU-Hello.xml GNU-Hello
57 This downloads the source and any build dependencies into the Zero Install
58 cache, and creates a new directory called GNU-Hello.
61 If the name is "." then it uses the current directory instead of creating a new one.
66 To compile the code, cd to the directory created by "setup" above, and then:
71 The resulting package will be in a new gnu-hello-1.3 subdirectory (or whatever version you downloaded).
72 Temporary build files will be in a new "build" subdirectory. These are kept to make rebuilds faster, but
73 you can delete them if you don't plan to recompile.
78 To create an archive that other people can download:
80 .B 0compile publish http://mysite/downloads
82 The will archive the target directory. Upload the resulting tarball to the downloads directory on your web-server.
83 The command will also create an XML file which can be used to download and run this version.
87 Deletes the 'build' and distribution directories, if present.
92 To make changes to the code before compiling:
96 This copies the source code from the cache into a new "src" subdirectory. Edit to taste and then "build".
100 To see the differences between the original (cached) source code and the copy in your "src" directory:
106 To create a self-contained bundle with the source code and build dependencies:
108 .B 0compile include-deps
110 This copies all required items from the Zero Install cache to a new "dependencies" subdirectory. The whole
111 directory tree (including the "dependencies" subdirectory) can then be copied to the build machine. This is
112 useful if the build machine doesn't have network access, and so can't download them itself.
115 Note that this doesn't include the 0compile program itself.
119 To bring up the GTK interface, which offers an newbie-friendly interface to some of the features above:
125 To send a bug-report about a failed build:
127 .B 0compile report-bug
130 .SH COMMAND-LINE OPTIONS
133 \fB-h\fP, \fB--help\fP
134 Show the built-in help text.
137 \fB-v\fP, \fB--verbose\fP
138 More verbose output. Use twice for even more verbose output.
141 \fB-V\fP, \fB--version\fP
142 Display version information.
146 Copyright (C) 2007 Thomas Leonard.
149 You may redistribute copies of this program under the terms of the GNU General Public License.
152 Please report bugs to the developer mailing list:
154 http://0install.net/support.html
158 The Zero Install Injector was created by Thomas Leonard.
161 0launch(1), 0store(1)
163 The Zero Install web-site:
165 .B http://0install.net/0compile.html