From 39366c637e1fdb6ed466f6fef0131e40ab54b6b8 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Sat, 12 May 2018 10:22:16 +0200
Subject: Mention test, update, and clean commands in bdep(1)

---
 bdep/bdep.cli | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

(limited to 'bdep/bdep.cli')

diff --git a/bdep/bdep.cli b/bdep/bdep.cli
index 21b3c68..0d30561 100644
--- a/bdep/bdep.cli
+++ b/bdep/bdep.cli
@@ -230,6 +230,23 @@ namespace bdep
          $ ./hello  # run the result
          \
 
+         Using the build system directly on configurations other than the
+         default requires explicitly specifying their paths. To make this more
+         convenient, the \l{bdep-update(1)}, \l{bdep-test(1)}, and
+         \l{bdep-clean(1)} commands allow us to refer to them by names,
+         perform the desired build system operation on several of them at
+         once, and, in case of \cb{test}, perform it on immediate or all
+         dependencies or a project. For example:
+
+         \
+         $ bdep test @gcc @clang
+         in configuration @gcc:
+         <...>
+
+         in configuration @clang:
+         <...>
+         \
+
          |
 
      \li|\b{Add, Remove, or Change Dependencies}\n
-- 
cgit v1.1