-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bootstrap: Various Step refactors #111955
Commits on May 29, 2023
-
Give a more helpful error when calling
cargo_crates_in_set
for an a……lias Before: ``` thread 'main' panicked at 'no entry found for key', builder.rs:110:30 ``` After: ``` thread 'main' panicked at 'missing crate for path library', check.rs:89:26 ```
Configuration menu - View commit details
-
Copy full SHA for c571558 - Browse repository at this point
Copy the full SHA c571558View commit details -
Allow checking individual crates
This is useful for profiling metadata generation. This comes very close to removing all_krates, but doesn't quite - there's one last usage left in `doc`.
Configuration menu - View commit details
-
Copy full SHA for 564e3ad - Browse repository at this point
Copy the full SHA 564e3adView commit details -
Add a
make_run_crates
function and use it Rustc and StdThis fixes the panic from the previous commit.
Configuration menu - View commit details
-
Copy full SHA for 20372f1 - Browse repository at this point
Copy the full SHA 20372f1View commit details -
Extend
msg
anddescription
to work with any subcommandPreviously `description` only supported `Testing` and `Benchmarking`, and `msg` gave weird results for `doc` (it would say `Docing`).
Configuration menu - View commit details
-
Copy full SHA for cb4b7f6 - Browse repository at this point
Copy the full SHA cb4b7f6View commit details -
Switch doc::{Std, Rustc} to
crate_or_deps
Previously they were using `all_krates` and various hacks to determine which crates to document. Switch them to `crate_or_deps` so `ShouldRun` tells them which crate to document instead of having to guess. This also makes a few other refactors: - Remove the now unused `all_krates`; new code should only use `crate_or_deps`. - Add tests for documenting Std - Remove the unnecessary `run_cargo_rustdoc_for` closure so that we only run cargo once - Give a more helpful error message when documenting a no_std target - Use `builder.msg` in the Steps instead of `builder.info`
Configuration menu - View commit details
-
Copy full SHA for 58e18dd - Browse repository at this point
Copy the full SHA 58e18ddView commit details -
Switch Steps from crates to crate_or_deps where possible
and document why the single remaining place can't switch
Configuration menu - View commit details
-
Copy full SHA for 3e765a7 - Browse repository at this point
Copy the full SHA 3e765a7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 71770d5 - Browse repository at this point
Copy the full SHA 71770d5View commit details -
- Switch from `cargo rustdoc` to `cargo doc` This allows passing `-p` to multiple packages. - Remove `OsStr` support It doesn't work with RUSTDOCFLAGS, and we don't support non-utf8 paths anyway. - Pass `-p std` for each crate in the standard library By default cargo only documents the top-level crate, which is `sysroot` and has no docs.
Configuration menu - View commit details
-
Copy full SHA for c28ee60 - Browse repository at this point
Copy the full SHA c28ee60View commit details