aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/install
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2023-03-24 07:46:05 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2023-03-24 07:46:05 +0200
commitd2c6ab2c77690203674ee3a7ec21eec836e9ab87 (patch)
tree864d175b2028d6e2554d87975386ef48015fe701 /libbuild2/install
parent750b20e01169c15f39fb8d7af49af34d96c677ae (diff)
Document relocatable installation support
Diffstat (limited to 'libbuild2/install')
-rw-r--r--libbuild2/install/functions.cxx10
1 files changed, 5 insertions, 5 deletions
diff --git a/libbuild2/install/functions.cxx b/libbuild2/install/functions.cxx
index 8d1a1f3..9f5fa44 100644
--- a/libbuild2/install/functions.cxx
+++ b/libbuild2/install/functions.cxx
@@ -31,11 +31,11 @@ namespace build2
//
// As an example, consider an executable that supports loading plugins
// and requires the plugin installation directory to be embedded into
- // the executable during build. The common way to support relocatable
- // installations for such cases is to embed a path relative to the
- // executable and complete it at runtime. If you would like to always
- // use the relative path, regardless of whether the installation is
- // relocatable of not, then you can simply always pass rel_base, for
+ // the executable during the build. The common way to support
+ // relocatable installations for such cases is to embed a path relative
+ // to the executable and complete it at runtime. If you would like to
+ // always use the relative path, regardless of whether the installation
+ // is relocatable of not, then you can simply always pass rel_base, for
// example:
//
// plugin_dir = $install.resolve($install.lib, $install.bin)