aboutsummaryrefslogtreecommitdiff
path: root/bdep/projects-configs.cli
diff options
context:
space:
mode:
Diffstat (limited to 'bdep/projects-configs.cli')
-rw-r--r--bdep/projects-configs.cli11
1 files changed, 6 insertions, 5 deletions
diff --git a/bdep/projects-configs.cli b/bdep/projects-configs.cli
index 72b9736..a5c5808 100644
--- a/bdep/projects-configs.cli
+++ b/bdep/projects-configs.cli
@@ -58,11 +58,12 @@ include <bdep/common-options.hxx>;
\cb{packages.manifest}).
A project managed by \cb{bdep} has one or more associated build
- configurations (see \l{bdep-config(1)} for details). One of these
- configurations can be designated as the default and used if no configuration
- is specified explicitly. So, for example, running \cb{status} without any
- arguments in the project directory will show the status of all the project
- packages initialized in the default configuration.
+ configurations (see \l{bdep-config(1)} for details). Some of these
+ configurations, one per the configuration type, can be designated as default
+ and used if no configuration is specified explicitly. So, for example,
+ running \cb{status} without any arguments in the project directory will show
+ the status of all the project packages initialized in the default
+ configurations.
An associated build configuration can be assigned a name in which case we
can specify it using the \c{\b{@}\i{cfg-name}} notation. For example: