From 07ab59a93f9447d5489743e8d7e19b6adb5ebbf1 Mon Sep 17 00:00:00 2001 From: Karen Arutyunov Date: Fri, 9 Jul 2021 20:55:15 +0300 Subject: Add support for configuration type and bdep-config-link sub-command --- bdep/projects-configs.cli | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'bdep/projects-configs.cli') 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 ; \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: -- cgit v1.1