Line 28: |
Line 28: |
| * ''main'', for applications, path to exec file from service root directory | | * ''main'', for applications, path to exec file from service root directory |
| * ''gpg-key'', identify gpg key to sign feeds, useful if there are several keys to sign | | * ''gpg-key'', identify gpg key to sign feeds, useful if there are several keys to sign |
| + | * ''build-command'', for services that have compilation stage, command how to build binaries<br>Its value is a shell command, executed inside the build directory $BUILDDIR. It must compile the source in $SRCDIR, putting the final result (ready for distribution) in $DISTDIR. If this command starts to get complicated, you should move it to a script (either inside the main source archive or in a separate dependency) and just set this attribute to the command to run the script.<br>'''NOTE''': This command will be executed not only in service developer environment but also on user side if proper binary wasn't found, so do not use here any development related dependencies like ''autogen.sh''<br>For example, followed command builds regular autotools based project |
| + | "$SRCDIR"/configure --prefix="$DISTDIR" && make install |
| | | |
| To see the full explanation of configure files format(e.g. using configure filed values in other fields) in python, see [http://docs.python.org/library/configparser.html]. | | To see the full explanation of configure files format(e.g. using configure filed values in other fields) in python, see [http://docs.python.org/library/configparser.html]. |
Line 49: |
Line 51: |
| * ''push'', rsync dist/ to the server | | * ''push'', rsync dist/ to the server |
| * ''lint'', check feed file on the server<br>will run [http://0install.net/feedlint.html FeedLint] application for http://download.sugarlabs.org/services/ feed | | * ''lint'', check feed file on the server<br>will run [http://0install.net/feedlint.html FeedLint] application for http://download.sugarlabs.org/services/ feed |
− | * ''build-command'', for services that have compilation stage, command how to build binaries<br>Its value is a shell command, executed inside the build directory $BUILDDIR. It must compile the source in $SRCDIR, putting the final result (ready for distribution) in $DISTDIR. If this command starts to get complicated, you should move it to a script (either inside the main source archive or in a separate dependency) and just set this attribute to the command to run the script.<br>'''NOTE''': This command will be executed not only in service developer environment but also on user side if proper binary wasn't found, so do not use here any development related dependencies like ''autogen.sh''<br>For example, followed command builds regular autotools based project
| |
− | "$SRCDIR"/configure --prefix="$DISTDIR" && make install
| |
| | | |
| === Any arch services === | | === Any arch services === |