aboutsummaryrefslogtreecommitdiff
path: root/doc/manual.cli
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual.cli')
-rw-r--r--doc/manual.cli26
1 files changed, 21 insertions, 5 deletions
diff --git a/doc/manual.cli b/doc/manual.cli
index 7835163..ec61e74 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -250,7 +250,22 @@ build configuration to use for building the package.
\li|\n\c{config: <config-vars>}\n
- Additional build system configuration variables.||
+ Additional build system configuration variables.
+
+ A single level of quotes (either single or double) is removed in each
+ variable before being passed to \c{bpkg}. For example, the following value:
+
+ \
+ config: config.cc.coptions=\"-O3 -stdlib='libc++'\"
+ \
+
+ Will be passed to \c{bpkg} as the following (single) argument:
+
+ \
+ config.cc.coptions=-O3 -stdlib='libc++'
+ \
+
+ ||
\h#arch-result-manifest|Result Manifest|
@@ -470,7 +485,7 @@ exec \"$2\" --build \"$3\" cc config.c=gcc-6
A \c{bbot} controller that issues own build tasks maps available build
machines (as reported by agents) to \i{build configurations} according to the
-\c{conftab} configuration file. Blank lines and lines that start with \c{#}
+\c{buildtab} configuration file. Blank lines and lines that start with \c{#}
are ignored. All other lines in this file have the following format:
\
@@ -479,9 +494,10 @@ are ignored. All other lines in this file have the following format:
Where \c{<machine-name-pattern>} is filesystem wildcard pattern that is
matched against available machine names, \c{<config-name>} is the
-configuration name, optional \c{<target>} is the build target, and
-optional \c{<config-vars>} is a list of additional build system configuration
-variables. The matched machine name, the target, and configuration variables
+configuration name, optional \c{<target>} is the build target, and optional
+\c{<config-vars>} is a list of additional build system configuration variables
+with the same quoting semantics as in the \c{config} value in the build task
+manifest. The matched machine name, the target, and configuration variables
are included into the build task manifest.
Note that each machine name is matched against every pattern and all the