diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/markdown/IDE-integration.md | 6 | ||||
| -rw-r--r-- | docs/markdown/Reference-manual.md | 44 | ||||
| -rw-r--r-- | docs/markdown/snippets/introspect_test_deps.md | 5 |
3 files changed, 33 insertions, 22 deletions
diff --git a/docs/markdown/IDE-integration.md b/docs/markdown/IDE-integration.md index 816225f..5188359 100644 --- a/docs/markdown/IDE-integration.md +++ b/docs/markdown/IDE-integration.md @@ -247,6 +247,7 @@ line arguments, environment variable settings and how to process the output. "is_parallel": true / false, "protocol": "exitcode" / "tap", "cmd": ["command", "to", "run"], + "depends": ["target1-id", "target2-id"], "env": { "VARIABLE1": "value 1", "VARIABLE2": "value 2" @@ -254,6 +255,11 @@ line arguments, environment variable settings and how to process the output. } ``` +The `depends` entry *(since 0.56.0)* contains target ids; they can be +looked up in the targets introspection data. The executable +pointed to by `cmd` is also included in the entry, as are any +arguments to the test that are build products. + ## Build system files It is also possible to get Meson build files used in your current project. This diff --git a/docs/markdown/Reference-manual.md b/docs/markdown/Reference-manual.md index a860f85..fafc9cb 100644 --- a/docs/markdown/Reference-manual.md +++ b/docs/markdown/Reference-manual.md @@ -1776,7 +1776,7 @@ the following methods. `MESONINTROSPECT` contains the path to the introspect command that corresponds to the `meson` executable that was used to configure the - build. (This might be a different path then the first executable + build. (This might be a different path than the first executable found in `PATH`.) It can be used to query build configuration. Note that the value will contain many parts, f.ex., it may be `python3 /path/to/meson.py introspect`. The user is responsible for splitting @@ -2155,27 +2155,27 @@ the following methods: `args` keyword, you can specify external dependencies to use with `dependencies` keyword argument. -- `check_header` *(since 0.47.0)*: returns true if the specified header is *usable* with - the specified prefix, dependencies, and arguments. - You can specify external dependencies to use with `dependencies` - keyword argument and extra code to put above the header test with - the `prefix` keyword. In order to look for headers in a specific - directory you can use `args : '-I/extra/include/dir`, but this - should only be used in exceptional cases for includes that can't be - detected via pkg-config and passed via `dependencies`. *(since 0.50.0)* The - `required` keyword argument can be used to abort if the header cannot be - found. - -- `has_header`: returns true if the specified header *exists*, and is - faster than `check_header()` since it only does a pre-processor check. - You can specify external dependencies to use with `dependencies` - keyword argument and extra code to put above the header test with - the `prefix` keyword. In order to look for headers in a specific - directory you can use `args : '-I/extra/include/dir`, but this - should only be used in exceptional cases for includes that can't be - detected via pkg-config and passed via `dependencies`. *(since 0.50.0)* The - `required` keyword argument can be used to abort if the header cannot be - found. +- `check_header(header_name)` *(since 0.47.0)*: returns true if the + specified header is *usable* with the specified prefix, + dependencies, and arguments. You can specify external dependencies + to use with `dependencies` keyword argument and extra code to put + above the header test with the `prefix` keyword. In order to look + for headers in a specific directory you can use `args : + '-I/extra/include/dir`, but this should only be used in exceptional + cases for includes that can't be detected via pkg-config and passed + via `dependencies`. *(since 0.50.0)* The `required` keyword argument + can be used to abort if the header cannot be found. + +- `has_header(header_name)`: returns true if the specified header + *exists*, and is faster than `check_header()` since it only does a + pre-processor check. You can specify external dependencies to use + with `dependencies` keyword argument and extra code to put above the + header test with the `prefix` keyword. In order to look for headers + in a specific directory you can use `args : '-I/extra/include/dir`, + but this should only be used in exceptional cases for includes that + can't be detected via pkg-config and passed via `dependencies`. + *(since 0.50.0)* The `required` keyword argument can be used to + abort if the header cannot be found. - `has_header_symbol(headername, symbolname)`: detects whether a particular symbol (function, variable, #define, type diff --git a/docs/markdown/snippets/introspect_test_deps.md b/docs/markdown/snippets/introspect_test_deps.md new file mode 100644 index 0000000..a29ea09 --- /dev/null +++ b/docs/markdown/snippets/introspect_test_deps.md @@ -0,0 +1,5 @@ +## Dependencies listed in test and benchmark introspection + +The introspection data for tests and benchmarks now includes the target +ids for executables and built files that are needed by the test. IDEs can +use this feature to update the build more quickly before running a test. |