summaryrefslogtreecommitdiff
path: root/docs/markdown
diff options
context:
space:
mode:
authorXavier Claessens <xclaessens@netflix.com>2025-10-16 20:36:12 -0400
committerXavier Claessens <xclaesse@gmail.com>2025-10-17 16:15:14 -0400
commitd37d46d32e07e39bce31c84f7c5da7a5038a256e (patch)
tree1085d90b2e7c2febc17f85c74eab49f1a8541c75 /docs/markdown
parent624ddc9001c2c53109dbc67e9292fa467998b0d0 (diff)
downloadmeson-d37d46d32e07e39bce31c84f7c5da7a5038a256e.tar.gz
cargo: document that it is recommended to use workspaces
Diffstat (limited to 'docs/markdown')
-rw-r--r--docs/markdown/Wrap-dependency-system-manual.md5
-rw-r--r--docs/markdown/snippets/cargo-workspace.md5
2 files changed, 10 insertions, 0 deletions
diff --git a/docs/markdown/Wrap-dependency-system-manual.md b/docs/markdown/Wrap-dependency-system-manual.md
index 302546ebb..402dbe3e6 100644
--- a/docs/markdown/Wrap-dependency-system-manual.md
+++ b/docs/markdown/Wrap-dependency-system-manual.md
@@ -367,6 +367,11 @@ Since *1.5.0* Cargo wraps can also be provided with `Cargo.lock` file at the roo
of (sub)project source tree. Meson will automatically load that file and convert
it into a series of wraps definitions.
+Since *1.10.0* Workspace Cargo.toml are supported. For the time being it is
+recommended to regroup all Cargo dependencies inside a single workspace invoked
+from the main Meson project. When invoking multiple different Cargo subprojects
+from Meson, feature resolution of common dependencies might be wrong.
+
## Using wrapped projects
Wraps provide a convenient way of obtaining a project into your
diff --git a/docs/markdown/snippets/cargo-workspace.md b/docs/markdown/snippets/cargo-workspace.md
index 04bf5d555..0b373903d 100644
--- a/docs/markdown/snippets/cargo-workspace.md
+++ b/docs/markdown/snippets/cargo-workspace.md
@@ -3,3 +3,8 @@
When parsing `Cargo.toml` files, Meson now recognizes workspaces
and will process all the required members and any requested optional
members of the workspace.
+
+For the time being it is recommended to regroup all Cargo dependencies inside a
+single workspace invoked from the main Meson project. When invoking multiple
+different Cargo subprojects from Meson, feature resolution of common
+dependencies might be wrong.