AcoSail/llvm-project
8
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
main
llvm-project/.gitignore

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

73 lines
2.2 KiB
Plaintext
Raw Permalink Normal View History

Add a reduced copy of the llvm .gitignore as a start for the monorepo .gitignore. llvm-svn: 357961
2019-04-09 08:52:49 +08:00
#==============================================================================#
# This file specifies intentionally untracked files that git should ignore.
# See: http://www.kernel.org/pub/software/scm/git/docs/gitignore.html
#
# This file is intentionally different from the output of `git svn show-ignore`,
# as most of those are useless.
#==============================================================================#
#==============================================================================#
# File extensions to be ignored anywhere in the tree.
#==============================================================================#
# Temp files created by most text editors.
*~
# Merge files created by git.
*.orig
[llvm] Ignore .rej files in .gitignore Ignore reject files (.rej) files generated by patch. I can't imagine a reason they should ever be checked in. I considered ignoring patch files as well but decided to err on the side of caution because we might not want them to be easily deleted by something like git clean. Differential revision: https://reviews.llvm.org/D124619
2022-04-28 23:43:12 +08:00
# Reject files created by patch.
*.rej
Add a reduced copy of the llvm .gitignore as a start for the monorepo .gitignore. llvm-svn: 357961
2019-04-09 08:52:49 +08:00
# Byte compiled python modules.
*.pyc
# vim swap files
.*.sw?
.sw?
#OS X specific files.
.DS_store
[NFC] Add CMakeUserPresets.json filename to .gitignore CMake 3.19 introduced the `presets`. Quoting the documentation: > `CMakePresets.json` may be checked into a version control system, and > `CMakeUserPresets.json` **should NOT be checked in**. We will ignore the `CMakeUserPresets.json` file if that is present at the root of a subproject. Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D93167
2021-01-22 19:45:29 +08:00
# Ignore the user specified CMake presets in subproject directories.
/*/CMakeUserPresets.json
Add a reduced copy of the llvm .gitignore as a start for the monorepo .gitignore. llvm-svn: 357961
2019-04-09 08:52:49 +08:00
# Nested build directory
Change /build to /build* in top-level .gitignore. Reviewers: beanz Differential Revision: https://reviews.llvm.org/D65559 llvm-svn: 367641
2019-08-02 10:14:08 +08:00
/build*
Add a reduced copy of the llvm .gitignore as a start for the monorepo .gitignore. llvm-svn: 357961
2019-04-09 08:52:49 +08:00
#==============================================================================#
# Explicit files to ignore (only matches one).
#==============================================================================#
# Various tag programs
/tags
/TAGS
/GPATH
/GRTAGS
/GSYMS
/GTAGS
Add GNU idutils tag filename to .gitignore. Differential Revision: https://reviews.llvm.org/D81331
2020-06-13 04:05:08 +08:00
/ID
Add a reduced copy of the llvm .gitignore as a start for the monorepo .gitignore. llvm-svn: 357961
2019-04-09 08:52:49 +08:00
.gitusers
autom4te.cache
cscope.files
cscope.out
autoconf/aclocal.m4
autoconf/autom4te.cache
/compile_commands.json
# Visual Studio built-in CMake configuration
/CMakeSettings.json
# CLion project configuration
/.idea
#==============================================================================#
# Directories to ignore (do not add trailing '/'s, they skip symlinks).
#==============================================================================#
# VS2017 and VSCode config files.
.vscode
.vs
[NFC] Adding pythonenv* to .gitignore The new feature in GitHub called 'GitHub Codespaces' generates a pythonenv3.8 directory in the root level of the llvm-project git checkout. So I am adding that directory to the .gitignore. See the following for more info: https://github.com/features/codespaces Differential Revision: https://reviews.llvm.org/D86846
2020-09-04 10:42:27 +08:00
# pythonenv for github Codespaces
pythonenv*
[clangd] Store index in '.cache/clangd/index' instead of '.clangd/index' Summary: .clangd/index was well-intentioned in 2754942cbaef, but `.clangd` is the best filename for the clangd config file (matching .clang-format and .clang-tidy). And of course we can't have both .clangd/index and .clangd... There are a few overlapping goals to satisfy: - it should be clear from the directory name that this is transient data that is safe to delete at the cost of recomputation, i.e. a cache - it should be easy and self-documenting to blacklist these files in .gitignore - we should have some consistency between filenames in-tree and corresponding files in user storage (e.g. under XDG's ~/.cache/) - we should be consistent across platforms (including windows, which doesn't have distinct cache vs config directories) So the plan is: $PROJECT/.clangd (project config) $PROJECT/.cache/clangd/index/ (project index) $PROJECT/.cache/clangd/modules/ (maybe in future) $XDG_CONFIG_HOME/clangd/config.yaml (user config) $XDG_CACHE_HOME/clangd/index/ (index of non-project files) $XDG_CACHE_HOME/clangd/modules/ (maybe in future) This is sensible if XDG_{CONFIG,CACHE}_HOME coincide, and has a simple .gitignore rule going forward: `.cache/`. The monorepo gitignore is updated to reflect the backwards-compatible practice: ignore .clangd/ (with trailing slash) matching index files from clangd 9/10 ignore .cache matching index from clangd 11+, and potentially other tools. The entries from llvm-project/llvm gitignore are removed (obsolete). Reviewers: kadircet, hokein Subscribers: ilya-biryukov, MaskRay, jkorous, omtcyfz, arphaman, usaxena95, cfe-commits, llvm-commits Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D83099
2020-07-03 05:51:26 +08:00
# clangd index. (".clangd" is a config file now, thus trailing slash)
.clangd/
.cache
[analyzer] SATest: Add a set of initial projects for testing Differential Revision: https://reviews.llvm.org/D81592
2020-06-04 23:40:39 +08:00
# static analyzer regression testing project files
/clang/utils/analyzer/projects/*/CachedSource
/clang/utils/analyzer/projects/*/PatchedSource
/clang/utils/analyzer/projects/*/ScanBuildResults
[clangd] Store index in '.cache/clangd/index' instead of '.clangd/index' Summary: .clangd/index was well-intentioned in 2754942cbaef, but `.clangd` is the best filename for the clangd config file (matching .clang-format and .clang-tidy). And of course we can't have both .clangd/index and .clangd... There are a few overlapping goals to satisfy: - it should be clear from the directory name that this is transient data that is safe to delete at the cost of recomputation, i.e. a cache - it should be easy and self-documenting to blacklist these files in .gitignore - we should have some consistency between filenames in-tree and corresponding files in user storage (e.g. under XDG's ~/.cache/) - we should be consistent across platforms (including windows, which doesn't have distinct cache vs config directories) So the plan is: $PROJECT/.clangd (project config) $PROJECT/.cache/clangd/index/ (project index) $PROJECT/.cache/clangd/modules/ (maybe in future) $XDG_CONFIG_HOME/clangd/config.yaml (user config) $XDG_CACHE_HOME/clangd/index/ (index of non-project files) $XDG_CACHE_HOME/clangd/modules/ (maybe in future) This is sensible if XDG_{CONFIG,CACHE}_HOME coincide, and has a simple .gitignore rule going forward: `.cache/`. The monorepo gitignore is updated to reflect the backwards-compatible practice: ignore .clangd/ (with trailing slash) matching index files from clangd 9/10 ignore .cache matching index from clangd 11+, and potentially other tools. The entries from llvm-project/llvm gitignore are removed (obsolete). Reviewers: kadircet, hokein Subscribers: ilya-biryukov, MaskRay, jkorous, omtcyfz, arphaman, usaxena95, cfe-commits, llvm-commits Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D83099
2020-07-03 05:51:26 +08:00
/clang/utils/analyzer/projects/*/RefScanBuildResults
Reland [lldb][docs] Use sphinx instead of epydoc to generate LLDB's Python reference The build server should now have the missing dependencies. Original summary: Currently LLDB uses epydoc to generate the Python API reference for the website. epydoc however is unmaintained since more than a decade and no longer works with Python 3. Also whatever setup we had once for generating the documentation on the website server no longer seems to work, so the current website documentation has been stale since more than a year. This patch replaces epydoc with sphinx and its automodapi plugin that can generate Python API references. LLVM already uses sphinx for the rest of the documentation, so this way we are more consistent with the rest of LLVM. The only new dependency is the automodapi plugin for sphinx. This patch effectively does the following things: * Remove the epydoc code. * Make a new dummy Python API page in our website that just calls the Sphinx command for generated the API documentation. * Add a mock _lldb module that is only used when generating the Python API. This way we don't have to build all of LLDB to generate the API reference. Some notes: * The long list of skips is necessary due to boilerplate functions that SWIG is generating. Sadly automodapi is not really scriptable from what I can see, so we have to blacklist this stuff manually. * The .gitignore change because automodapi wants a subfolder of our documentation directory to place generated documentation files there. The path is also what is used on the website, so we can't really workaround this (without copying the whole `docs` dir somewhere else when we build). * We have to use environment variables to pass our build path to our sphinx configuration. Sphinx doesn't support passing variables onto that script. Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D94489
2021-01-15 20:24:24 +08:00
# automodapi puts generated documentation files here.
/lldb/docs/python_api/
Reference in New Issue Copy Permalink