From cc7608840f0002bf929165cee4c74791261dc8c2 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Fri, 25 May 2018 21:34:14 +0300
Subject: Add config command tests

---
 bdep/config.cli | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

(limited to 'bdep/config.cli')

diff --git a/bdep/config.cli b/bdep/config.cli
index 8248510..44fcfd5 100644
--- a/bdep/config.cli
+++ b/bdep/config.cli
@@ -68,7 +68,15 @@ namespace bdep
          As a shortcut, if \ci{cfg-name} is not specified and \ci{cfg-dir} is
          a simple path that starts with \cb{@}, then it is treated as the name
          and the configuration directory is assumed to be
-         \c{\i{prj-dir}\b{-}\i{cfg-name}}.
+         \c{\i{prj-dir}\b{-}\i{cfg-name}}. Note that in case of \c{create},
+         \ci{cfg-dir} must be preceded with \cb{--} (double dash) option to
+         disambiguate it from \c{\b{@}\i{cfg-name}}. For example, assuming
+         the project directory is \cb{hello}:
+
+         \
+         $ bdep config add @clang                        # ../hello-clang
+         $ bdep config create -- @gcc cc config.cxx=g++  # ../hello-gcc
+         \
 
          Unless the \cb{--no-default} option is specified, the first added or
          created build configuration is designated as the default. Several
-- 
cgit v1.1