From d37d46d32e07e39bce31c84f7c5da7a5038a256e Mon Sep 17 00:00:00 2001 From: Xavier Claessens Date: Thu, 16 Oct 2025 20:36:12 -0400 Subject: cargo: document that it is recommended to use workspaces --- docs/markdown/Wrap-dependency-system-manual.md | 5 +++++ docs/markdown/snippets/cargo-workspace.md | 5 +++++ 2 files changed, 10 insertions(+) (limited to 'docs') 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. -- cgit v1.2.3