Yep, for sure. Works well for my specific project setup though, and being able to look up where a given symbol comes from reliably (based on exactly same logic as compiler) and get taken directly to file and position in file sure does hit the spot!
Thomas
On 22/01/13 10:26, Matthew Brush wrote:
On 13-01-22 12:15 AM, Thomas Young wrote:
(As an aside, for myself, I'm managed to hack something up that uses libClang to lookup references, that doesn't need know about the whole set of project files in order to work. It actually just executes the corresponding compile command within libClang each time you click 'lookup reference', and so fits in quite nicely with the 'no list of files in project' paradigm..)
Sure, if you only want to lookup references in the same translation unit or any included header files that happen to be in the search path, but to really make full use, LibClang essentially needs a "project" to support it (include paths, defines, other translation units/files, etc).
Cheers, Matthew Brush
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel