aboutsummaryrefslogtreecommitdiff
path: root/libbuild2/build/script/parser+cleanup.test.testscript
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2020-07-10 09:51:54 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2020-07-10 11:07:49 +0200
commitddc5b76007bd4524f27a7449bcd4a5e21f8d797d (patch)
treeb806c70865171a1614bd6f5c8675b60d40d75fdd /libbuild2/build/script/parser+cleanup.test.testscript
parentb92a060879caf1de82a60ff2980f70ac165ec1a8 (diff)
Document ad hoc import and its usage in glue buildfiles
If the target being imported has no project name and is either absolute or is a relative directory, then this is treated as ad hoc importation. Semantically it is similar to a normal import but with the location of the project being imported hard-coded into the buildfile. This type of import can be used to create a special "glue buildfile" that "pulls" together several projects, usually for convenience of development. One typical case that calls for such a glue buildfile is a multi-package project. To be able to invoke the build system driver directly in the project root, we can add a glue buildfile that imports and builds all the packages: import pkgs = */ ./: $pkgs See "Target Importation" in the manual for details.
Diffstat (limited to 'libbuild2/build/script/parser+cleanup.test.testscript')
0 files changed, 0 insertions, 0 deletions