rust/.gitignore

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

85 lines
1.3 KiB
Plaintext
Raw Normal View History

2019-10-21 16:36:49 +08:00
# This file should only ignore things that are generated during a `x.py` build,
# generated by common IDEs, and optional files controlled by the user that
# affect the build (such as config.toml).
# In particular, things like `mir_dump` should not be listed here; they are only
# created during manual debugging and many people like to clean up instead of
# having git ignore such leftovers. You can use `.git/info/exclude` to
# configure your local ignore list.
2021-04-21 03:40:32 +08:00
## File system
.DS_Store
desktop.ini
## Editor
2021-03-11 10:28:05 +08:00
*.swp
*.swo
2021-04-21 03:40:32 +08:00
Session.vim
.cproject
2016-05-14 01:18:59 +08:00
.idea
*.iml
2021-04-21 03:40:32 +08:00
.vscode
.project
.vim/
2021-04-21 03:40:32 +08:00
.favorites.json
.settings/
.vs/
2021-04-21 03:40:32 +08:00
## Tool
2011-01-04 05:56:01 +08:00
.valgrindrc
2021-04-21 03:40:32 +08:00
.cargo
# Included because it is part of the test case
!/tests/run-make/thumb-none-qemu/example/.cargo
2021-04-21 03:40:32 +08:00
## Configuration
/config.toml
2021-04-21 03:40:32 +08:00
/Makefile
config.mk
config.stamp
no_llvm_build
## Build
/dl/
2019-08-09 01:42:46 +08:00
/doc/
2011-12-24 03:43:27 +08:00
/inst/
/llvm/
2011-07-14 04:51:30 +08:00
/mingw-build/
Ignore things in .gitignore in tidy - Switch from `walkdir` to `ignore`. This required various changes to make `skip` thread-safe. - Ignore `build` anywhere in the source tree, not just at the top-level. We support this in bootstrap, we should support it in tidy too. As a nice side benefit, this also makes tidy a bit faster. Before: ``` ; hyperfine -i '"/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0-tools-bin/rust-tidy" "/home/gh-jyn514/rust2" "/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0/bin/cargo" "/home/gh-jyn514/rust2/build" "32"' Benchmark 1: "/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0-tools-bin/rust-tidy" "/home/gh-jyn514/rust2" "/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0/bin/cargo" "/home/gh-jyn514/rust2/build" "32" Time (mean ± σ): 1.080 s ± 0.008 s [User: 2.616 s, System: 3.243 s] Range (min … max): 1.069 s … 1.099 s 10 runs ``` After: ``` ; hyperfine '"/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0-tools-bin/rust-tidy" "/home/gh-jyn514/rust2" "/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0/bin/cargo" "/home/gh-jyn514/rust2/build" "32"' Benchmark 1: "/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0-tools-bin/rust-tidy" "/home/gh-jyn514/rust2" "/home/gh-jyn514/rust2/build/aarch64-unknown-linux-gnu/stage0/bin/cargo" "/home/gh-jyn514/rust2/build" "32" Time (mean ± σ): 705.0 ms ± 1.4 ms [User: 3179.1 ms, System: 1517.5 ms] Range (min … max): 702.3 ms … 706.9 ms 10 runs ```
2023-01-04 10:16:24 +08:00
build/
2023-03-18 13:29:53 +08:00
!/compiler/rustc_mir_build/src/build/
/build-rust-analyzer/
2021-04-21 03:40:32 +08:00
/dist/
2020-01-14 05:40:19 +08:00
/unicode-downloads
/target
Move the standard library to a separate workspace This ensures that the Cargo.lock packaged for it in the rust-src component is up-to-date, allowing rust-analyzer to run cargo metadata on the standard library even when the rust-src component is stored in a read-only location as is necessary for loading crates.io dependencies of the standard library. This also simplifies tidy's license check for runtime dependencies as it can now look at all entries in library/Cargo.lock without having to filter for just the dependencies of runtime crates. In addition this allows removing an exception in check_runtime_license_exceptions that was necessary due to the compiler enabling a feature on the object crate which pulls in a dependency not allowed for the standard library. While cargo workspaces normally enable dependencies of multiple targets to be reused, for the standard library we do not want this reusing to prevent conflicts between dependencies of the sysroot and of tools that are built using this sysroot. For this reason we already use an unstable cargo feature to ensure that any dependencies which would otherwise be shared get a different -Cmetadata argument as well as using separate build dirs. This doesn't change the situation around vendoring. We already have several cargo workspaces that need to be vendored. Adding another one doesn't change much. There are also no cargo profiles that are shared between the root workspace and the library workspace anyway, so it doesn't add any extra work when changing cargo profiles.
2024-08-02 04:09:50 +08:00
/library/target
/src/bootstrap/target
2021-04-21 03:40:32 +08:00
/src/tools/x/target
# Created by default with `src/ci/docker/run.sh`
/obj/
2024-06-18 11:56:12 +08:00
/rustc-ice*
2021-04-21 03:40:32 +08:00
## Temporary files
*~
\#*
\#*\#
.#*
## Tags
2018-07-22 20:14:06 +08:00
tags
tags.*
TAGS
2018-07-22 20:14:06 +08:00
TAGS.*
2021-04-21 03:40:32 +08:00
## Python
__pycache__/
*.py[cod]
*$py.class
## Node
node_modules
package-lock.json
2022-02-02 00:14:59 +08:00
package.json
2021-04-21 03:40:32 +08:00
## Rustdoc GUI tests
tests/rustdoc-gui/src/**.lock
2019-10-21 16:36:49 +08:00
# Before adding new lines, see the comment at the top.