From d2c6ab2c77690203674ee3a7ec21eec836e9ab87 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 24 Mar 2023 07:46:05 +0200 Subject: Document relocatable installation support --- libbuild2/install/functions.cxx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'libbuild2/install') 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) -- cgit v1.1