From ccab7d64f474f00e010b2c6601e63d8034c5552a Mon Sep 17 00:00:00 2001 From: Alberto Aguirre Date: Fri, 14 Apr 2017 08:18:37 -0500 Subject: Add support for @CURRENT_SOURCE_DIR@ in generator arguments Allow users to specify @CURRENT_SOURCE_DIR@ in generator arguments to specify the current target source directory. This is useful when creating protobuf generator objects in sub-directories because protoc will then generate files in the expected location. Fixes #1622. Remove stray semicolon Update documentation --- docs/markdown/Reference-manual.md | 1 + 1 file changed, 1 insertion(+) (limited to 'docs/markdown') diff --git a/docs/markdown/Reference-manual.md b/docs/markdown/Reference-manual.md index b46f907..276c9c9 100644 --- a/docs/markdown/Reference-manual.md +++ b/docs/markdown/Reference-manual.md @@ -318,6 +318,7 @@ In addition to the above substitutions, the `arguments` keyword argument also ac - `@OUTPUT@`: the full path to the output file - `@INPUT@`: the full path to the input file - `@SOURCE_DIR@`: the full path to the root of the source tree +- `@CURRENT_SOURCE_DIR@`: this is the directory where the currently processed meson.build is located in - `@BUILD_DIR@`: the full path to the root of the build dir where the output will be placed NOTE: Generators should only be used for outputs that will ***only*** be used as inputs for a [build target](#build_target) or a [custom target](#custom_target). When you use the processed output of a generator in multiple targets, the generator will be run multiple times to create outputs for each target. Each output will be created in a target-private directory `@BUILD_DIR@`. -- cgit v1.1