From 023f1a286b7dfe80eb80a9e6924e492cf6f3f80a Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Thu, 10 May 2018 10:34:31 +0200 Subject: Implement test, update, and clean commands --- bdep/update.cli | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 bdep/update.cli (limited to 'bdep/update.cli') diff --git a/bdep/update.cli b/bdep/update.cli new file mode 100644 index 0000000..e78dab4 --- /dev/null +++ b/bdep/update.cli @@ -0,0 +1,49 @@ +// file : bdep/update.cli +// copyright : Copyright (c) 2014-2017 Code Synthesis Ltd +// license : MIT; see accompanying LICENSE file + +include ; + +"\section=1" +"\name=bdep-update" +"\summary=update project in build configurations" + +namespace bdep +{ + { + " + + + + ", + + "\h|SYNOPSIS| + + \c{\b{bdep update} [] [] [] [...]} + + \c{ = (\b{@} | \b{--config}|\b{-c} )... | \b{--all}|\b{-a}\n + = (\b{--directory}|\b{-d} )... | \n + = \b{--directory}|\b{-d} } + + \h|DESCRIPTION| + + The \cb{update} command updates the project packages in one or more build + configurations. Underneath it executes the \l{bpkg-pkg-update(1)} command + which itself is not much more than the build system \cb{update} operation + (see \l{b(1)} for details). As a result, the main utility of this command + is the ability to refer to build configurations by names and to project + packages implicitly via the current working directory. + + If no project or package directory is specified, then the current working + directory is assumed. If no configuration is specified, then the default + configuration is assumed. See \l{bdep-projects-configs(1)} for details on + specifying projects and configurations. Optional \c{\i{cfg-var}...} are + the additional configuration variables to pass to the build system. + " + } + + class cmd_update_options: project_options + { + "\h|UPDATE OPTIONS|" + }; +} -- cgit v1.1