Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging the path of the compilation database being used. #268

Closed
golung opened this issue Jan 28, 2020 · 0 comments
Closed

Logging the path of the compilation database being used. #268

golung opened this issue Jan 28, 2020 · 0 comments

Comments

@golung
Copy link

golung commented Jan 28, 2020

Many developers are working in dynamic, complex environments in which multiple compilation databases are generated at different times and locations. It is therefore often unclear which compilation database - if any - is being used at a particular point in time.

Thus it will be very helpful of clangd printed the path of the compilation database that is being used into its log file.

arichardson pushed a commit to arichardson/llvm-project that referenced this issue Apr 1, 2020
Summary: Fixes clangd/clangd#268

Reviewers: sammccall

Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D73628
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant