mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
rust/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

98 lines
3.1 KiB
TOML
Raw Permalink Normal View History

Use workspaces and switch to a single Cargo.lock. This involves hacking the code used to run cargo test on various packages, because it reads Cargo.lock to determine which packages should be tested. This change implements a blacklist, since that will catch new crates when they are added in the future.
2016-09-02 03:55:29 -05:00
[workspace]
Switch to using the v2 resolver in most workspaces Pinning the resolver to v1 was done in 5abff3753a7c ("Explicit set workspace.resolver ...") in order to suppress warnings. Since there is no specific reason not to use the new resolver and since it fixes issues, change to `resolver = "2"` everywhere except library and submodules.
2024-08-07 02:02:57 -05:00
resolver = "2"
Use workspaces and switch to a single Cargo.lock. This involves hacking the code used to run cargo test on various packages, because it reads Cargo.lock to determine which packages should be tested. This change implements a blacklist, since that will catch new crates when they are added in the future.
2016-09-02 03:55:29 -05:00
members = [
mv compiler to compiler/
2020-08-27 22:58:48 -05:00
"compiler/rustc",
Move `test-float-parse` to the global workspace Since `test-float-parse` is now implemented in Rust, we can move it into the global workspace and check dependency licenses.
2024-07-20 11:13:27 -05:00
"src/etc/test-float-parse",
update rustc-std-workspace crates - make rustc-std-workspace-core/alloc re-exports of their underlying crates, like std = cleanup manifests
2024-11-03 15:30:16 -06:00
"src/rustc-std-workspace/rustc-std-workspace-core",
"src/rustc-std-workspace/rustc-std-workspace-alloc",
"src/rustc-std-workspace/rustc-std-workspace-std",
`src/etc/json-types` -> `src/rustdoc-json-types`
2021-01-24 14:42:33 -06:00
"src/rustdoc-json-types",
Add `build_helper` crate to share code between tidy and bootstrap
2022-12-30 04:11:33 -06:00
"src/tools/build_helper",
Move Cargo.{toml,lock} to the repository root directory.
2018-08-21 21:50:46 -05:00
"src/tools/cargotest",
"src/tools/clippy",
Implement `x.py test src/tools/clippy --bless` - Add clippy_dev to the rust workspace Before, it would give an error that it wasn't either included or excluded from the workspace: ``` error: current package believes it's in a workspace when it's not: current: /home/joshua/rustc/src/tools/clippy/clippy_dev/Cargo.toml workspace: /home/joshua/rustc/Cargo.toml this may be fixable by adding `src/tools/clippy/clippy_dev` to the `workspace.members` array of the manifest located at: /home/joshua/rustc/Cargo.toml Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest. ``` - Change clippy's copy of compiletest not to special-case rust-lang/rust. Using OUT_DIR confused `clippy_dev` and it couldn't find the test outputs. This is one of the reasons why `cargo dev bless` used to silently do nothing (the others were that `CARGO_TARGET_DIR` and `PROFILE` weren't set appropriately). - Run clippy_dev on test failure I tested this by removing a couple lines from a stderr file, and they were correctly replaced. - Fix clippy_dev warnings
2021-04-14 08:20:49 -05:00
"src/tools/clippy/clippy_dev",
Move Cargo.{toml,lock} to the repository root directory.
2018-08-21 21:50:46 -05:00
"src/tools/compiletest",
Add supporting infrastructure for `run-make` V2 tests
2024-01-20 10:51:59 -06:00
"src/tools/run-make-support",
Move Cargo.{toml,lock} to the repository root directory.
2018-08-21 21:50:46 -05:00
"src/tools/error_index_generator",
"src/tools/linkchecker",
Auto-generate lint documentation.
2020-09-08 17:09:57 -05:00
"src/tools/lint-docs",
Detect unused files in `src/test/mir-opt` and error on them in tidy.
2022-10-30 19:17:25 -05:00
"src/tools/miropt-test-tools",
Move Cargo.{toml,lock} to the repository root directory.
2018-08-21 21:50:46 -05:00
"src/tools/unstable-book-gen",
"src/tools/tidy",
Add a script to verify the Platform Support page is up-to-date.
2020-08-11 18:49:39 -05:00
"src/tools/tier-check",
Move Cargo.{toml,lock} to the repository root directory.
2018-08-21 21:50:46 -05:00
"src/tools/build-manifest",
"src/tools/remote-test-client",
"src/tools/remote-test-server",
"src/tools/rust-installer",
"src/tools/rustdoc",
"src/tools/rls",
"src/tools/rustfmt",
"src/tools/miri",
bump Miri, update for cargo-miri being a separate project
2020-06-01 13:17:20 -05:00
"src/tools/miri/cargo-miri",
Move Cargo.{toml,lock} to the repository root directory.
2018-08-21 21:50:46 -05:00
"src/tools/rustdoc-themes",
Add unicode table generator
2020-01-13 15:40:19 -06:00
"src/tools/unicode-table-generator",
Add jsondocck tool, and use it for rustdoc JSON
2021-01-15 19:34:15 -06:00
"src/tools/jsondocck",
jsondoclint: New Tool
2022-08-23 08:49:37 -05:00
"src/tools/jsondoclint",
LLVM Bitcode Linker: Added crate
2024-02-06 12:15:38 -06:00
"src/tools/llvm-bitcode-linker",
Add new tool to check HTML: * Make html-checker run by default on rust compiler docs as well * Ensure html-checker is run on CI * Lazify tidy binary presence check
2021-04-23 09:43:18 -05:00
"src/tools/html-checker",
switch stage0.txt to stage0.json and add a tool to generate it
2021-08-26 04:26:03 -05:00
"src/tools/bump-stage0",
Add replace-version-placeholder tool This tool is to be ran at specific points in the release process to replace the version place holder made by stabilizations with the version number.
2022-08-23 15:14:12 -05:00
"src/tools/replace-version-placeholder",
Add wrapper for -Z gcc-ld=lld to invoke rust-lld with the correct flavor The wrapper is installed as `ld` and `ld64` in the `lib\rustlib\<host_target>\bin\gcc-ld` directory and its sole purpose is to invoke `rust-lld` in the parent directory with the correct flavor.
2021-09-25 08:25:08 -05:00
"src/tools/lld-wrapper",
add tool to collect license metadata from REUSE
2022-11-15 03:19:17 -06:00
"src/tools/collect-license-metadata",
initial prototype of the tool to generate copyright notices
2022-11-15 04:27:19 -06:00
"src/tools/generate-copyright",
feat: implement basic suggest-tests tool
2023-03-01 03:17:08 -06:00
"src/tools/suggest-tests",
Generate windows-sys bindings
2023-04-15 05:57:07 -05:00
"src/tools/generate-windows-sys",
create new tool rustdoc-gui-test
2023-05-20 06:40:11 -05:00
"src/tools/rustdoc-gui-test",
Port PGO/LTO/BOLT optimized build pipeline to Rust
2023-06-03 02:41:44 -05:00
"src/tools/opt-dist",
Add tool `src/tools/coverage-dump` for use by some new coverage tests
2023-08-10 20:52:37 -05:00
"src/tools/coverage-dump",
Implement `x perf` as a separate tool
2024-06-27 03:22:03 -05:00
"src/tools/rustc-perf-wrapper",
Promote the `wasm32-wasip2` target to Tier 2 This commit promotes the `wasm32-wasip2` Rust target to tier 2 as proposed in rust-lang/compiler-team#760. There are two major changes in this PR: 1. The `dist-various-2` container, which already produces the other WASI targets, now has an extra target added for `wasm32-wasip2`. 2. A new `wasm-component-ld` binary is added to all host toolchains when LLD is enabled. This is the linker used for the `wasm32-wasip2` target. This new linker is added for all host toolchains to ensure that all host toolchains can produce the `wasm32-wasip2` target. This is similar to how `rust-lld` was originally included for all host toolchains to be able to produce WebAssembly output when the targets were first added. The new linker is developed [here][wasm-component-ld] and is pulled in via a crates.io-based dependency to the tree here. [wasm-component-ld]: https://github.com/bytecodealliance/wasm-component-ld
2024-06-24 14:30:44 -05:00
"src/tools/wasm-component-ld",
Update RLS and rustfmt.
2018-07-26 16:58:55 -05:00
]
Add a tool to run `x.py` from any subdirectory This adds a binary called `x` in `src/tools/x`. All it does is check the current directory and its ancestors for a file called `x.py`, and if it finds one, runs it. By installing x, you can easily `x.py` from any subdirectory. It can be installed globally with `cargo install --path src/tools/x`
2020-11-01 21:43:51 -06:00
Update RLS and rustfmt.
2018-07-26 16:58:55 -05:00
exclude = [
Cargo.toml: exclude the `build` directory from the workspace.
2018-11-25 06:59:52 -06:00
"build",
Add support for using cg_clif to bootstrap rustc
2020-10-15 07:23:43 -05:00
"compiler/rustc_codegen_cranelift",
Exclude rustc_codegen_gcc from namespace
2021-07-19 18:13:02 -05:00
"compiler/rustc_codegen_gcc",
Fully remove submodule handling from bootstrap.py These submodules were previously updated in python because Cargo gives a hard error if toml files are missing from the workspace: ``` error: failed to load manifest for workspace member `/home/jnelson/rust-lang/rust/src/tools/rls` Caused by: failed to read `/home/jnelson/rust-lang/rust/src/tools/rls/Cargo.toml` Caused by: No such file or directory (os error 2) failed to run: /home/jnelson/rust-lang/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo build --manifest-path /home/jnelson/rust-lang/rust/src/bootstrap/Cargo.toml ``` However, bootstrap doesn't actually need to be part of the workspace. Remove it so we can move submodule handling fully to Rust, avoiding duplicate code between Rust and Python. Note that this does break `cargo run`; it has to be `cd src/bootstrap && cargo run` now. Given that we're planning to make the main entrypoint a shell script (or rust binary), I think this is a good tradeoff for reduced complexity in bootstrap.py.
2022-05-29 02:26:19 -05:00
"src/bootstrap",
Change `src/test` to `tests` in source files, fix tidy and tests
2023-01-05 02:45:44 -06:00
"tests/rustdoc-gui",
HACK(eddyb) Cargo.toml: also exclude the `obj` directory from the workspace.
2018-11-25 15:15:20 -06:00
# HACK(eddyb) This hardcodes the fact that our CI uses `/checkout/obj`.
"obj",
Add a tool to run `x.py` from any subdirectory This adds a binary called `x` in `src/tools/x`. All it does is check the current directory and its ancestors for a file called `x.py`, and if it finds one, runs it. By installing x, you can easily `x.py` from any subdirectory. It can be installed globally with `cargo install --path src/tools/x`
2020-11-01 21:43:51 -06:00
# The `x` binary is a thin wrapper that calls `x.py`, which initializes
# submodules, before which workspace members cannot be invoked because
# not all `Cargo.toml` files are available, so we exclude the `x` binary,
# so it can be invoked before the current checkout is set up.
"src/tools/x",
mikros: Change back to postcard as RPC serialization format
2024-06-18 16:30:33 -05:00
"mikros_std_deps",
Update stage0 bootstrap compiler We've got a freshly minted beta compiler, let's update to use that on nightly! This has a few other changes associated with it as well * A bump to the rustc version number (to 1.19.0) * Movement of the `cargo` and `rls` submodules to their "proper" location in `src/tools/{cargo,rls}`. Now that Cargo workspaces support the `exclude` option this can work. * Updates of the `cargo` and `rls` submodules to their master branches. * Tweak to the `src/stage0.txt` format to be more amenable for Cargo version numbers. On the beta channel Cargo will bootstrap from a different version than rustc (e.g. the version numbers are different), so we need different configuration for this. * Addition of `dev` as a readable key in the `src/stage0.txt` format. If present then stage0 compilers are downloaded from `dev-static.rust-lang.org` instead of `static.rust-lang.org`. This is added to accomodate our updated release process with Travis and AppVeyor.
2017-04-20 16:32:54 -05:00
]
Temporarily turn overflow checks off for rustc-rayon-core
2021-10-24 08:36:45 -05:00
[profile.release.package.rustc-rayon-core]
# The rustc fork of Rayon has deadlock detection code which intermittently
# causes overflows in the CI (see https://github.com/rust-lang/rust/issues/90227)
# so we turn overflow checks off for now.
# FIXME: This workaround should be removed once #90227 is fixed.
overflow-checks = false
Strip lld-wrapper binaries This cuts down on the amount of data we need to ship and users need to keep on disk for each Rust toolchain. As noted in the added comment, there's not much going on in these executables, so the added benefit of symbols and debuginfo isn't large, while the cost is not insignificant. This takes each of the binaries (we store 4 identical copies under different names) from 3.7MB to 384KB.
2024-01-06 08:33:51 -06:00
# These are very thin wrappers around executing lld with the right binary name.
# Basically nothing within them can go wrong without having been explicitly logged anyway.
# We ship these in every rustc tarball and even after compression they add up
# to around 0.6MB of data every user needs to download (and 15MB on disk).
[profile.release.package.lld-wrapper]
debug = 0
strip = true
Promote the `wasm32-wasip2` target to Tier 2 This commit promotes the `wasm32-wasip2` Rust target to tier 2 as proposed in rust-lang/compiler-team#760. There are two major changes in this PR: 1. The `dist-various-2` container, which already produces the other WASI targets, now has an extra target added for `wasm32-wasip2`. 2. A new `wasm-component-ld` binary is added to all host toolchains when LLD is enabled. This is the linker used for the `wasm32-wasip2` target. This new linker is added for all host toolchains to ensure that all host toolchains can produce the `wasm32-wasip2` target. This is similar to how `rust-lld` was originally included for all host toolchains to be able to produce WebAssembly output when the targets were first added. The new linker is developed [here][wasm-component-ld] and is pulled in via a crates.io-based dependency to the tree here. [wasm-component-ld]: https://github.com/bytecodealliance/wasm-component-ld
2024-06-24 14:30:44 -05:00
[profile.release.package.wasm-component-ld-wrapper]
debug = 0
strip = true
Strip lld-wrapper binaries This cuts down on the amount of data we need to ship and users need to keep on disk for each Rust toolchain. As noted in the added comment, there's not much going on in these executables, so the added benefit of symbols and debuginfo isn't large, while the cost is not insignificant. This takes each of the binaries (we store 4 identical copies under different names) from 3.7MB to 384KB.
2024-01-06 08:33:51 -06:00
Move `test-float-parse` to the global workspace Since `test-float-parse` is now implemented in Rust, we can move it into the global workspace and check dependency licenses.
2024-07-20 11:13:27 -05:00
# Bigint libraries are slow without optimization, speed up testing
[profile.dev.package.test-float-parse]
opt-level = 3
# Speed up the binary as much as possible
[profile.release.package.test-float-parse]
opt-level = 3
codegen-units = 1
# FIXME: LTO cannot be enabled for binaries in a workspace
# <https://github.com/rust-lang/cargo/issues/9330>
# lto = true
Strip lld-wrapper binaries This cuts down on the amount of data we need to ship and users need to keep on disk for each Rust toolchain. As noted in the added comment, there's not much going on in these executables, so the added benefit of symbols and debuginfo isn't large, while the cost is not insignificant. This takes each of the binaries (we store 4 identical copies under different names) from 3.7MB to 384KB.
2024-01-06 08:33:51 -06:00
Reference in New Issue Copy Permalink