diff options
Diffstat (limited to 'bdep/ci.cli')
| -rw-r--r-- | bdep/ci.cli | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/bdep/ci.cli b/bdep/ci.cli index 832f01a..c3f8825 100644 --- a/bdep/ci.cli +++ b/bdep/ci.cli @@ -65,9 +65,16 @@ namespace bdep \ $ bdep ci --builds gcc + $ bdep ci --builds network/gcc $ bdep ci --target-config 'linux*-gcc*' $ bdep ci --package-config network $ bdep ci --build-config 'network/linux*-gcc*' + + $ bdep ci --override \ + 'default-build-config: config.foo.cache=true config.foo.buffer=16' + + $ bdep ci --override 'mytest-build-config: config.foo.cache=true' \ + --package-config mytest \ Manifest overrides override the entire value group that they belong @@ -79,8 +86,17 @@ namespace bdep build-email build-{warning,error}-email builds build-{include,exclude} *-builds *-build-{include,exclude} + *-build-config \ + For the package configuration-specific build constraint overrides the + corresponding configuration must exist in the package manifest. In + contrast, the package configuration override (\cb{*-build-config}) adds a + new configuration if it doesn't exist and updates the arguments of the + existing configuration otherwise. In the former case, all the potential + build constraint overrides for such a newly added configuration must + follow the corresponding \cb{*-build-config} override. + Note that the build constraints group values (both common and build package configuration-specific) are overridden hierarchically so that the \c{[\b{*-}]\b{build-}{\b{include},\b{exclude}\}} overrides don't affect |