You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?The text was updated successfully, but these errors were encountered: