-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support for compile_commands.json #77
Comments
Support for compile_commands.json is definitely something I'm interested in adding to the project. Could you clarify which part of the functionality you'd like to see moved to a companion crate? |
I mean, supporting
I'm sure |
Oh I see, I misread your initial post. Sorry about that! I'll spend some time looking into existing solutions, but I imagine we can just implement this ourselves without too much trouble. |
Thank you :) |
Update: Implemented a thin wrapper for compile_commands.json and compile_flags.txt in a separate crate: https://github.com/WillLillis/compile_commands Will hopefully be able to start working on correcting include paths (and supporting inline diagnostics!) soon :) |
This way it is possible to extract the correct include paths. (ideally this should be a companion crate, to be shared across other language servers, I know)
The text was updated successfully, but these errors were encountered: