It looks like the compilation database is only used for discovering source files, without any additional cross translation unit analysis [1]. Even if you don't plan on implementing data flow tracking or other passes, it can still be interesting to know on which translation unit a function declaration is defined on.
Also, it seems we always have to recompile each unit when switching between source files. Consider pre-compiling and caching so it's only done once. That should also enable users to search across files/ASTs.
Nice, you don't see many new Qt projects that use QDockWidget anymore.
Nice to see another static analysis tool.
It looks like the compilation database is only used for discovering source files, without any additional cross translation unit analysis [1]. Even if you don't plan on implementing data flow tracking or other passes, it can still be interesting to know on which translation unit a function declaration is defined on.
Also, it seems we always have to recompile each unit when switching between source files. Consider pre-compiling and caching so it's only done once. That should also enable users to search across files/ASTs.
[1]: https://clang.llvm.org/docs/analyzer/user-docs/CrossTranslat...
Is this based on or otherwise related to kythe?
This is the repo: https://github.com/uvic-aurora/acav
Feel free to leave a comment if you have any questions. Thanks!