summary refs log tree commit diff
path: root/src/bootstrap/Cargo.toml
AgeCommit message (Collapse)AuthorLines
2024-11-11move `src/tools/build_helper` into `src/build_helper`onur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-09-27Bump `cc` and run `cargo update` for bootstrapTrevor Gross-1/+1
Bump `cc` to 1.1.22, which includes a caching fix. Also run `cargo update` which does a minor increment on a few dependencies.
2024-09-18Bump cc dependencyArtyom Tetyukhin-1/+1
2024-08-18Update some dependency versions that allow better licensingTrevor Gross-1/+1
With the new resolver, a few dependencies get brought in twice with different licenses. For example, all dependencies from `wasm-tools` gained Apache-2.0 and MIT options, and with the v2 resolver we were using one version from before and one version from after this change. This made tidy's license check difficult. Update some minimum versions to remove duplicate dependencies and smooth out license checking.
2024-08-01Update sysinfo version to 0.31.2Guillaume Gomez-1/+1
2024-07-14use std for file mtime and atime modificationsonur-ozkan-1/+0
Since 1.75 std provides an interface to set access and modified times on files. This change replaces the external dependency previously used for these operations with the corresponding std functions. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-07-07bootstrap: once_cell::sync::Lazy -> std::sync::LazyLockPavel Grigorenko-1/+0
2024-06-04bootstrap: implement new feature `bootstrap-self-test`onur-ozkan-0/+1
Some of the bootstrap logics should be ignored during unit tests because they either make the tests take longer or cause them to fail. Therefore we need to be able to exclude them from the bootstrap when it's called by unit tests. This change introduces a new feature called `bootstrap-self-test`, which is enabled on bootstrap unit tests by default. This allows us to keep the logic separate between compiler builds and bootstrap tests without needing messy workarounds (like checking if target names match those in the unit tests). Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-05-06Update version of cc crate to v1.0.97James Farrell-1/+1
Reason: In order to build the Windows version of the Rust toolchain for the Android platform, the following patch to the cc is crate is required to avoid incorrectly determining that we are building with the Android NDK: https://github.com/rust-lang/cc-rs/commit/57853c4bf8a89a0f4c9137eb367ac580305c6919 This patch is present in version 1.0.80 and newer versions of the cc crate. The rustc source distribution currently has 3 different versions of cc in the vendor directory, only one of which has the necessary fix. We (the Android Rust toolchain) are currently maintaining local patches to upgrade the cc crate dependency versions, which we would like to upstream. Furthermore, beyond the specific reason, the cc crate in bootstrap is currently pinned at an old version due to problems in the past when trying to update it. It is worthwhile to figure out and resolve these problems so we can keep the dependency up-to-date. Other fixes: As of cc v1.0.78, object files are prefixed with a 16-character hash. Update src/bootstrap/src/core/build_steps/llvm.rs to account for this to avoid failures when building libunwind and libcrt. Note that while the hash prefix was introduced in v1.0.78, in order to determine the names of the object files without scanning the directory, we rely on the compile_intermediates method, which was introduced in cc v1.0.86 As of cc v1.0.86, compilation on MacOS uses the -mmacosx-version-min flag. A long-standing bug in the CMake rules for compiler-rt causes compilation to fail when this flag is specified. So we add a workaround to suppress this flag. Updating to cc v1.0.91 and newer requires fixes to bootstrap unit tests. The unit tests use targets named "A", "B", etc., which fail a validation check introduced in 1.0.91 of the cc crate.
2024-05-01add a reference link to the comment of the "cc" and "cmake".onur-ozkan-3/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-04-19bootstrap: don't use rayon for sysinfoklensy-1/+1
It's looks overkill to use rayon to collect cpu usage
2024-01-11bump bootstrap dependenciesonur-ozkan-15/+19
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-12-30bootstrap: bump fd-lockonur-ozkan-5/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-12-25Update sysinfo version to 0.30.1Guillaume Gomez-1/+1
2023-12-21Update sysinfo version to 0.30.0Guillaume Gomez-1/+1
2023-12-16create helper fn `hex_encode` and remove `hex` dependencyonur-ozkan-1/+0
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-12-05Update bootstrap libc to 0.2.150Urgau-1/+1
Version 0.2.150 include support for the new check-cfg syntax
2023-10-30bootstrap: bump fd-lock, clap and windows.chenx97-3/+3
this also updates target-sensitive dependencies like rustix and libc.
2023-10-24remap cargo dependencies to /rust/depsPietro Albini-0/+1
2023-10-17move bootstrap utils into bootstrap/src/utils moduleonur-ozkan-5/+5
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-15bump bootstrap:clap_complete to `4.4.3`onur-ozkan-1/+1
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-10move `features` above to appear before others sectionsonur-ozkan-3/+3
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-10sort/reorganize dependencies in bootstrap/Cargo.tomlonur-ozkan-9/+9
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-09-01bump pretty_assertions to 1.4onur-ozkan-1/+1
Removes the duplicated dependency(syn 1.0.102) from bootstrap dependency tree Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-08-14Upgrade Object and related depsdirreke-1/+1
2023-06-05bootstrap: remove dep `is-terminal`kadiwa-1/+0
2023-06-03only check when we specify rustc in config.tomlyukang-0/+1
2023-05-27Revert "Rollup merge of #111538 - ↵Mark Rousskov-1/+0
chenyukang:yukang-fix-110067-version-issue, r=jyn514" This reverts commit 9267843e72c8692f934c2ef5505c8a7496c0f06e, reversing changes made to e52fbff5e8c2de7ba085ef84d7d50500b695d521. This breaks our ability to bump the src/version where we're bootstrapping with an older compiler than usual (according to version number). It's not clear whether the intended use case has a clean solution given this constraint, so reverting for now - we can reland with a fix of some kind implemented.
2023-05-20Auto merge of #111413 - workingjubilee:bump-object-0-31-1, r=MarkSimulacrumbors-1/+1
Bump object and thorin-dwp Required to fix watchOS breakage.
2023-05-14Make sure the build.rustc version is either the same or 1 apartyukang-0/+1
2023-05-10Bump object and thorin-dwpJubilee Young-1/+1
object -> 0.31.1 thorin-dwp -> 0.6.0 Required to fix watchOS breakage.
2023-05-10Generate shell completions for bootstrap with Clapclubby789-0/+1
2023-05-06Migrate bootstrap to Clap-based argumentsclubby789-1/+2
2023-04-12drop some windows featuresklensy-4/+0
2023-04-05Use the `junction` crate in bootstrap instead of manually creating the junctionThom Chiovoloni-0/+3
2023-04-01bootstrap replace atty with is-terminal, dedupe few depsklensy-1/+1
2023-03-21Auto merge of #108659 - ferrocene:pa-test-metrics, r=Mark-Simulacrumbors-0/+2
Include executed tests in the build metrics (and use a custom test display impl) The main goal of this PR is to include all tests executed in CI inside the build metrics JSON files. I need this for Ferrocene, and `@Mark-Simulacrum` expressed desire to have this as well to ensure all tests are executed at least once somewhere in CI. Unfortunately implementing this required rewriting inside of bootstrap all of the code to render the test output to console. libtest supports outputting JSON instead of raw text, which we can indeed use to populate the build metrics. Doing that suppresses the console output though, and compared to rustc and Cargo the console output is not included as a JSON field. Because of that, this PR had to reimplement both the "pretty" format (one test per line, with `rust.verbose-tests = true`), and the "terse" format (the wall of dots, with `rust.verbose-tests = false`). The current implementation should have the exact same output as libtest, except for the benchmark output. libtest's benchmark output is broken in the "terse" format, so since that's our default I slightly improved how it's rendered. Also, to bring parity with libtest I had to introduce support for coloring output from bootstrap, using the same dependencies `annotate-snippets` uses. It's now possible to use `builder.color_for_stdout(Color::Red, "text")` and `builder.color_for_stderr(Color::Green, "text")` across all of bootstrap, automatically respecting the `--color` flag and whether the stream is a terminal or not. I recommend reviewing the PR commit-by-commit. r? `@Mark-Simulacrum`
2023-03-20migrate compiler, bootstrap, and compiletest to windows-rsAndy Russell-11/+13
2023-03-13Don't use fd-lock on Solaris in bootstrapPetr Sumbera-1/+4
...as Solaris is missing flock() fixes #103630
2023-03-07switch to termcolorPietro Albini-1/+1
2023-03-02add a splash of colorPietro Albini-0/+2
2023-02-27Allow building serde and serde_derive in parallelbjorn3-1/+4
This reduces build time of bootstrap by ~6s
2023-01-03Add `build_helper` crate to share code between tidy and bootstrapNilstrieb-0/+1
2022-12-31Revert "Auto merge of #105058 - ↵Joshua Nelson-1/+0
Nilstrieb:no-merge-commits-for-you-only-bors-is-allowed-to-do-that, r=jyn514" This reverts commit 4839886f0abe208ab8f2bb73a3076a59fe2ab60c, reversing changes made to ce85c98575e3016cf2007d90a85be321e592aa96.
2022-12-30Add `build_helper` crate to share code between tidy and bootstrapNilstrieb-0/+1
2022-12-22Use LLVM_CMAKE_DIR for lld buildNikita Popov-5/+0
LLVM_CONFIG_PATH is no longer supported as of LLVM 16, switch to using the cmake module instead. We separately return the llvm-config and cmake directory paths, because llvm-config always refers to the host binary, while the cmake directory is for the target triple.
2022-12-04Update pretty_assertions to 1.3bjorn3-1/+1
This replaces ansi_term with yansi which in turn removes a winapi dependency edge
2022-11-23Bump `fd-lock` in `bootstrap` againMateusz Mikuła-1/+1
Followup to https://github.com/rust-lang/rust/pull/103778 Sorry for the quick succession but this fixes one more building issue for Tier 3 `windows-gnullvm` that I have previously missed, and it would be nice to have it in the release.
2022-11-22Rollup merge of #104622 - nicholasbishop:bishop-uefi-clang, r=Mark-SimulacrumManish Goregaokar-0/+1
Use clang for the UEFI targets This fixes an issue where the C and asm sources built by compiler_builtins were being compiled as ELF objects instead of PE objects. This wasn't noticed before because it doesn't cause compiler_builtins or rustc to fail to build. You only see a failure when a program is built that references one of the symbols in an ELF object. Compiling with clang fixes this because the cc crate converts the UEFI targets into Windows targets that clang understands, causing it to produce PE objects. Also update compiler_builtins to 0.1.84 to pull in some necessary fixes for compiling the UEFI targets with clang. Fixes https://github.com/rust-lang/rust/issues/104326
2022-11-20dist: Ensure UEFI rlibs are all COFFNicholas Bishop-0/+1
If clang isn't the C compiler used for the UEFI targets, or if the wrong `--target` is passed to clang, we will get ELF objects in some rlibs. This will cause problems at link time when trying to compile a UEFI program that uses any of those objects. Add a check to the dist step for UEFI targets that reads each rlib with the `object` crate and fails with an error if any non-COFF objects are found.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-27 17:41:00 +0000