Update

Author: github-actions

Release-notes-for-1-10-0.html

@@ -243,6 +243,10 @@ <h2 id="support-for-cargo-workspaces">Support for Cargo workspaces</h2>
 <p>When parsing <code>Cargo.toml</code> files, Meson now recognizes workspaces
 and will process all the required members and any requested optional
 members of the workspace.</p>
+<p>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.</p>
 <h2 id="methods-from-compiler-object-now-accept-strings-for-include_directories">Methods from compiler object now accept strings for include_directories</h2>
 <p>The various <a href="Reference-manual_returned_compiler.html"><ins><code>compiler</code></ins></a> methods with a <code>include_directories</code> keyword argument
 now accept stings or array of strings, in addition to <a href="Reference-manual_returned_inc.html"><ins><code>inc</code></ins></a> objects

Wrap-dependency-system-manual.html

@@ -556,10 +556,16 @@ <h3 id="cargo-wraps">Cargo wraps</h3>
 This is typically used as <code>extra_args += ['--cfg', 'foo']</code>.</li>
 <li>The <code>extra_deps</code> variable is pre-defined and can be used to add extra dependencies.
 This is typically used as <code>extra_deps += dependency('foo')</code>.</li>
+<li>The <code>features</code> variable is pre-defined and contains the list of features enabled
+on this crate.</li>
 </ul>
 <p>Since <em>1.5.0</em> Cargo wraps can also be provided with <code>Cargo.lock</code> file at the root
 of (sub)project source tree. Meson will automatically load that file and convert
 it into a series of wraps definitions.</p>
+<p>Since <em>1.10.0</em> 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.</p>
 <h2 id="using-wrapped-projects">Using wrapped projects</h2>
 <p>Wraps provide a convenient way of obtaining a project into your
 subproject directory. Then you use it as a regular subproject (see

Wrapdb-projects.html

@@ -627,7 +627,7 @@ <h1 id="meson-wrapdb-packages">Meson WrapDB packages</h1>
 </tr>
 <tr>
 <td> eigen</td>
-<td> <big><strong><a href="https://wrapdb.mesonbuild.com/v2/eigen_3.4.0-2/eigen.wrap">3.4.0-2</a></strong></big><br><a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.9-1/eigen.wrap">3.3.9-1</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.8-1/eigen.wrap">3.3.8-1</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.7-3/eigen.wrap">3.3.7-3</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.5-1/eigen.wrap">3.3.5-1</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.4-1/eigen.wrap">3.3.4-1</a>
+<td> <big><strong><a href="https://wrapdb.mesonbuild.com/v2/eigen_5.0.0-1/eigen.wrap">5.0.0-1</a></strong></big><br><a href="https://wrapdb.mesonbuild.com/v2/eigen_3.4.0-2/eigen.wrap">3.4.0-2</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.9-1/eigen.wrap">3.3.9-1</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.8-1/eigen.wrap">3.3.8-1</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.7-3/eigen.wrap">3.3.7-3</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.5-1/eigen.wrap">3.3.5-1</a>, <a href="https://wrapdb.mesonbuild.com/v2/eigen_3.3.4-1/eigen.wrap">3.3.4-1</a>
 </td>
 <td> eigen3</td>
 <td></td>

assets/js/search/Workspace

@@ -0,0 +1 @@
+urls_downloaded_cb({"token":"Workspace","urls":[{"url":"Wrap-dependency-system-manual.html#cargo-wraps","node_type":"p","page":"Wrap dependency system manual","sections":["Wrap dependency system manual","\nprovide section","Cargo wraps"],"context":{"gi-language":["default"]}}]});

assets/js/search/common

@@ -1 +1 @@
-fragment_downloaded_cb({"url":"Release-notes-for-1-10-0.html#support-for-cargo-workspaces","fragment":"Support for Cargo workspaces\nWhen parsing Cargo.toml files, Meson now recognizes workspaces\nand will process all the required members and any requested optional\nmembers of the workspace.\n"});
+fragment_downloaded_cb({"url":"Release-notes-for-1-10-0.html#support-for-cargo-workspaces","fragment":"Support for Cargo workspaces\nWhen parsing Cargo.toml files, Meson now recognizes workspaces\nand will process all the required members and any requested optional\nmembers of the workspace.\nFor the time being it is recommended to regroup all Cargo dependencies inside a\nsingle workspace invoked from the main Meson project. When invoking multiple\ndifferent Cargo subprojects from Meson, feature resolution of common\ndependencies might be wrong.\n"});