kadircet added a comment. > Strictly speaking you could, assuming you have a compile database and it's > okay to have copies or symlinks of the database.
Well you wouldn't have index shards without a compilation database anyway though. > That does speak to another issue though; moving the compile database to move > the index files is not very intuitive. We could improve the help text around > compile commands to explain fully the implications of the file which might > help. I am not sure if this is something that is interesting to the average user. Hence we've only documented in the designs <https://clangd.llvm.org/design/indexing.html> and the code: Before indexing each file, the index checks for a cached *.idx file on disk. After indexing, it writes this file. This avoids reindexing on startup if nothing changed since last time. These files are located in .cache/clangd/index/ next to compile_commands.json. For headers with no CDB, such as the standard library, they are in clangd/index under the user’s cache directory ($XDG_CACHE_HOME, DARWIN_USER_CACHE_DIR, or %LocalAppData%). Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D103377/new/ https://reviews.llvm.org/D103377 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
