add rustc-dev doc about bootstrap tools
Signed-off-by: onur-ozkan <work@onurozkan.dev>
This commit is contained in:
parent
5408aaea59
commit
26d6ce76a7
2 changed files with 24 additions and 0 deletions
|
@ -75,6 +75,7 @@
|
||||||
- [Prologue](./building/bootstrapping/intro.md)
|
- [Prologue](./building/bootstrapping/intro.md)
|
||||||
- [What Bootstrapping does](./building/bootstrapping/what-bootstrapping-does.md)
|
- [What Bootstrapping does](./building/bootstrapping/what-bootstrapping-does.md)
|
||||||
- [How Bootstrap does it](./building/bootstrapping/how-bootstrap-does-it.md)
|
- [How Bootstrap does it](./building/bootstrapping/how-bootstrap-does-it.md)
|
||||||
|
- [Writing tools in Bootstrap](./building/bootstrapping/writing-tools-in-bootstrap.md)
|
||||||
- [Debugging bootstrap](./building/bootstrapping/debugging-bootstrap.md)
|
- [Debugging bootstrap](./building/bootstrapping/debugging-bootstrap.md)
|
||||||
|
|
||||||
# High-level Compiler Architecture
|
# High-level Compiler Architecture
|
||||||
|
|
|
@ -0,0 +1,23 @@
|
||||||
|
# Writing tools in Bootstrap
|
||||||
|
|
||||||
|
There are three types of tools you can write in bootstrap:
|
||||||
|
|
||||||
|
- **`Mode::ToolBootstrap`**
|
||||||
|
Use this for tools that don’t need anything from the in-tree compiler and can run with the stage0 `rustc`.
|
||||||
|
The output is placed in the "stage0-bootstrap-tools" directory. This mode is for general-purpose tools built
|
||||||
|
entirely with the stage0 compiler, including target libraries and only works for stage 0.
|
||||||
|
|
||||||
|
- **`Mode::ToolStd`**
|
||||||
|
Use this for tools that rely on the locally built std. The output goes into the "stageN-tools" directory.
|
||||||
|
This mode is rarely used, mainly for `compiletest` which requires `libtest`.
|
||||||
|
|
||||||
|
- **`Mode::ToolRustc`**
|
||||||
|
Use this for tools that depend on both the locally built `rustc` and the target `std`. 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. When you choose `Mode::ToolRustc`, `ToolBuild` implementation takes care of this automatically.
|
||||||
|
If you need to use the builder’s compiler for something specific, you can get it from `ToolBuildResult`, which is
|
||||||
|
returned by the tool's [`Step`].
|
||||||
|
|
||||||
|
Regardless of the tool type you must return `ToolBuildResult` from the tool’s [`Step`] implementation and use `ToolBuild` inside it.
|
||||||
|
|
||||||
|
[`Step`]: https://doc.rust-lang.org/nightly/nightly-rustc/bootstrap/core/builder/trait.Step.html
|
Loading…
Add table
Add a link
Reference in a new issue