You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/building/bootstrapping/writing-tools-in-bootstrap.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,16 @@ There are three types of tools you can write in bootstrap:
19
19
20
20
Use this for tools that use the `rustc_private` mechanism,
21
21
and thus depend on the locally built `rustc` and its rlib artifacts.
22
-
This is more complex than the other modes because the tool must be built with the same compiler used for `rustc` and placed in the "stageN-tools" directory.
23
-
When you choose `Mode::ToolRustcPrivate`, `ToolBuild` implementation takes care of this automatically.
22
+
This is more complex than the other modes,
23
+
because the tool must be built with the same compiler used for `rustc`,
24
+
and placed in the "stageN-tools" directory.
25
+
When you choose `Mode::ToolRustcPrivate`,
26
+
`ToolBuild` implementation takes care of this automatically.
24
27
If you need to use the builder’s compiler for something specific,
25
28
you can get it from `ToolBuildResult`, which is returned by the tool's [`Step`].
26
29
27
-
Regardless of the tool type you must return `ToolBuildResult` from the tool’s [`Step`] implementation and use `ToolBuild` inside it.
30
+
Regardless of the tool type,
31
+
you must return `ToolBuildResult` from the tool’s [`Step`] implementation,
0 commit comments