// file : bdep/init.cli // copyright : Copyright (c) 2014-2017 Code Synthesis Ltd // license : MIT; see accompanying LICENSE file include ; "\section=1" "\name=bdep-init" "\summary=initialize project dependency management" namespace bdep { { " ", "\h|SYNOPSIS| \c{\b{bdep init} [] [] [] []\n \b{bdep init} [] [] \b{--empty|-E}\n \b{bdep init} [] [] \b{--config-add|-A} [\b{@}]\n \b{bdep init} [] [] \b{--config-create|-C} [\b{@}] \\\n \ \ \ \ \ \ \ \ \ \ []} \c{ = \b{--directory}|\b{-d} \n = (\b{--directory}|\b{-d} )... | \n = (\b{@} | \b{--config}|\b{-c} )... | \b{--all}|\b{-a}\n = ( | )...\n = ( | )...} \h|DESCRIPTION| The \cb{init} command... If is omitted, then the default configuration is assumed. If is omitted, then the current working directory is assumed. In this case the current directory must be either a project directory (), a package directory () or a subdirectory of package directory. are arguments to \cb{bpkg cfg-create}. are arguments to \cb{bpkg pkg-build}. In the first variant the configurations can also be specified as directories using the \cb{--config|-c} option. The second and third variants are semantically equivalent to first performing \cb{config add} and \cb{config create} (\l{bdep-config(1)}), respectively, followed by the first variant. In both cases the \cb{--default|-d} option can be used to make the added/created configuration default. " } class cmd_init_options: configuration_options { "\h|INIT OPTIONS|" }; }