user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify that build.full-bootstrap is only used to affect uplifting, not stage selection

Browse source
This commit is contained in:
Jakub Beránek 2025-08-12 17:19:45 +02:00
parent 36dfed6435
commit f2c2d3ebc3
No known key found for this signature in database
GPG key ID: 909CD0D26483516B
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
bootstrap.example.toml
View file

@ -345,9 +345,9 @@
# want to use vendoring. See https://forge.rust-lang.org/infra/other-installation-methods.html#source-code. # want to use vendoring. See https://forge.rust-lang.org/infra/other-installation-methods.html#source-code.
#build.vendor = if "is a tarball source" && "vendor" dir exists && ".cargo/config.toml" file exists { true } else { false } #build.vendor = if "is a tarball source" && "vendor" dir exists && ".cargo/config.toml" file exists { true } else { false }
# Typically the build system will build the Rust compiler twice. The second # If you build the compiler more than twice (stage3+) or the standard library more than once
# compiler, however, will simply use its own libraries to link against. If you # (stage 2+), the third compiler and second library will get uplifted from stage2 and stage1,
# would rather to perform a full bootstrap, compiling the compiler three times, # respectively. If you would like to disable this uplifting, and rather perform a full bootstrap,
# then you can set this option to true. # then you can set this option to true.
# #
# This is only useful for verifying that rustc generates reproducible builds. # This is only useful for verifying that rustc generates reproducible builds.