forked from Telodendria/Telodendria
Add a run recipe.
This commit is contained in:
parent
538412d1c2
commit
1d0fb32155
2 changed files with 15 additions and 0 deletions
|
@ -898,6 +898,13 @@ to <code>PROG</code>.</li>
|
|||
binary, but it is primarily used for generating releases.
|
||||
</li>
|
||||
<li>
|
||||
<code>run</code>: Run a built <b>Telodendria</b> binary with the
|
||||
development configuration in <code>contrib/</code>. This recipe can
|
||||
be used for quick testing during development. It is <i>not</i> the
|
||||
recommended way to run <b>Telodendria</b> in a production environment;
|
||||
it should be used only for development.
|
||||
</li>
|
||||
<li>
|
||||
<code>clean</code>: Remove the <code>build/</code> directory, which
|
||||
effectively cleans the source tree. Note that <code>build</code> does
|
||||
not place anything outside of <code>build/</code>, so this is
|
||||
|
|
|
@ -98,6 +98,14 @@ recipe_build() {
|
|||
fi
|
||||
}
|
||||
|
||||
recipe_run() {
|
||||
if [ -f "build/$PROG" ]; then
|
||||
"build/$PROG" -c contrib/development.conf
|
||||
else
|
||||
echo "build/$PROG does not exist; build it first."
|
||||
fi
|
||||
}
|
||||
|
||||
# Remove all build files, which can be regenerated by re-running the
|
||||
# build recipe.
|
||||
recipe_clean() {
|
||||
|
|
Loading…
Reference in a new issue