about summary refs log tree commit diff
path: root/src/bootstrap/tool.rs
AgeCommit message (Collapse)AuthorLines
2023-10-17move bootstrap core implementation to bootstrap/src/core moduleonur-ozkan-848/+0
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-09-05Add tool `src/tools/coverage-dump` for use by some new coverage testsZalathar-0/+1
2023-08-21Fix elided lifetimes in rust-lang/rustMichael Goulet-1/+1
2023-07-25Remove credential providers from bootstrapArlo Siemsen-33/+0
since they are now built-in to the Cargo binary
2023-07-15Rollup merge of #113643 - jyn514:try-run, r=ozkanonurjyn-1/+2
bootstrap: Clean up try_run r? `@ozkanonur` since you reviewed `@GuillaumeGomez's` PR i recommend reviewing commit-by-commit
2023-07-15Rollup merge of #113644 - jyn514:bootstrap-cleanups, r=albertlarsan68Matthias Krüger-1/+1
misc bootstrap cleanups - rename `detail_exit_macro` to `exit` - remove unnecessary `Builder::new_standalone` function - support `x suggest` with build-metrics
2023-07-15Deduplicate `Builder::try_run` and mark `Config::try_run` as deprecatedjyn-1/+2
This does three things: 1. Remove `forward!(Build, fn try_run())`. Having `try_run` behave differently as a free function than an associated function is confusing, and `Builder::try_run` is a very desirable name. 2. Move `test::try_run` and `run::try_run` to `Builder::try_run`. These functions are different than `Config::try_run` - they delay the failure and print it out at the end of the build. 3. Mark `Config::try_run` as deprecated to encourage people to use `Builder::try_run` instead.
2023-07-14Add `track_caller` to builder.msgjyn-0/+1
this makes the panics on nested GHA groups more useful
2023-07-13Rename `detail_exit_macro` to `exit`jyn-1/+1
`detail` and `macro` weren't adding any info.
2023-07-09Port PGO/LTO/BOLT optimized build pipeline to RustJakub Beránek-0/+1
2023-07-04bootstrap: rust-installer no loger subtree, so allow running lints over itklensy-1/+1
2023-06-23Make `try_run` return a `Result<(), ()>` instead of a booleanGuillaume Gomez-1/+1
2023-06-12allow mutating the c compilers detected by bootstrapPietro Albini-1/+1
This will be needed to create synthetic targets in future commits.
2023-06-06Fix rust-analyzer proc macro serverLaurențiu Nicola-1/+1
2023-05-30create `build_helper/src/util` modozkanonur-1/+1
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-05-20implement and use tools/rustdoc-gui-test in bootstrapozkanonur-0/+1
2023-05-05Generate windows-sys bindingsChris Denton-0/+1
2023-04-29Combine several `Step`s into a single step with multiple pathsjyn-1/+1
2023-04-25Rollup merge of #110744 - weihanglo:cargo-credential-install, r=ehussYuki Okushi-3/+3
bootstrap: update paths cargo-credential crate This should be done in #110653 but forgot. Fixes #110742 ## How to verify this patch Run `./x.py build cargo`. Previously it would fail with ```console error: manifest path `/projects/rust/src/tools/cargo/crates/credential/cargo-credential-1password/Cargo.toml` does not exist ```
2023-04-24Rollup merge of #110637 - oli-obk:gha, r=jyn514Matthias Krüger-38/+23
Group some sections of our logs in github actions This makes logs a little bit more readable as you can now collapse all the parts that don't interest you (and they get collapsed automatically) Obviously there's a lot more sites where we can/need to do this, too, but this is already helpful imo r? ```@jyn514```
2023-04-23bootstrap: update paths cargo-credential crateWeihang Lo-3/+3
This should be done in #110653 but forgot.
2023-04-22Group entire build steps in the gha logsOli Scherer-38/+23
2023-04-21ship clippy, miri and rustfmt with sysrootozkanonur-6/+27
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-04-18boostrap: print output during building toolsWeihang Lo-1/+1
2023-04-18Rollup merge of #109981 - duckymirror:issue-107094, r=albertlarsan68Matthias Krüger-0/+6
Set commit information environment variables when building tools This fixes #107094. ~I'm trying to add a regression test for this issue.~ **Update**: I've added a test and a new test header `needs-git-hash` which makes sure it doesn't run when commit hashes are ignored (`bootstrap`'s `ignore-git` option).
2023-04-16bootstrap: switch from `stream_cargo` to `try_run_quiet`Weihang Lo-3/+3
It is unnecessary to stream cargo JSON output.
2023-04-16chore: remove `rustc-workspace-hack`Weihang Lo-129/+2
Co-authored-by: Scott Schafer <schaferjscott@gmail.com> Co-authored-by: Eric Huss <eric@huss.org>
2023-04-16chore: remove Cargo features in rustc-workspace-hackWeihang Lo-1/+0
2023-04-16chore: allow `cargo` to have its own workspaceWeihang Lo-1/+4
This also * bumps cargo to the latest in rust-lang/cargo. * adds 0BSD to allowed list of licenses Co-authored-by: Scott Schafer <schaferjscott@gmail.com> Co-authored-by: Eric Huss <eric@huss.org>
2023-04-16Set git info env variables when building toolsErik Hofmayer-0/+6
This should fix issue #107094.
2023-04-09feat: implement basic suggest-tests toolEzra Shaw-0/+1
2023-04-08s/ignore_git/omit_git_hashGimbles-1/+1
2023-02-21Enable --cfg=parallel_compiler in rustdoc.Mara Bos-1/+5
2023-02-19Improve building compiler artifacts outputMatthew J Perez-6/+54
2023-01-14Make stage2 rustdoc and proc-macro-srv disableable in x.py installDavid Tolnay-0/+6
2023-01-14Auto merge of #106520 - ehuss:update-mdbook, r=Mark-Simulacrumbors-2/+23
Update mdbook This updates mdbook from 0.4.21 to 0.4.25. The list of changes is [here](https://github.com/rust-lang/mdBook/blob/master/CHANGELOG.md#mdbook-0425). The only user-visible changes are some changes around the theme picker, and change to the copy-to-clipboard ignoring hidden lines. Internally there were some dependency updates and small fixes. This also updates `clap` from 4.0.15 to 4.0.32 whose changelog is [here](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md#4032---2022-12-22). This impacts tools like cargo. I don't see anything particularly noteworthy there, though there are some small user-visible changes. Unfortunately this required adding a hack for building `rustix` with a bootstrap tool. The comment explains why. I am unable to think of some other workaround (or even a cleaner way to set the rustflag). Ideas are welcome if you can think of alternatives. I'm struggling to even think of a long-term solution, other than asking projects not to do auto-nightly feature detection. One medium-term solution is to avoid the clap dependency for the mdbook library (which is how rustix gets pulled in). That is one of my goals for the 0.5 release of mdbook, but that probably won't happen until later this year. It would also require dropping clap from `rustbook` and using some other means to parse arguments (there's only two options, so it can probably be done manually).
2023-01-09Update mdbookEric Huss-2/+23
2023-01-04Revert "bootstrap: Get rid of `tail_args` in `stream_cargo`"Joshua Nelson-1/+1
This reverts commit 9dfe50440e6d48bd2fd40a4b7b3992998e55eace. Fixes `x clippy`.
2022-12-30bootstrap: Get rid of `tail_args` in `stream_cargo`Joshua Nelson-1/+1
2022-12-08Build rust-analyzer proc-macro server by defaultJoshua Nelson-10/+0
This allows getting rid of some documentation and an extra step when building a custom toolchain: https://rustc-dev-guide.rust-lang.org/building/how-to-build-and-run.html#creating-a-rustup-toolchain and it seems likely that people will want to do this if they want rustdoc (which is also built by default).
2022-11-15initial prototype of the tool to generate copyright noticesPietro Albini-0/+1
2022-11-15add tool to collect license metadata from REUSEPietro Albini-0/+1
2022-11-12Distinguish `--dry-run` from the automatic dry run checkJoshua Nelson-1/+1
2022-10-31Auto merge of #102950 - oli-obk:check_miri, r=RalfJungbors-18/+12
Enable `x.py check` for miri Now that the miri subtree is working properly, let's add it to x.py check. cc `@rust-lang/miri`
2022-10-19mark rust-analyzer as a host-only toolPietro Albini-2/+2
All tools meant to be shipped with host toolchains only should be marked as `ONLY_HOSTS = true`, but rust-analyzer was marked as `ONLY_HOSTS = false` incorrectly. This meant that bootstrap attempted to build rust-analyzer for cross-compilation-only targets, causing errors because libstd is not present on some of them. It will still be possible to cross-compile rust-analyzer by passing a different --host flag to ./x, like you can cross-compile other tools.
2022-10-13Remove unused macro argumentOli Scherer-12/+11
2022-10-12Enable `x.py check` for miriOli Scherer-14/+9
2022-10-04Don't build the compiler before building rlsJosh Stone-1/+1
The rls stub is a simple stable tool, which doesn't need compiler libs.
2022-09-21Remove miri from the submodule list and require it for CI to passOli Scherer-2/+2
2022-09-17Rollup merge of #101873 - WaffleLapkin:x-build-proc-macro-srv, r=jyn514Matthias Krüger-10/+22
Allow building `rust-analyzer-proc-macro-srv` as a standalone tool This PR allows building `rust-analyzer-proc-macro-srv` as a standalone tool via `x b proc-macro-srv-cli` (I thought that `x b rust-analyzer-proc-macro-srv` should work, but it doesn't for some reason...). Also this PR adds a copy of `rust-analyzer-proc-macro-srv` binary to `build/{triple}/{stage}/libexec/` when building `rust-analyzer-proc-macro-srv`, so that r-a can pick it up. This is useful to make r-a (and I assume Intellij IDEA) to expand macros when using a custom, build from source toolchain. r? ``@jyn514`` [_zulip thread_](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/How.20to.20fix.20.60UnsupportedABI.60.20for.20custom.20toolchains.3F/near/299040175)
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-22 21:52:58 +0000