From f253fe820064310eee9aefc793328e84674d5c36 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Mon, 11 Jul 2022 14:46:08 +0300
Subject: Add support for build-file package manifest value

---
 doc/manual.cli | 22 ++++++++++++++++------
 1 file changed, 16 insertions(+), 6 deletions(-)

(limited to 'doc')

diff --git a/doc/manual.cli b/doc/manual.cli
index c85b483..0ef08cf 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -733,6 +733,8 @@ license: <licenses> [; <comment>]
 [build-include]: <config>[/<target>] [; <comment>]
 [build-exclude]: <config>[/<target>] [; <comment>]
 
+[build-file]: <path>
+
 [bootstrap-build]: <text>
 [root-build]: <text>
 [*-build]: <text>
@@ -1480,9 +1482,11 @@ Note that the comment of the matching exclusion is used by the web interface
 (\c{brep}) to display the reason for the build configuration exclusion.
 
 
-\h2#manifest-package-x-build|\c{{bootstrap,root,*\}-build[2]}|
+\h2#manifest-package-build-file|\c{build-file}|
 
 \
+[build-file]: <path>
+
 [bootstrap-build]: <text>
 [root-build]: <text>
 [*-build]: <text>
@@ -1499,24 +1503,30 @@ the alternative naming scheme should use the \c{*-build2} values instead of
 \c{*-build}.
 
 These files must reside in the package's \c{build/} subdirectory and have the
-\c{.build} extension (or their alternative names). The respective manifest
-value name prefix must be the file path relative to this subdirectory with the
-extension stripped.
+\c{.build} extension (or their alternative names). They can be provided either
+inline as text fragments or, for additional files, by referring to them with a
+path relative to this subdirectory, but not both. The \c{*-build}/\c{*-build2}
+manifest value name prefixes must be the file paths relative to this
+subdirectory with the extension stripped.
 
-As an example, the following value corresponds to the
+As an example, the following values correspond to the
 \c{build/config/common.build} file:
 
 \
+build-file: config/common.build
+
 config/common-build:
 \\
 config [bool] config.libhello.fancy ?= false
 \\
 \
 
-And the following value corresponds to the \c{build2/config/common.build2}
+And the following values correspond to the \c{build2/config/common.build2}
 file in a package with the alternative naming scheme:
 
 \
+build-file: config/common.build2
+
 config/common-build2:
 \\
 config [bool] config.libhello.fancy ?= false
-- 
cgit v1.1