summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/reference/items/language/moduleprovider.qdoc2
-rw-r--r--doc/reference/items/language/probe.qdoc2
2 files changed, 3 insertions, 1 deletions
diff --git a/doc/reference/items/language/moduleprovider.qdoc b/doc/reference/items/language/moduleprovider.qdoc
index ac3b4f0bf..81a09a66b 100644
--- a/doc/reference/items/language/moduleprovider.qdoc
+++ b/doc/reference/items/language/moduleprovider.qdoc
@@ -40,6 +40,8 @@
The actual module creation is done on the right-hand side of the
\l{ModuleProvider::relativeSearchPaths}{relativeSearchPaths} property.
+ A ModuleProvider item may contain \l{Probe} items.
+
Here is a complete minimal example of a module provider. It just creates an empty module.
If you put this item into the file \c {module-providers/mymodule/provider.qbs}
in your project source directory, you will be able to successfully build a product which
diff --git a/doc/reference/items/language/probe.qdoc b/doc/reference/items/language/probe.qdoc
index f0deb4c75..8e31d8827 100644
--- a/doc/reference/items/language/probe.qdoc
+++ b/doc/reference/items/language/probe.qdoc
@@ -35,7 +35,7 @@
\brief Locates files outside the project.
- Probe items can appear inside \l{Product} and \l{Project} items.
+ Probe items can appear inside \l{Product}, \l{Project} and \l{ModuleProvider} items.
They are run prior to building, for instance to locate dependent headers, libraries, and other
files outside the project directory whose locations are not known ahead of time.
Probes can be parameterized via their properties and typically store results in