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

An example of how to create a C++ compilation database is needed #13976

Open
vadimcn opened this issue Sep 11, 2021 · 2 comments
Open

An example of how to create a C++ compilation database is needed #13976

vadimcn opened this issue Sep 11, 2021 · 2 comments
Labels
help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)

Comments

@vadimcn
Copy link

vadimcn commented Sep 11, 2021

Description of the problem / feature request:

Please provide a definitive example of how to create a compilation database for a Bazel-based C++ project.

Feature requests: what underlying problem are you trying to solve with this feature?

There are numerous IDEs that rely on clang language server (which requires compilation database for precise source indexing) to implement code browsing / code completion features for C++.

@keith
Copy link
Member

keith commented Sep 11, 2021

@vadimcn
Copy link
Author

vadimcn commented Sep 11, 2021

https://github.com/grailbio/bazel-compilation-database/ can provide this

That repo is no longer supported, the tool cannot deal with the --config=... switch and... well, did not work on the repo I have on hand. I've spent a few hours trying to figure out what's wrong with it, but couldn't.
Edit: Tried it on a smaller repo. It worked, but took a veeery long time. Looks like it actually builds the entire repo?

Would be nice to hear from Bazel devs about how this sort of tool is supposed to work.

@oquenchil oquenchil added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed type: feature request untriaged labels Feb 14, 2022
@ShreeM01 ShreeM01 added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Jan 10, 2023
@keertk keertk added the help wanted Someone outside the Bazel team could own this label Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-CPP Issues for C++ rules type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

6 participants