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

Compilation database #18

Open
rwols opened this issue Jul 21, 2017 · 1 comment
Open

Compilation database #18

rwols opened this issue Jul 21, 2017 · 1 comment

Comments

@rwols
Copy link

rwols commented Jul 21, 2017

I'm playing around with DoxyPress and so far it seems very interesting. Nice work! I immediately have an issue I wanted to talk about. The clang parsing functionality is very interesting and I believe this is The Future™, so I'd like to use this.

Currently I need to pass compilation flags manually, and it seems this gets applied to all input files. Also, I get errors like an "undefined std::uint64_t", which seems to suggest it cannot find the standard library headers.

This might not be the best way to handle flags. There's already functionality to handle things like this with clang::tooling::CompilationDatabase.

Also, how exactly do you parse headers? The GUI seems to be attempting to parse implementation files, not header files. I'm guessing you're extracting the declarations from the translation unit resulting from parsing a .cpp file?

@bgeller
Copy link
Member

bgeller commented Jul 30, 2017

We have noted a few issues finding the system headers on some platforms. Talking to the clang team they are indicating this is a problem with clang 3.7 and works much better with clang 3.8. We are currently in the process of adding clang 3.8 and clang 3.9 support.

We have noted your request to leverage the CompilationDatabase to detect the flags.

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

2 participants