aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/snippets/implicit_fallback.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/markdown/snippets/implicit_fallback.md')
-rw-r--r--docs/markdown/snippets/implicit_fallback.md21
1 files changed, 0 insertions, 21 deletions
diff --git a/docs/markdown/snippets/implicit_fallback.md b/docs/markdown/snippets/implicit_fallback.md
deleted file mode 100644
index a6cbaf0..0000000
--- a/docs/markdown/snippets/implicit_fallback.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## Implicit dependency fallback
-
-`dependency('foo')` now automatically fallback if the dependency is not found on
-the system but a subproject wrap file or directory exists with the same name.
-
-That means that simply adding `subprojects/foo.wrap` is enough to add fallback
-to any `dependency('foo')` call. It is however requires that the subproject call
-`meson.override_dependency('foo', foo_dep)` to specify which dependency object
-should be used for `foo`.
-
-## Wrap file `provide` section
-
-Wrap files can define the dependencies it provides in the `[provide]` section.
-When `foo.wrap` provides the dependency `foo-1.0` any call do `dependency('foo-1.0')`
-will automatically fallback to that subproject even if no `fallback` keyword
-argument is given. See [Wrap documentation](Wrap-dependency-system-manual.md#provide_section).
-
-## `find_program()` fallback
-
-When a program cannot be found on the system but a wrap file has its name in the
-`[provide]` section, that subproject will be used as fallback.