aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--bbot/worker/worker.cxx14
-rw-r--r--doc/manual.cli2
2 files changed, 13 insertions, 3 deletions
diff --git a/bbot/worker/worker.cxx b/bbot/worker/worker.cxx
index 8a5c8d7..025fa04 100644
--- a/bbot/worker/worker.cxx
+++ b/bbot/worker/worker.cxx
@@ -637,13 +637,23 @@ build (size_t argc, const char* argv[])
//
change_wd (trace, &r.log, rwd);
- // b create(<dir>) config.config.load=~host
+ // b create(<dir>) config.config.load=~build2
+ //
+ // Note also that we suppress warnings about unused config.* values,
+ // such CLI configuration.
+ //
+ // What if a module wants to use CLI? The current thinking is that we
+ // will be "whitelisting" base (i.e., those that can plausibly be used
+ // by multiple modules) libraries and tools for use by build system
+ // modules. So if and when we whitelist CLI, we will add it here, next
+ // to cc.
//
r.status |= run_b (
trace, r.log, wre,
"-V",
"create(" + module_dir.representation () + ",cc)",
- "config.config.load=~host");
+ "config.config.load=~build2",
+ "config.config.persist+='config.*'@unused=drop");
if (!r.status)
break;
diff --git a/doc/manual.cli b/doc/manual.cli
index 225065e..4191d6d 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -889,7 +889,7 @@ Such commands, therefore, have no associated \i{step id}:
\
#
#
-b -V create config.config.load=~host
+b -V create config.config.load=~build2
bpkg -v create --existing
# bpkg.configure.add