From 46fdd9eb995af4f704b283f0e6ce2c54d2e43d5c Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 17 Aug 2016 14:40:59 +0200 Subject: If bpkg has exe.suffix, use it for the default build2 name So if bpkg is called bpkg-stage, then we by default look for b-stage. --- bpkg/common.cli | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'bpkg/common.cli') diff --git a/bpkg/common.cli b/bpkg/common.cli index 587d32d..577b449 100644 --- a/bpkg/common.cli +++ b/bpkg/common.cli @@ -75,14 +75,17 @@ namespace bpkg \li|Even more detailed information.||" } - path --build = "b" + path --build { "", "The build program to be used to build packages. This should be the path to the build2 \cb{b} executable. You can also specify additional options - that should be passed to the build program with \cb{--build-option}. If - the build program is not explicitly specified, then \cb{bpkg} will use - \cb{b} by default." + that should be passed to the build program with \cb{--build-option}. + + If the build program is not explicitly specified, then \cb{bpkg} will + by default use \cb{b} plus an executable suffix if one was specified + when building \cb{bpkg}. So, for example, if \cb{bpkg} name was set + to \cb{bpkg-1.0}, then it will look for \cb{b-1.0}." } strings --build-option -- cgit v1.1