diff options
| author | Christian Kandeler <christian.kandeler@theqtcompany.com> | 2016-06-15 12:34:55 +0200 |
|---|---|---|
| committer | Christian Kandeler <christian.kandeler@theqtcompany.com> | 2016-06-15 16:00:17 +0000 |
| commit | 5f5330af841f660eefc10f4dfb650fa8ca9b5147 (patch) | |
| tree | 39d5b04e546883605a193df4f60929bcf8937df7 /doc | |
| parent | cd0c1e9fd91359d54d5aaeee7c6093cf8620b45f (diff) | |
Cache the results of probes.
Probes are often used to call external processes, which can be
expensive. We do not want them to be executed every time a project is
re-resolved. So cache the results and provide the means to force re-
execution if something changes externally.
Task-number: QBS-25
Change-Id: I5c48a6f657f5829b72df7677b566177502655c5e
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/reference/items/probe.qdoc | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/reference/items/probe.qdoc b/doc/reference/items/probe.qdoc index a9e1cf4b7..7ec0e078b 100644 --- a/doc/reference/items/probe.qdoc +++ b/doc/reference/items/probe.qdoc @@ -40,6 +40,9 @@ A \c Probe item can appear inside a \l{Product Item} and is run prior to building products in order to locate dependent headers, libraries, and other files outside the project directory whose locations are not known ahead of time. \c Probes are similar to configure scripts. + \note Because Probes often invoke external processes, which is relatively expensive compared + to evaluating normal properties, their results are cached. To force re-evaluation + of a Probe, you can supply the \c{--force-probe-execution} command-line option. \section1 Probe Properties |