summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorHelmut Grohne <helmut@subdivi.de>2021-05-09 07:50:18 +0200
committerHelmut Grohne <helmut@subdivi.de>2021-05-09 07:50:18 +0200
commit15fa5e5b555fdc1aad10f51822de877cde71294d (patch)
tree6c072ade8fda146e32503fc4afc0414c8263e822 /README.md
parentbf30d5dd03503f776127c42d3f1d8b2ea529b150 (diff)
downloadmdbp-15fa5e5b555fdc1aad10f51822de877cde71294d.tar.gz
the stdout fd contains the build log
Using a pipe enables streaming of logs, which would not be possible with a regular file output.
Diffstat (limited to 'README.md')
-rw-r--r--README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.md b/README.md
index 603d157..66b9fa7 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,8 @@ The output directory `out` is supposed to be an empty directory. Then run one
of the backends `mdbp-BACKEND [BACKENDOPTIONS] REQUEST.json`. The process
blocks until the build has finished and its return code signifies success or
failure of the operation. Usage of unsupported parameters of the particular
-backend result in a failure of the operation as a whole.
+backend result in a failure of the operation as a whole. The content of the
+stdout file descriptor is to be considered the build log.
When to use mdbp?
-----------------