Changeset 24ecd679

Timestamp:

06/01/2023 11:09:45 AM (4 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

12.0, kea, lazarus, lxqt, trunk, xry111/xf86-video-removal

Children:

48d48bdd

Parents:

185bfd71

git-author:

Xi Ruoyao <xry111@…> (06/01/2023 10:52:47 AM)

git-committer:

Xi Ruoyao <xry111@…> (06/01/2023 11:09:45 AM)

Message:

rust: Add rustdoc into build.tools

The rustdoc program is a part of rustup default install. And it was
installed with previous rustc releases even if we didn't specify it in
build.tools (so it's in the "contents and short descriptions" section).
But with rustc-1.69 it's not installed if we don't explicitly add it
into build.tools.

It's needed by "cargo doc" command (I use it when I develop Rust
crates), and also some BLFS packages (at least, the testsuite of
librsvg).

Add rustdoc into build.tools so it will be built and installed.

File:

• general/prog/rust.xml (modified) (2 diffs)

general/prog/rust.xml

@@ -283 +283 @@
 
 # Specify which extended tools (those from the default install).
-tools = ["cargo", "clippy", "rustfmt"]
+tools = ["cargo", "clippy", "rustdoc", "rustfmt"]
 
 # Use the source code shipped in the tarball for the dependencies.
@@ -441 +441 @@
 
     <para>
-      <command>tools = ["cargo", "clippy", "rustfmt"]</command>: if the tools
-      are not scecified, the absence of <application>Miri</application> now
-      causes the install to fail. But <application>Miri</application> is not
-      built in the stable channel. Some of the other tools are unlikely to
-      be useful unless using (old) code analyzers or editing the standard library.
-      This set match those from the 'default' profile in binary command
-      <command>rustup</command> which are recommended for most users, except that
-      the documentation was disabled at the start of the '[build]' section.
+      <command>tools = ["cargo", "clippy", "rustdoc", "rustfmt"]</command>:
+      only build the tools from the 'default' profile in binary command
+      <command>rustup</command> which are recommended for most users.
+      The other tools are unlikely to be useful unless using (old) code
+      analyzers or editing the standard library.
     </para>